Vi and Vim Asked by Connie Jash on February 5, 2021
I am SSHing into an Ubuntu machine where I use Bash as the shell. I used to be able to edit my ~/.vimrc
file very easily. Now, whenever I try to write to it, I get a warning
E297 write error in swap file
and also after typing in text, I cannot save the changes. Vim tells me that
E667: Fsync failed.
In order to exit the file, I simply have to type the :q!
(force quit command).
This also happens to my ~/.bashrc
file, and any other ~/.file
that I access. However, I can successfully edit files in any directory outside of /usr2/
.
This is an NFS file system and ls -ld ~
outputs that I have rwx
permissions on that directory, and that I am the owner of it:
drwxrwxrwx 9 my_name users ... /usr2/my_name
It is odd because I am the owner of the file and have reading and writing permissions:
ls -l ~/.vimrc
-rwxr----- 1 my_name users 172 Aug 18 14:18 /usr2/my_name/.vimrc
I also have only used 54% of my allotted disk space by my system admin, so it cannot be a disk space issue. I also cannot find any .vimrc.swp
files.
It turns out that I had installed a version control tool called "repo" on the home directory of the company computer (/usr2/user_name) that had a very small disk partition allocated to it by the system admin. It took up 5GB of space. I removed it and already had it installed in a different directory.
After the removal and freeing up of disk space, I was able to edit my ~/.vimrc and ~/.bashrc files that are in the home directory.
It also turns out that my company has a special tool for checking users disk quota, and running df
command was not accurate enough (I had not used 54% of quota, I had used 100%). Pretty much, just make sure to have enough disk space available.
Answered by Connie Jash on February 5, 2021
Get help from others!
Recent Answers
Recent Questions
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP