Re: Problem with xfs_repair

[Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>]

On Fri, 28 Jul 2006, Justin Piszcz wrote:

> On Fri, 28 Jul 2006, Ralf Hildebrandt wrote:
>
> > xfs_repair gave me this when repairing my / fs using a knoppix boot cd:
> >
> > Phase 1 - find and verify superblock...
> > Phase 2 - using internal log
> >        - zero log...
> >        - scan filesystem freespace and inode maps...
> >        - found root inode chunk
> > Phase 3 - for each AG...
> >        - scan and clear agi unlinked lists...
> >        - process known inodes and perform inode discovery...
> >        - agno = 0
> >        - agno = 1
> >        - agno = 2
> >        - agno = 3
> >        - agno = 4
> >        - agno = 5
> >        - agno = 6
> >        - agno = 7
> >        - agno = 8
> >        - agno = 9
> >        - agno = 10
> >        - agno = 11
> >        - agno = 12
> >        - agno = 13
> >        - agno = 14
> >        - agno = 15
> >        - process newly discovered inodes...
> > Phase 4 - check for duplicate blocks...
> >        - setting up duplicate extent list...
> >        - clear lost+found (if it exists) ...
> >        - clearing existing "lost+found" inode
> >        - marking entry "lost+found" to be deleted
> >        - check for inodes claiming duplicate blocks...
> >        - agno = 0
> >        - agno = 1
> >        - agno = 2
> >        - agno = 3
> >        - agno = 4
> >        - agno = 5
> >        - agno = 6
> >        - agno = 7
> >        - agno = 8
> >        - agno = 9
> >        - agno = 10
> >        - agno = 11
> >        - agno = 12
> >        - agno = 13
> >        - agno = 14
> >        - agno = 15
> > Phase 5 - rebuild AG headers and trees...
> >        - reset superblock...
> > Phase 6 - check inode connectivity...
> >        - resetting contents of realtime bitmap and summary inodes
> >        - ensuring existence of lost+found directory
> >        - traversing filesystem starting at / ...
> > rebuilding directory inode 128
> >
> > fatal error -- can't read block 16777216 for directory inode 167785633
> >
> > a) How can I find out which file/directory this inode belongs to?
> > b) Can I mark the block defektiv somehow?
> >
> > --
> > Ralf Hildebrandt (i.A. des IT-Zentrums)         Ralf.Hildebrandt@xxxxxxxxxx
> > Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
> > Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-962
> > IT-Zentrum Standort CBF                 send no mail to spamtrap@xxxxxxxxxx
>
> Is your knoppix boot cd 5.0.1 == 2.6.17 == bugged kernel? ;P

When repairing, do not use knoppix 5.0.1 or any version that uses 2.6.17 
either..