[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: EXT3-fs error (device ide0(3,9)): ext3_readdir



Hi Andreas,

On Tue, Nov 20, 2001 at 12:51:48PM -0700, Andreas Dilger wrote:
> That does seem to be a bad inode number, unless you actually have 400M
> inodes in this fs.  It seems somewhat strange in hex: 0x181a191d, so
> not just a single bit error, and name_len=23 is 0x17, so also strange,
> but rec_len seems OK.
> 
> > So what should I do now ? Go to runlevel 1, umount /usr and run fsck ?
> 
> Yes, always the best thing to do when having an ext2/ext3 problem,
> unless you want to keep it around in case we need more data to try
> and debug it.  What you might want to do is:
> 
Unfortunately I need this box, so I had to do the repair as fast as
possible.

> # unmount /usr
> # script /tmp/e2fsck.log
> # debugfs (device name)
> debugfs> dump <47390> /tmp/bad_dir
> debugfs> q
> 
> # od -Ax -tx4 -a /tmp/bad_dir
> (od output here)

000000 0000b91e 0201000c 0000002e 0000b91d
        rs   9 nul nul  ff nul soh stx   . nul nul nul  gs   9 nul nul
000010 0202000c 00002e2e 0000c2c7 010d0018
        ff nul stx stx   .   . nul nul   G   B nul nul can nul cr soh
000020 6c697562 736e6974 672e312e 0000007a
         b   u   i   l   t   i   n   s   .   1   .   g z nul nul nul
000030 0000c3a8 07070010 312e6873 007a672e
         (   C nul nul dle nul bel bel   s   h .   1   .   g   z nul
000040 0000c2c1 010a0014 73616272 2e312e68
         A   B nul nul dc4 nul  nl soh r   b   a   s   h   .   1   .
000050 00007a67 0000c2c3 01090014 68736162
         g   z nul nul   C B nul nul dc4 nul ht soh   b   a   s h
000060 672e312e 0000007a 0000c2c5 010c0014
         .   1   .  g   z nul nul nul   E B nul nul dc4 nul  ff soh
000070 68736162 2e677562 7a672e31 0000b88d
         b a s h b u g .  1 .  g z cr 8 nul nul
000080 0114001c 736e6573 656c6269 6964652d
         fs nul dc4 soh s e n s i b l e -   e d i
000090 2e726f74 7a672e31 0000b88f 010b0014
         t o r .  1 .  g z si 8 nul nul dc4 nul vt soh

These are the first 10 lines of the od output, the whole file has 
~370k. I can send it per pm or post other parts if you need it.

> 
> # e2fsck -f (device name)
> (e2fsck output here)

root enterprise [/3]:/home #e2fsck -f -v /dev/hda9
e2fsck 1.25 (20-Sep-2001)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

   55978 inodes used (1%)
    3107 non-contiguous inodes (5.6%)
         # of inodes with ind/dind/tind blocks: 2173/11/0
  244133 blocks used (86%)
       0 bad blocks
       0 large files

   48549 regular files
    3828 directories
       0 character device files
       0 block device files
       0 fifos
     428 links
    3592 symbolic links (3592 fast symbolic links)
       0 sockets
--------
   56397 files
										  
> # exit
> 
> and send the output to the list if it isn't too huge, otherwise some small
> interesting parts are OK, or you could keep it in case of future need.
> 
Done.



As you can see, fsck ran without any problems, also mount rw went fine,
no more problems so far.

Thanks for the quick help.


Cheers,

Dirk





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]