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.
The fix is quite simple to overcome this warning i.e. just go ahead and delete the reported .swp file using rm -f /path/.file.swpBut with this you loose any chance of file recovery. So it is important that you first recover the content from .swp file before you delete it.
This command will recover the content of /tmp/file using /tmp/.file.swp into your current file i.e. /tmp/file_recover. Check the status of the Recovery. As it is also possible that if your .swp file is corrupted then Recovery may Fail
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.
Vim/Vi editor keeps a copy of your changes in these .swp files. The content in these swp files are updated after typing 200 characters or when you have not typed anything for four seconds.This only happens if the buffer was changed, not when you only moved around. The reason why it is not kept up to date all the time is that this would slow down normal work too much.
In addition, normally .example.swp file is made in the same directory of the original file. Then, you cannot list .example.swp files with ls on terminal. You need to use ll or ls -a commands to list .example.swp files on terminal.
This message is actually pretty important if you care about not losing text you've potentially not saved. It should not be considered annoying, and should not cause you to hastily delete the swap file or configure vim to run without it.
Any file you edit with vim will have a corresponding swap file while you edit, which vim uses to keep track of changes. When you quit editing a file, vim will automatically discard the corresponding swap file. Therefore, the existence of a swap file, and your attempt to write overtop the original file, should be cause for consideration and appropriate action.
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).
Note: If Vim has doubt about what it found, it will give an error message and insert lines with "???" in the text. If you see an error message while recovering, search in the file for "???" to see what is wrong. You may want to cut and paste to get the text you need.
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.
UPDATE: I tried to do as suggested .I pressed e and it opened the environment file then I pressed i to edit it and changed my nodejs version (initially it was 9.x and I made it 8.x) then I pressed Esc and then shift+; and then wq|x after that I finally pressed Enter and it closes the vi editor after that again I ran the same command but it gave me same error but with further update stating NEWER than swap file!
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.
Solution: ls -A (This will show you if a .swp file really existd)rm .filename.swp (This will delete the .swp file which was generated while you closed the session accidentally while editing the original file)
This is a strange problem. the swap file get created for the new files. so, my directory is empty there is no file exist and then when I vi test.txt I get the swap file message. It looks like the vi create .swp files as crash dump and show me that restore file message.
I found this thread from 2008, seems dated, but it sounds exactly like your issue. It would appear to be something with NetApp specifically. I noted that in your output the server was named netapp-3240 which I assumed was a NetApp appliance.
This behaviour is seen using "vim" to edit files, and causes an error message about the swap file being present (due to the swap file being created even though the open() return value implies it was not).
When someone mentions a "swap file", the first thing that comes into your mind might be the kind of file that you would create to increase the swap space on a Unix system. Think swapfile and the swapon command. But there's another kind of swap file that comes into play, generally when you're trying to edit a file that might have encountered some difficulties during a prior edit. That type of swap file is created by your system to help ensure that you don't lose important file content when something goes wrong. And it generally sits in the same directory as the original file and has .swp as its extension.
These swap files store content for the specific file -- for example, while you're editing a file with vim. They are set up when you start an edit session and then automatically removed when you're done unless some problem occurs and your editing session doesn't complete properly. In that case, vim will offer you a chance to recover your work where you left off.
If you were sitting in a directory containing a file that is currently being edited with vim, you might see the type of file that I'm referring to. If the file being edited were called chkAccts.sh, for example, the swap file set up when you begin your edit would be called .chkAccts.sh.swp and you could spot it sitting in the same directory were you to look for it from another window or login session.
These swap files have two purposes: 1) to help keep you from losing content if you run into some kind of editing glitch and 2) to keep you from editing the same file at the same time from each of two sessions. If an editing session crashes or you try to edit the file a second time from a separate window, vim will warn you by issuing a fairly verbose message indicating that the swap file exists and teling you that the reason is one of the two that I just mentioned. It will also supply the command needed to start the editing session using the contents of the swap file.
If you edit the file again, despite the warning, but fail to remove the swap file, vim will continue to warn you. It will show you something like this. In fact, it will show you this every time you edit the file -- as long as the .swp is still sitting there under your fingertips.
You might recognize some of the original file the contents if you try to look at a .swp file, but it's not going to look like exactly like the original file. It will contain your original text, but also some other content. It is, after all, a dump of some portion of your editing. They shadow your editing session.
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.
If, for some reason, you want your swap files to be stored somewhere other than your current directory, you can create a .vimrc file and insert a command such as directory=/tmp to use a different directory. You can also disable the behavior (creating swap files) altogether by setting up your .vimrc file like the one shown below. Though I think the protection is generally a good thing, some Unix folks prefer to use other means to ensure their files aren't subject to loss and think that the appearance of .swp files on their systems is more trouble than it's worth. The tradeoff should probably depend on whether you waste a lot of time cleaning up .swp files that you don't need or are grateful every time one of them saves work in progress when you editing session runs into problems.
Programs running on Linux 2.6+ distribution, for example vi, may open a swapfile when editing or creating new files and then change the mode bits on the swapfile to 600. When this setattr fails, it displays an error.E325: ATTENTIONFound a swap file by the name ".new_file.txt.swp"owned by: gen_user dated: Thu May 1 05:24:48 2008[cannot be read]While opening file "new_file.txt" dated: Thu May 1 05:24:48 2008The cifs.ntfs_ignore_unix_security_ops hidden option can be set to allow the vi operation to work without error in this scenario. In clustered Data ONTAP, the failure behavior can be overridden on either an entire vserver or a single volume. To override this for an entire vserver, set the ntfs-unix-security-ops field to ignore in the vserver nfs settings of the vserver. To override the failure behavior on a single volume, set the ntfs-unix-security-ops to ignore inside the export-policy rule that is exporting the volume. 2b1af7f3a8