Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Note for anyone using a recent version of extundelete: the CLI syntax has changed. Don't mount the device you're trying to recover from, and instead use extundelete --restore-file <path> /dev/<device-file>. Commented Nov 9, 2018 at 3:21
  • use "rm-trash" utility which handles puts them to trash for later retrieval and supports all options of "rm" command. Commented Nov 20, 2018 at 14:20
  • Don't use "rm" if you wish to restore the files in future .You can use "rm-trash" utility from apt-get : github.com/nateshmbhat/rm-trash Commented Nov 20, 2018 at 14:30
  • could you explain where the number 22 on ` cp /proc/5383/fd/22 /path/to/restored/file` come from? I am stuck on that part, it gives me 5 different number Commented Aug 12, 2019 at 14:50
  • @AdiPrasetyo: As the answer states the fourth column in the lsof output is the number of the file descriptor the process has opened to the file. A process may have multiple open file descriptors to the same file. Commented Aug 13, 2019 at 14:46