search for: dump2f

...filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> Trying to find alternate super-blocks proves futile: dump2fs /dev/sda2 | grep -i superblock dump2fs 1.41.12 (17-May-2010) dump2fs: Bad magic number in super-block while trying to open /dev/sda2 Couldn't find valid filesystem superblock The file systems on this host were all created as type ext4 and all are lvs with the exception of /boot, which is not...

...ll of the drives in there. three of my drives had all their data remain intact, but the fourth one did not. all that remained on the 4th drive was the lost+found directory. I'm sure the data is still there, it's just eluding me. sadly I don't know how to find it. Thought I found dump2fs which tells me that it needs recovery. don't know how much help this will give: dumpe2fs /dev/hdg1 dumpe2fs 1.32 (09-Nov-2002) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 1c762a60-0820-4ad1-9e61-ea5066870851 Filesystem mag...

...quot;large file" just a private file used by the file system itself, or maybe the journal? It is a large drive (500GB), so maybe a large file got generated which normally might appear smaller on a smaller drive. I tried ls -sal and other flags with ls looking for the large file. I also ran dump2fs, although the output can be somewhat complex. I included the beginning of the dump2efs output below my fsck.ext3 output. Thanks, Edmond ----- [root at localhost sbin]# /sbin/fsck.ext3 -f -v -n /dev/sda1 e2fsck 1.35 (28-Feb-2004) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking direc...