Crontab Write Error Swap File
Contents |
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more
Write Error In Swap File Vim
about hiring developers or posting ads with us Vi and Vim beta Questions Tags Users Badges write error in swap file vi Unanswered Ask Question _ Vi and Vim Stack Exchange is a question and answer site for people using the vi and Vim families of write error in swap file unix text editors. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “E297: Write error in swap
Write Error In Swap File Linux
file” due to running in a VM up vote 3 down vote favorite UPDATE: I've tried both the :set noswapfile swapfile solution and the :e! solution and the swapfile one is better because it retains undo history even for large files, in this case meaning over 1.5 MB. For some reason, :e! does not keep undo history in those cases even though it does keep it in the normal case (say sub-100KB). The swapfile solution appears to me now to
E297: Write Error In Swap File
work under any circumstances, which is very impressive. A bit of a weird question: How can I cleanly get rid of or move past the error message "E297: Write error in swap file"? I am running GVim when this happens and do not want to be forced to close it down and reopen a new GVim because I don't want to lose all my open buffers and ideally I'd like to keep all my undo history in each file too, but even a solution where I lose undo history would be an improvement. I have one limited workaround right now noted at bottom and am looking for something a little better... Why would I want to ignore such an error? A good question: I am running GVim in a virtual machine and I have it open on a file on the "host" file system rather than the VM's own file system and I "suspend" the VM. After coming back from the suspend, every GVim window open on a host system file will give this message. So the message is evidently due to the disconnection from the host file system that has to occur when the VM is suspended. GVim obviously thinks it still has a valid perhaps file descriptor and such when it doesn't. So the way the error arises is not anything alarming and I just need or want a way to move past i
error on certain directories, but not others? All partitions have plenty of free space.nano didn't tell me much of the issues I was finding, then vim told me this error.[EDIT] Using cp e297 write error in swap file vim in this dir thinks there's no space on the device, which is incorrect. I'm on
E297 Write Error In Swap File Linux
/home and there's 30G free space. I can copy anything out of this dir just fine.Gonna try a fsck tomorrow. Permalink Reply Quote e514 file system full Spawn Report Mark Unread Edit Delete 22 Oct, 2009, David Haley wrote in the 2nd comment: Votes: 0 Sounds like something is messed up with your filesystem, yes, if df tells you there's space left and cp http://vi.stackexchange.com/questions/6641/e297-write-error-in-swap-file-due-to-running-in-a-vm tells you there's not. Is it possible that there's a permissions error somewhere? Permalink Reply Quote Spawn Report Mark Unread Edit Delete 22 Oct, 2009, Zeno wrote in the 3rd comment: Votes: 0 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 http://www.mudbytes.net/forum/topic/2208/ are still around somewhere with issues probably. Permalink Reply Quote Spawn Report Mark Unread Edit Delete 22 Oct, 2009, Cratylus wrote in the 4th comment: Votes: 0 I SUGGEST YOU BACK UP BEFORE REBOOTING THE BOX. YOU NEVER KNOW.-CRATHTTP://LPMUDS.NET Permalink Reply Quote Spawn Report Mark Unread Edit Delete 23 Oct, 2009, Davion wrote in the 5th comment: Votes: 0 Have you checked to see what your swap space looks like? 'top' should show all that. Also 'df' should show your disc space. Permalink Reply Quote Spawn Report Mark Unread Edit Delete 23 Oct, 2009, quixadhal wrote in the 6th comment: Votes: 0 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 havi
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads http://superuser.com/questions/218262/how-to-get-rid-of-the-warnings-when-opening-a-file-that-has-a-swp-file with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a http://forums.scotsnewsletter.com/index.php?showtopic=7120 question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to get rid of the warnings when opening a file that has a .swp file? up vote 24 down vote favorite 1 How can write error I get rid of the annoying warnings when I open a file that has a .swp file? Or, how do I not generate the .swp files at all? Example warning: E325: ATTENTION Found a swap file by the name ".notes.swp" owned by: james dated: Fri Dec 3 17:38:07 2010 file name: ~james/school/se/project-dir/rottencucumber/doc/notes modified: no user name: james host name: james-laptop process ID: 2251 (still running) While opening file "notes" dated: Fri Dec 3 18:46:10 2010 NEWER than swap file! (1) Another program may be write error in 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 notes" to recover the changes (see ":help recovery"). If you did this already, delete the swap file ".notes.swp" to avoid this message. Swap file ".notes.swp" already exists! [O]pen Read-Only, (E)dit anyway, (R)ecover, (Q)uit, (A)bort: vim vi share|improve this question edited Jun 19 '14 at 17:43 Oliver Salzburg♦ 56.1k35185245 asked Dec 4 '10 at 6:41 James 2,02431225 add a comment| 7 Answers 7 active oldest votes up vote 17 down vote accepted The pasted message suggests you still have the "notes" file open in another Vim session. It is definitely not a good idea to edit a file that is being edited elsewhere. If that message is wrong, you need to determine how your Vim session exited improperly and avoid that in the future. As for recovering, that may be an issue in this one instance since "notes" is newer than the Vim .swp file associated with it, but you can still try. Just make sure you copy your "notes" file to a backup location first. It would be a good idea to read through ":help recover.txt". The lesson here is that you're not supposed to be seeing this message, and that you are means Something Went Wrong Somewhere. It's (
functions may not work. Please re-enable javascript to access full functionality. 0 Crontab problems Started by valkarye , May 19 2004 12:58 AM Please log in to reply 24 replies to this topic #1 OFFLINE valkarye valkarye Contributor Members 11 posts Posted 19 May 2004 - 12:58 AM Hope someone can help,I'm using RedHat 9 that seems to be working fine, with one exception - I'm unable to install or edit a new crontab, even as root.Following the man page and other tutorials, I've removed the crontab entry (crontab -u root -r) and then created a new file using vim and attempted to install the new crontab using the command: crontab foo.txt .After hitting enter, the system pauses for a few seconds and then returns back to a prompt - with no mention of installing a new crontab.Running crontab -e displays no information and any info that is updatedand saved (:wq!) never displays the next time -e is run.ps -ef | grep cron shows that crond is running and /var/log/cron doesn't throw out any glaring errors (that I'm aware of).Any ideas?Thanks,EricP.S.This is system wide for all users Back to top #2 OFFLINE Bruno Bruno Le Professeur Pingouin Admin Emeritus 37,904 posts Posted 19 May 2004 - 04:32 AM Hi EricThis is a pretty weird problem indeed . . . . I am wondering if you still have the following files: /etc/crontab /etc/cron.hourly, daily, weekly, monthly /etc/anacrontabAlso, is there maybe something blocked in /var/spool/cron/XXXX ?You might want to try to upgrade the crontab file, Here is the latest for RH 9 . . and install it with: # rpm -Uhv crontabs-1.10-5.noarch.rpmIf that does no good maybe try the same with anacron # rpm -Uhv anacron-2.3-25.i386.rpm Bruno One Page Linux Manual ~ Yo Linux ~Great Linux Links ~ www.brunolinux.comMy Hometown ~ Registered Linux User #299965 ~ LFS User #11450 Back to top #3 OFFLINE linuxdude32 linuxdude32 Board Bigwig Members 2,702 posts Posted 19 May 2004 - 05:17 AM Welcome to the fo