xfs_repair stymied!

xfs_repair stymied!

Post by Bob Bernst » Sun, 05 Sep 2004 04:50:54


An indigo2 running Irix 6.5 repeats this message in the system console:

WARNING: Filesystem "/poes": corrupt inode 6295024 ((a)extents = 819349670). Unmount and run xfs_repair.
ALERT: 0x0: 49 4e 81 a4 1 2 0 1 0 0 0 0 0 0 0 0
ALERT: Filesystem "/poes": XFS internal error xfs_iformat_extents(1) at line 703 of file ../fs/xfs/xfs_inode.c. Caller 0x881d25fc
ALERT: xfs_stack_trace[0] 0x881ce70c

Here is the xfs_repair output:

# xfs_repair /dev/dsk/dks1d6s7
Phase 1 - find and verify superblock...
Phase 2 - 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
invalid ino number 18446744073709551615 in dir ino 2101376, entry #2, bno 1
clearing ino number in entry 2...
illegal name "/0205723.nc4" in directory inode 2101376, entry will be cleared
invalid ino number 18446744073709551615 in dir ino 2101376, entry #3, bno 1
clearing ino number in entry 3...
illegal name "/0205723.nc5" in directory inode 2101376, entry will be cleared
invalid ino number 18446744073709551615 in dir ino 2101376, entry #34, bno 5
clearing ino number in entry 34...
illegal name "/0205811.cc2" in directory inode 2101376, entry will be cleared
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- clear lost+found (if it exists) ...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
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 / ...
Segmentation fault (core dumped)


This behaviour repeats if the command is repeated.

The file listing shows the "illegal" entities:

# ls -al > filelist
UX:ls: ERROR: Cannot access .//0205723.nc4: No such file or directory
UX:ls: ERROR: Cannot access .//0205723.nc5: No such file or directory
UX:ls: ERROR: Cannot access .//0205811.cc2: No such file or directory

They are all time-stamped Dec 31 1969.

Since this problem appears to resist xfs_repair's efforts to correct it, are
there any other approaches that might remedy the situation?


Best regards,

--
Bob Bernstein
 
 
 

xfs_repair stymied!

Post by Thomas Jah » Mon, 06 Sep 2004 20:58:38

Bob Bernstein < XXXX@XXXXX.COM > writes:


[...]


[...]


Unfortunately you will probably need to use xfs_db to cure such
problems. I once had a SGI support to walk me through
this. I'm myself not competent/confident enough to give you directions
to follow.

Thomas Jahns
--
"Computers are good at following instructions,
but not at reading your mind."
D. E. Knuth, The TeXbook, Addison-Wesley 1984, 1986, 1996, p. 9

 
 
 

xfs_repair stymied!

Post by ajm » Wed, 08 Sep 2004 22:54:09


You don't mention what release of Irix you're running (uname -R) I
encountered a very similar looking bug (triggered by illegal filenames
with prepended slashes) that was fixed in 6.5.23 - maybe you need the
xfs_repair binary from a later release?

Regards,
Andy