Ошибка чтения файла блокировки etc fstab swp недостаточно данных прочитано

Я получил такую ошибку при открытии файла /My_file/.main.cpp открывал с помощью программы nano.

Error reading lock file /My_file/.main.cpp.swp: Not enough data read

Как мне это исправить ??

задан 30 мая 2019 в 10:53

timob256timob256

2,8194 золотых знака38 серебряных знаков72 бронзовых знака

Надо удалить скрытый файл. .[Твой_файл].swp, который хранится в той же папке что и файл который я пытаюсь открыть.

Надо воспользоваться командой shell-a и удалить этот скрытый файл командой

# rm /My_file/.main.cpp.swp

Эта проблема возникает в nano 2.7.4 (по крайней мере у меня такая версия) и должна быть связана с тем, как nano обрабатывает поврежденный файл подкачки. Хотя её она бывает связана с нехваткой памяти.

ответ дан 30 мая 2019 в 10:53

timob256timob256

2,8194 золотых знака38 серебряных знаков72 бронзовых знака

Источник

@bbgeek17 Thank you for the reply. There is plenty of storage space on all drives, but you bring up a good point… There was an episode previously where syslog file overfilled the boot SSD with errors from an USB device. I deleted the syslog file, removed the device and all was forgotten. I wonder if the fstab.swp was created during this time and is a remnant of that issue? Based on your google search article, it sounds like the correct action is to rm the fstab.swp file. I will give it another 24hrs for other replies before I dare to delete an important system file and then report back to you.

I also attempted to edit etc/fstab with vi and received the following error thus supporting idea of fstab.swp file conflicting with fstab:

Code:

E325: ATTENTION
Found a swap file by the name "/etc/.fstab.swp"
          owned by: root   dated: Mon Jul 12 21:34:36 2021
         [cannot be read]
While opening file "/etc/fstab"
             dated: Wed Jun  2 20:04:31 2021

(1) Another program may be editing the same file.  If this is the case,
    be careful not to end up with two different instances of the same
    file when making changes.  Quit, or continue with caution.
(2) An edit session for this file crashed.
    If this is the case, use ":recover" or "vim -r /etc/fstab"
    to recover the changes (see ":help recovery").
    If you did this already, delete the swap file "/etc/.fstab.swp"
    to avoid this message.
"/etc/fstab" 5 lines, 207 characters

In the end, I think your articles recommendation to delete .fstab.swp is the most logical. Maybe a mv command versus rm to start. Incidentally, I did a DuckDuckGo search and that article did not appear. Maybe I should start using Google again.

Thanks for your feedback!

Last edited: Sep 30, 2021

Источник

I am getting this error while opening /etc/profile file using nano.

Error reading lock file /etc/.profile.swp: Not enough data read

How can I fix this?

Zanna♦

68.1k55 gold badges209 silver badges319 bronze badges

asked Jul 25, 2017 at 9:12

Try to remove the hidden file .[yourfilename].swp, which is stored in the same folder as the file that you are trying to open.
In your case try the shell command rm /etc/.profile.swp.

This issue also occurs with nano 2.7.4, and must be something to do with how nano handles a corrupted swapfile.

Hope this helped

storm

4,8836 gold badges33 silver badges48 bronze badges

answered Sep 21, 2017 at 8:50

sunwalkersunwalker

5513 silver badges2 bronze badges

The problem is linked to a bug in an older version of nano as seen here.

As per the report, the affected version was nano-2.4.2. You should run nano --version to ascertain your current version and update accordingly.

A more detailed report of the actual issue can be found here.

answered Jul 25, 2017 at 9:47

Was happening for me because I was out of disk space, I cleared up some space, deleted the swap file and it worked.

answered Dec 8, 2017 at 20:04

AnthonyAnthony

1211 silver badge3 bronze badges

This happened for me because of a log file that wasn’t rotating, it took the entire disk space, I solved it by truncating this log file, then removing the .swp file.

answered Aug 25, 2019 at 6:47

AyuMuAyuMu

111 bronze badge

For me this was because of running docker container logs.
Worked fine after deleting them.
Logs location: /var/lib/docker/containers/
rm -rf /var/lib/docker/containers/*

Note: this will delete all the log generated till today, you may choose to deleted not required and also take backup to avoid logs data loss.

answered May 23, 2022 at 8:44

Please try this one (run this on the current folder):

find . -name "*.swp" -delete

Keep in mind that as @pbhj commented:

[…] this will find all files below the current root, ending in .swp, and delete them. Which should work to remove temporary nano files, but might have unintended consequences.

answered Sep 6, 2022 at 20:38

Источник

Before you get into this article, you may find here are the most frequent solved problems here it is.

This article covers a detailed step by step solution and there are significant reasons this content serves your purpose. Success

I’m happy to share the piece of tip here that worked for me and saved my time a lot.

Let’s begin now,

Introduction

Before begin, a bit to describe my development work here is the project developed in PHP Laravel Framework with LAMP (Linux Apache, MySQL and Php). The completed Php project is deployed in AWS Server instance in where Linux Ubuntu 18.4 OS installed.

Over a period of time, php project captures error logs increased size and occupied disk space in server instance.

Software Involved

Linux — Ubuntu 18.4

Linux Command Terminal

PHP — Laravel Framework

MySQL

As you may have encountered these terms like error writing lock file no space left on device, swp: Not enough data read, .swp file. There could be lot of reasons why we encounter «Not enough space left«.

Similarly here are the most frequent search terms as you and me searched a lot to get here.

Error reading lock file /etc/.profile.swp Not enough data read

Error reading lock file /etc/.default.swp Not enough data read

Error reading lock file /etc/.rc.local.swp Not enough data read

As said above .swp file may be the one causing the error. In your case .swp could be profile or default or local.

Problem Description

This is what happened in my case,

I logged into server instance where my php project is deployed which is Ubuntu 18.4, and opened command Terminal (Ctrl + Alt + T). I navigated to project folder.

When exactly this error thrown?

There was a random common error in php project, if you are php background I’m sure you know it .env file and its purposes.

.env file stores all the configurations databases, SSL certificates credentials etc of the project.

As said in above box, I actually did not configure correctly, setting to APP_DEBUG=true in .env file is fine for development.

APP_DEBUG = true

Whereas when you deploy your project in server it is highly not recommended to set as true. It should be set to false as below

APP_DEBUG = false

Why setting to false is important?

Its because when you set APP_Debug = true in .env file means when you encounter error in application the exception thrown in browser along with whole .env file expose everything as plain text.

Imagine anyone sees the error can also read your database user name and password.

Apart from above suggested let’s get into the main problem description,

In the project folder .env file resides in root folder, now I try to open it (to change APP_DEBUG=false) in command line editor in terminal with this command $ sudo nano .env

$ sudo nano .env

After executing the command error show as «Error reading lock file ./..env.swp not enough data read«. This is because any file you open with any editor .swp file gets created. And in here, log file size huge and space on device is insufficient to open the file in editor.

If you have searched google many sites suggested different approach that did not help as much, that’s the only reason I’m providing helping hand, explore more here

Get Set Solution helps everyone with details steps with google search.

Solve Error reading lock file

So how I get rid of not enough data read on device? Let’s move to solution section.

Solution

The simple solution is provided in image below.

These are the 4 steps to do

1. Navigate to your Project folder

2. Find if you have hidden .swp files in folder

3. Delete the .swp files

4. Ensure you have deleted or not

STEP 1 : Navigate to your Project Folder

I have placed my project folder in /home/ubuntu/projects/generator.

/home is home directory

/ubuntu is user account

/projects is the folder name

/generator is the actual php application

STEP : 2 Find if you have hidden .swp files

As circled 1 in image, execute this command find . -name «*.swp»

$ find . -name «*.swp»

the result will be as below as circled 2 list of .swp files available in my project

.swp files

STEP 3 : Delete the .swp files

As circled 3 in image, execute the command find . -name «*.swp» -delete

$ find . -name «*.swp» -delete

After executing command, you find all the .swp files are deleted

STEP 4: Ensure you have deleted .swp files are not

Just execute the same command find . -name «*.swp» this takes to next line that indicates you have deleted .swp files successfully

If you have missed all 4 steps, you can refer to below image described.

Solved Error reading lock file not enough space on disk

So what’s next move?

Now you can proceed to open .env file using this command, that’s all done.

$ sudo nano .env

Источник

I tried running sudo nano /etc/fstab/ but such a file did not exist. So nano displays the following error:

[ Error reading lock file /etc/.fstab.swp: Not enough data read ]

Some other background info about my setup, I had a swap parition defined during the OS installation but due to space constaints on my main partition I deleted it, and consumed the space.

Afterwards I added a second drive to my system and I’m trying to use one of its partitions as the swap. This is possible with GParted using the swapon command but it needs to be done after every reboot.

Is there a way to permanently set the new partition as my swap?

asked Dec 12, 2016 at 14:17

As lemonslice said, you need to edit /etc/fstab and not /etc/fstab/.
You can use GParted to find your UUID (right click > informations).

Then just add a ligne to fstab like this UUID=YOUR_UUID none swap sw 0 0. I made you a screenshot to show you my configuration :

lemonslice

4,5024 gold badges17 silver badges37 bronze badges

answered Dec 12, 2016 at 16:08

ShiningShining

3062 silver badges10 bronze badges

You can check the UUID of your (new) swap space:

user@host:~$ lsblk -f -o NAME,FSTYPE,UUID | grep swap
├─sda3 swap   ce70123c-6341-4802-9b96-29c39fb4110b

You should edit sudo nano /etc/fstab (without the trailing slash) and add the line (make sure you use your UUID):

UUID=ce70123c-6341-4802-9b96-29c39fb4110b none            swap    sw              0       0

answered Dec 12, 2016 at 15:48

lemonslicelemonslice

4,5024 gold badges17 silver badges37 bronze badges

Run the following command to get the UUID of your swap partition:

ls -l /dev/disk/by-uuid

Edit your /etc/fstab and change the uuid

# swap was on /dev/sdax during installation
UUID=put_the uuid_here none            swap    sw              0       0

Assign the new uuid ( change sdax with yours)

swapoff /dev/sdax
mkswap -U put_the_uuid_here /dev/sdax
swapon -a

answered Dec 22, 2016 at 22:32

GAD3RGAD3R

2321 silver badge3 bronze badges

Источник

I tried running sudo nano /etc/fstab/ but such a file did not exist. So nano displays the following error:

[ Error reading lock file /etc/.fstab.swp: Not enough data read ]

Some other background info about my setup, I had a swap parition defined during the OS installation but due to space constaints on my main partition I deleted it, and consumed the space.

Is there a way to permanently set the new partition as my swap?

asked Dec 12, 2016 at 14:17

As lemonslice said, you need to edit /etc/fstab and not /etc/fstab/.
You can use GParted to find your UUID (right click > informations).

Then just add a ligne to fstab like this UUID=YOUR_UUID none swap sw 0 0. I made you a screenshot to show you my configuration :

lemonslice

4,5024 gold badges17 silver badges37 bronze badges

answered Dec 12, 2016 at 16:08

ShiningShining

3062 silver badges10 bronze badges

You can check the UUID of your (new) swap space:

user@host:~$ lsblk -f -o NAME,FSTYPE,UUID | grep swap
├─sda3 swap   ce70123c-6341-4802-9b96-29c39fb4110b

You should edit sudo nano /etc/fstab (without the trailing slash) and add the line (make sure you use your UUID):

UUID=ce70123c-6341-4802-9b96-29c39fb4110b none            swap    sw              0       0

answered Dec 12, 2016 at 15:48

lemonslicelemonslice

4,5024 gold badges17 silver badges37 bronze badges

Run the following command to get the UUID of your swap partition:

ls -l /dev/disk/by-uuid

Edit your /etc/fstab and change the uuid

# swap was on /dev/sdax during installation
UUID=put_the uuid_here none            swap    sw              0       0

Assign the new uuid ( change sdax with yours)

swapoff /dev/sdax
mkswap -U put_the_uuid_here /dev/sdax
swapon -a

answered Dec 22, 2016 at 22:32

GAD3RGAD3R

2321 silver badge3 bronze badges

Источник

Я получаю эту ошибку при открытии /etc/profile файл с помощью нано.

Error reading lock file /etc/.profile.swp: Not enough data read

Как я могу зафиксировать это?

задан
20 September 2018 в 12:00

4 ответа

Попробуйте удалить скрытый файл . [Yourfilename] .swp , который хранится в той же папке, что и файл, который вы пытаетесь открыть.
В вашем случае попробуйте команду оболочки rm /etc/.profile.swp.

Эта проблема также возникает с nano 2.7.4 и должна быть связана с тем, как nano обрабатывает поврежденный файл подкачки.

Надеюсь, это помогло

ответ дан storm
23 November 2019 в 01:51

Проблема связана с ошибкой в более старой версии nano , как показано здесь .

Согласно отчету, уязвимая версия было нано-2.4.2 . Вы должны запустить nano --version , чтобы узнать текущую версию и обновить ее соответствующим образом.

Более подробный отчет о реальной проблеме можно найти здесь .

ответ дан The Pizza Overlord
23 November 2019 в 01:51

Это случилось со мной, потому что у меня не было дискового пространства, я очистил некоторое пространство, удалил файл подкачки, и это сработало.

ответ дан Anthony
23 November 2019 в 01:51

Это случилось со мной из-за того, что файл журнала не вращался, он занимал все место на диске, я решил это, усекнув этот файл журнала, а затем удалив файл .swp.

ответ дан AyuMu
23 November 2019 в 01:51

Ошибка чтения файла блокировки etc fstab swp недостаточно данных прочитано

Before you get into this article, you may find here are the most frequent solved problems here it is.

This article covers a detailed step by step solution and there are significant reasons this content serves your purpose. Success

I’m happy to share the piece of tip here that worked for me and saved my time a lot.

Let’s begin now,

Introduction

Before begin, a bit to describe my development work here is the project developed in PHP Laravel Framework with LAMP (Linux Apache, MySQL and Php). The completed Php project is deployed in AWS Server instance in where Linux Ubuntu 18.4 OS installed.

Over a period of time, php project captures error logs increased size and occupied disk space in server instance.

Software Involved Linux — Ubuntu 18.4 Linux Command Terminal PHP — Laravel Framework MySQL

As you may have encountered these terms like error writing lock file no space left on device, swp: Not enough data read, .swp file. There could be lot of reasons why we encounter «Not enough space left«.

Similarly here are the most frequent search terms as you and me searched a lot to get here.

Error reading lock file /etc/.profile.swp Not enough data read Error reading lock file /etc/.default.swp Not enough data read Error reading lock file /etc/.rc.local.swp Not enough data read

As said above .swp file may be the one causing the error. In your case .swp could be profile or default or local.

Problem Description

This is what happened in my case,

I logged into server instance where my php project is deployed which is Ubuntu 18.4, and opened command Terminal (Ctrl + Alt + T). I navigated to project folder.

When exactly this error thrown?

There was a random common error in php project, if you are php background I’m sure you know it .env file and its purposes.

As said in above box, I actually did not configure correctly, setting to APP_DEBUG=true in .env file is fine for development.

APP_DEBUG = true

Whereas when you deploy your project in server it is highly not recommended to set as true. It should be set to false as below

Why setting to false is important?

Its because when you set APP_Debug = true in .env file means when you encounter error in application the exception thrown in browser along with whole .env file expose everything as plain text.

Imagine anyone sees the error can also read your database user name and password.

Apart from above suggested let’s get into the main problem description,

In the project folder .env file resides in root folder, now I try to open it (to change APP_DEBUG=false) in command line editor in terminal with this command $ sudo nano .env

After executing the command error show as «Error reading lock file ./..env.swp not enough data read«. This is because any file you open with any editor .swp file gets created. And in here, log file size huge and space on device is insufficient to open the file in editor.

If you have searched google many sites suggested different approach that did not help as much, that’s the only reason I’m providing helping hand, explore more here

Get Set Solution helps everyone with details steps with google search.

So how I get rid of not enough data read on device? Let’s move to solution section.

Solution

The simple solution is provided in image below.

These are the 4 steps to do

1. Navigate to your Project folder 2. Find if you have hidden .swp files in folder 3. Delete the .swp files 4. Ensure you have deleted or not

STEP 1 : Navigate to your Project Folder

I have placed my project folder in /home/ubuntu/projects/generator.

/home is home directory

/ubuntu is user account

/projects is the folder name

/generator is the actual php application

STEP : 2 Find if you have hidden .swp files

As circled 1 in image, execute this command find . -name «*.swp»

$ find . -name «*.swp»

the result will be as below as circled 2 list of .swp files available in my project

STEP 3 : Delete the .swp files

As circled 3 in image, execute the command find . -name «*.swp» -delete

$ find . -name «*.swp» -delete

After executing command, you find all the .swp files are deleted

STEP 4: Ensure you have deleted .swp files are not

Just execute the same command find . -name «*.swp» this takes to next line that indicates you have deleted .swp files successfully

If you have missed all 4 steps, you can refer to below image described.

So what’s next move?

Now you can proceed to open .env file using this command, that’s all done.

$ sudo nano .env

4 ответа

Другие вопросы по тегам:

Похожие вопросы:

./. interfaces.swp: Not enough data read

Re: ./. interfaces.swp: Not enough data read

Bookmarks

Bookmarks

Posting Permissions

А вот еще интересные материалы:

Software Involved

Linux — Ubuntu 18.4

Linux Command Terminal

PHP — Laravel Framework

MySQL

Error reading lock file /etc/.profile.swp Not enough data read

Error reading lock file /etc/.default.swp Not enough data read

Error reading lock file /etc/.rc.local.swp Not enough data read

1. Navigate to your Project folder

2. Find if you have hidden .swp files in folder

3. Delete the .swp files

4. Ensure you have deleted or not