search for: e2salvage

...nting crashes. Mounting the filesystem manually errors with "invalid argument". I suspect this is either ext3 corruption, or lvm2 corruption, or both. I've made a copy of the partition on another system, and have been testing various things on that copy, like various fsck commands, e2salvage, e2extract, but fsck complains about bad superblocks, e2salvage apparently ran out of memory, and e2extract just listed millions of 0 length files. I wrote a small python script that hunts for ext3 magic numbers, and it found some in both a known-good ext3, as well as my corrupt partition image....

...the idea of searching for inodes. Maybe not all inodes are overwritten? What would you say? Are there chances that some inodes are not overwritten? Or are they all lost? Overwritten by zeros? Maybe not all of them are overwritten because of the '-j' switch? I modified the program "e2salvage" to find all inodes. I know, I had ~ 117807 files and directories on the disk. e2salvage found 85064 inodes. But I have the problem that on the disk there was an image (~1GB) with a whole Linux file system. I think block size also 4096. Do you think the inodes are from that image or could th...

So you know, I don't know too much about file systems. Here is what I did: I have two linux boxes. the first box had many hardrives in it, but needed to be used in other ways. So I took 4 harddrives out of it and placed it in the other Linux box. I thought it would be able to read these right away. (maybe this was my mistake?) I could mount all of the drives in there. three of my

...-bash: cd: kdo: Input/output error >From what I've read I should be able to get to the inodes under this directory and they will hold my data. Can someone provide syntax on how I can do this? FYI, I've tried the following utilities: - e2fsck (with every flag combination imaginable) - e2salvage - Tried to copy the partition to another via dd if=/dev/hdb2 of=/dev/hda2 bs=512 conv=noerror,sync,notrunc - Tried to copy partition with dd_rescue, and the verbose output shows that when it reaches certain positions it gets an "Input/output error" I ran dd_rescue -rfv /dev/hdb2 out then...

...) First inode: 11 Inode size: 128 Journal UUID: <none> Journal inode: 8 Journal device: 0x0000 First orphan inode: 0 Even clearing the has_journal and needs_recovery flags produced the same output using fsck as above. Running e2salvage on this backup-partition (/dev/hdb1 is the 'real' partition, /dev/hdb2 was written using dd) didn't help much as well. Hoping for some suggestions how to safe my data, since last backup was two month old :-( Regards -- Stephan Wiehr http://www.asta.uni-sb.de/~lynx/ "Alwa...

Hi, One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system. These are the first errors in the log: kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is

...e numbers look scary to me: --8<-- 11 inodes used (0%) 7136 non-contiguous inodes (64872.7%) # of inodes with ind/dind/tind blocks: 50303/388/0 126175 blocks used (1%) --8<-- I haven't even tried to have it "fix" the fs on the image file. What do you think? e2salvage doesn't recognize any superblocks (not even the backup superblocks dumpe2fs happily uses to display some information on the fs image), maybe because it's not an ext2 but ext3 fs. Well. Currently I'm running e2retrieve on the image to see whether this is able to do some recovery, but no...