Ideally, the very instant you realized your boo-boo, you unmounted the file system. The success you may enjoy with this tool very much depends on how soon you can off-line the Ext4 file system that housed the original, now-deleted file. Extundelete may very well be a part of your distribution, but in the root user's path, not in those of regular users. My go-to in these circumstances is extundelete which is a part of the System Rescue CD that I've flogged elsewhere. I suppose this means, tidy and diligent soul that you are, that you put the original in the Trashcan and emptied the Trash (otherwise, go rummage through the Trash. I am hoping there is software that would allow me to say "find data that starts with this and return the complete file or up to a specific size after it". I don't know the original size or Inode, all I have is the file name and the first 40% of the file. I also tried fsck/e2fsck on the USB drive hoping maybe it did fully copy but was broken in between somehow, it reported fine.Īnyone have suggestions on how to "undelete" the file on the original drive? I have only mount it read-only once I found out the corruption to avoid overwriting it. I tried using debugfs lsdel on the original drive but only 4 entries came up which were by root (file was made by user, not root), and I think it only works if it deletes files by rm. Long story short, I had a file in an EXT4 volume that I copied over to a USB drive that was also EXT4, when the copy finished I checked the file sizes of the original and the copied file and they matched, once I saw they matched I deleted (through the trash can) the original file (<- big mistake), once I moved the USB to the other computer that had the same OS (Fedora), I copied over the file but the file was much smaller, about 40% of the original size! If only one partition is set up on your server, take note of the existing disk and partition.I made a really bad mistake, and because it was a recent file, it was not backedup. Make a note of the paths of the logical volumes or the multiple device. Sector size (logical/physical): 512 bytes / 4096 bytes In this example, the server's operating system uses the Logical Volume Manager:ĭisk /dev/ram0: 640 MiB, 671088640 bytes, 1310720 sectors The following example lists information about hard disks, partitions, logical volumes, and multiple devices of a server with software raid.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |