22 Oct, 2009, David Haley wrote in the 2nd comment:
Sounds like something is messed up with your filesystem, yes, if df tells you there's space left and cp tells you there's not. Is it possible that there's a permissions error somewhere?
22 Oct, 2009, Zeno wrote in the 3rd comment:
I think even as root in that dir I was getting the errors.
Anyway, the user ended up creating a new dir and copying the files to that dir. Solved the problem, although I still need to do a fsck since those sectors are still around somewhere with issues probably.
Anyway, the user ended up creating a new dir and copying the files to that dir. Solved the problem, although I still need to do a fsck since those sectors are still around somewhere with issues probably.
22 Oct, 2009, Cratylus wrote in the 4th comment:
23 Oct, 2009, Davion wrote in the 5th comment:
Have you checked to see what your swap space looks like? 'top' should show all that. Also 'df' should show your disc space.
23 Oct, 2009, quixadhal wrote in the 6th comment:
E297 from vim has nothing to do with system swap. It's an error writing to the temporary "swap" file that vim makes, and uses as a recovery option if your editor crashes or is disconnected abnormally. That used to be pretty common in the days of dialup connections.
It can be caused by a full disk. It can ALSO be caused by not having write permission to the directory that holds the file you're editing. For example, if you setup a directory for multiple developers and give them write access to certain files, they won't have the ability to create new files.
If you're also having the issue as root, it might be an issue with the disk itself, either being full or having a file system problem. It might also be mounted read-only, or I suppose your vim config might point the temp/swap file creation to a different directory that doesn't exist. There can also be weird issues with hard links or mounted devices, but you'd probably know if those were in play.
Crat's right though… if it IS a filesystem issue, and if fsck can't fix it automatically, you might be in for some pain. Be careful, and if you can back things up while it's running now, it's probably best to do so… just in case.
It can be caused by a full disk. It can ALSO be caused by not having write permission to the directory that holds the file you're editing. For example, if you setup a directory for multiple developers and give them write access to certain files, they won't have the ability to create new files.
If you're also having the issue as root, it might be an issue with the disk itself, either being full or having a file system problem. It might also be mounted read-only, or I suppose your vim config might point the temp/swap file creation to a different directory that doesn't exist. There can also be weird issues with hard links or mounted devices, but you'd probably know if those were in play.
Crat's right though… if it IS a filesystem issue, and if fsck can't fix it automatically, you might be in for some pain. Be careful, and if you can back things up while it's running now, it's probably best to do so… just in case.
13 May, 2010, Zeno wrote in the 7th comment:
fsck didn't help, ran e2fsck tonight and all is good now.
Random Picks
nano didn't tell me much of the issues I was finding, then vim told me this error.
[EDIT] Using cp in this dir thinks there's no space on the device, which is incorrect. I'm on /home and there's 30G free space. I can copy anything out of this dir just fine.
Gonna try a fsck tomorrow.