Found A Swap File By The Name .swp
Kanisha Dezarn
The two scenarios presented in the message (E325: ATTENTION Found a swap file) are actually quite common: (1) either another vim program is editing the very same file you're trying to edit (it could actually be another person - in which case it really wouldn't make sense to just blindly delete the swap file - or it could be you in another terminal window or tab), or (2) a previous vim session crashed (most often this happens when you're editing remotely, and the network session is severed - in which case the vim session was not exited normally, and the .swp file remains behind; another example of this second scenario is that you've accidentally closed the terminal window or tab that had an active or backgrounded vim session).
About swap files. These swap files help you recover in case you loseyour connection (e.g., dropped wifi). They also protect you from trying toedit the same file from two places at the same time. When you open Vim, itcreates the swap file (e.g., .after.c.swp). As you type, it records all ofyour edits, even before you save. When you close Vim properly, it deletes theswap file. If you lose your connection, it will find the file and let you knowthat you can use it to recover your unsaved work. If you try to open the filefrom two places at once, it finds the file and gives you the same warning.
Are you getting "Found a swap file by the name" for some file with .swp extension? Are you trying to open a file using some editor such as vim or vi and getting this message? Do you want to get rid of this message? The solution is quite easy, just delete the reported .swp file but hey It is important that you fix this properly or you may loose unsaved data.
In this tutorial we learned all about swp files, why it is important to use these swp files and how to fix "Found a swap file by the name". It is very much possible that due to some unexpected event your existing vim/vi session crashed which would normally mean that all your saved changes are lost. But NO.
If you want to abandon prior editing changes that might be recorded in the swap file, just look for a file with the same name as the one you were editing, but starting with a period and having the extension .swp added to the end and remove it. Problem resolved.
When you see the message that a swap file is found, there is a lot oftext and several choices. There are three important details to lookfor:
- Is the file still being edited somewhere ("STILL RUNNING")?
- Is the file modified?
- Is the current version newer than the swap file?
If you need to remove a swapfile and can't use the "D" option, you can removethe file by hand using the "rm" command. To do that, you first need to knowthe name of the swapfile. The swapfile's name is derived from the name of thefile you are editing. Typically, vim will add a dot to the beginning of thefilename and add ".swp" to the end. For example, if you were editing a filenamed index.html, the vim swapfile would be named.index.html.swp. The dot at the beginning makes the swapfile ahidden file, so it won't show up when you type "ls" unless you typesomething like "ls -ald .*". To remove the file, you would type "rm" followedby the name of the swapfile. For example, you might type:
After recovering a file from a swapfile and deleting the swapfile you will usually use swapname .swo (or similar). If something goes wrong again, vim will not detect the .swo swapfile on startup. It is useful to restart vim, or do the following trick:
If you are using the function in a loop over swap files, you can use the script like so: vim-process-swap -s $swapfile and you won't need to pass the real filename. Note that when using the -s flag that it isn't possible to specify a recoveryfile name or location.
thank you very much for replying my post, I followed your suggestion and did several test. I found that the problem is not the file name. if I intentionalyl delete a part in schematic, and then redo the back annotate, then the Cadence will generate the same complain. here is my test sequence
If your /etc/fstab file has an entry for /dev/xvdb (or /dev/sdb) change it to match the line below; if it does not have an entry for this device, append the following line to your /etc/fstab file (using the swap device name for your system):
Is it possible you opened the vhost.conf file earlier with 'vi'? It creates a swap file (.swp) to notify other users when they open the same file, and in case your session crashes, it will store unsaved changes. It is save to remove this file if and only if nobody else is editing the file (Thanks to MadHatter for correcting me).
The script checks whether /private/var/vm/sleepimage exists. If it doesn't, then the swap volume isn't mounted and tries to mount the correct volume. If it does, it will check again four more times in two minute intervals before exiting. The reason I added this was because I found if I simply tried to mount the volume as soon the daemon loaded, it would fail.
Motivated by the same concerns, I wrote the following code and added it to my init.m file. There are two main entries you'll want to change to use this. The global variable $SwapDirectory is where the swap files are saved (by swap file, I mean it in the VIm sense; an "extra" copy of your notebook, separate from your manually saved copy that periodically saves any new work). The swap files are organized within the swap directory in a directory structure which "mirrors" their original file locations, and have ".swp" appended to their file names. The other variable you might want to change is the number of seconds between autosaves, indicated by the "300" (corresponding to 5 minutes) near the bottom of the code below. At the appropriate times, this code will (automatically in the background) save swap files for ALL open notebooks, unless they are unmodified from their manually-saved versions (this exception makes the code more efficient, and more importantly, prevents the storage of swap files for documentation notebooks, for example).
Try not to have any swap partitions or pupswap.swp files on microSD cards or flash drives. They usually run slower than regular hard drives, and also have limited number of writes before they start to fail. Using swap does a lot of disk writes.