search for: 000430

...ed optional features (10000). > Could you please run od -A x -t x1 /dev/hdd1 and send the output? For the superblock I get: 000400 c0 74 07 00 e2 e8 0e 00 d8 be 00 00 e1 8c 0e 00 000410 b5 74 07 00 00 00 00 00 02 00 00 00 02 00 00 00 000420 00 80 00 00 00 80 00 00 a0 3f 00 00 2f e9 7e 3b 000430 2f e9 7e 3b 01 00 16 00 53 ef 01 00 01 00 00 00 000440 1f e9 7e 3b 00 4e ed 00 00 00 00 00 01 00 00 00 000450 00 00 00 00 0b 00 00 00 80 00 00 00 04 00 00 00 000460 06 00 00 00 01 00 00 00 b9 d3 6c 59 2d cc 42 13 000470 91 84 d4 7b 60 d2 d9 50 00 00 00 00 00 00 00 00 000480 00 00 00 00 00 00 00 00...

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

If I have an image of a filesystem taken with dd, I can look at it with a hex editor and discover that an ext2/3 superblock is at offset 1024 and I can figure out a lot of info about it. I cannot figure out, however, how the superblock differs from ext2 in ext3. I can't tell them apart... the "magic number" is the same as well as the "revision" field. If I have such an

Hi folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)