Hello.
I controled my FS's with "xfs_repair -n" to be sure that they are error
free. Everything is OK but FS on disk hda9. I can do clean mount and umount
of hda9. xfs_check do not notice any errors. But output of xfs_repair:
# xfs_repair -n /dev/hda9
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- scan filesystem freespace and inode maps...
block (0,223632) multiply claimed by bno space tree, state - 1
block (1,223632) multiply claimed by bno space tree, state - 1
block (2,223632) multiply claimed by bno space tree, state - 1
block (4,223632) multiply claimed by bno space tree, state - 1
block (8,223632) multiply claimed by bno space tree, state - 1
block (9,223632) multiply claimed by bno space tree, state - 1
block (10,223632) multiply claimed by bno space tree, state - 1
block (11,223632) multiply claimed by bno space tree, state - 1
block (13,223632) multiply claimed by bno space tree, state - 1
block (14,223632) multiply claimed by bno space tree, state - 1
block (15,223632) multiply claimed by bno space tree, state - 1
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
data fork in ino 16152860 claims free block 1010064
- agno = 4
data fork in ino 16791313 claims free block 1534352
- agno = 5
- agno = 6
data fork in ino 25176869 claims free block 1796496
data fork in ino 25176898 claims free block 2058640
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
data fork in ino 53909610 claims free block 3369360
- agno = 13
- agno = 14
- agno = 15
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
data fork in regular inode 16152860 claims used block 1010064
would have cleared inode 16152860
- agno = 4
data fork in regular inode 16791313 claims used block 1534352
would have cleared inode 16791313
entry "140_4023.JPG" at block 0 offset 2376 in directory inode 17462732
referenc
es free inode 16791313
would clear inode number in entry at offset 2376...
- agno = 5
- agno = 6
data fork in regular inode 25176869 claims used block 1796496
would have cleared inode 25176869
data fork in regular inode 25176898 claims used block 2058640
would have cleared inode 25176898
entry "del8s.jpg" at block 0 offset 1392 in directory inode 26502965
references
free inode 25176869
would clear inode number in entry at offset 1392...
entry "Rea4s.JPG" at block 0 offset 2088 in directory inode 26502965
references
free inode 25176898
would clear inode number in entry at offset 2088...
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
data fork in regular inode 53909610 claims used block 3369360
would have cleared inode 53909610
- agno = 13
- agno = 14
- agno = 15
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
Segmentation fault
# xfs_repair /dev/hda9
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
block (0,223632) multiply claimed by bno space tree, state - 1
block (1,223632) multiply claimed by bno space tree, state - 1
block (2,223632) multiply claimed by bno space tree, state - 1
block (4,223632) multiply claimed by bno space tree, state - 1
block (8,223632) multiply claimed by bno space tree, state - 1
block (9,223632) multiply claimed by bno space tree, state - 1
block (10,223632) multiply claimed by bno space tree, state - 1
block (11,223632) multiply claimed by bno space tree, state - 1
block (13,223632) multiply claimed by bno space tree, state - 1
block (14,223632) multiply claimed by bno space tree, state - 1
block (15,223632) multiply claimed by bno space tree, state - 1
- 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
data fork in ino 16152860 claims free block 1010064
- agno = 4
data fork in ino 16791313 claims free block 1534352
- agno = 5
- agno = 6
data fork in ino 25176869 claims free block 1796496
data fork in ino 25176898 claims free block 2058640
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
data fork in ino 53909610 claims free block 3369360
- 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) ...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
data fork in regular inode 16152860 claims used block 1010064
xfs_repair: dinode.c:2436: process_dinode_int: Assertion `err == 0' failed.
# xfs_info /mnt/mnt
meta-data=/dev/hda9 isize=256 agcount=16, agsize=223633 blks
= sectsz=512
data = bsize=4096 blocks=3578128, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=2560, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
# xfs_db /dev/hda9
xfs_db> inode 16152860
xfs_db> print
core.magic = 0x494e
core.mode = 0100644
core.version = 1
core.format = 2 (extents)
core.nlinkv1 = 1
core.uid = 500
core.gid = 500
core.flushiter = 5
core.atime.sec = Thu Aug 11 23:12:14 2005
core.atime.nsec = 855897961
core.mtime.sec = Thu Aug 11 23:12:14 2005
core.mtime.nsec = 856897741
core.ctime.sec = Thu Aug 11 23:12:14 2005
core.ctime.nsec = 856897741
core.size = 5898
core.nblocks = 2
core.extsize = 0
core.nextents = 1
core.naextents = 0
core.forkoff = 0
core.aformat = 2 (extents)
core.dmevmask = 0
core.dmstate = 0
core.newrtbm = 0
core.prealloc = 0
core.realtime = 0
core.immutable = 0
core.append = 0
core.sync = 0
core.noatime = 0
core.nodump = 0
core.rtinherit = 0
core.projinherit = 0
core.nosymlinks = 0
core.gen = 1
next_unlinked = null
u.bmx[0] = [startoff,startblock,blockcount,extentflag] 0:[0,1010063,2,0]
Xfs_repair is from xfsprogs-2.7.1. Computer is amd64 with 512M memory and
kernel SGI-XFS CVS-2005-09-21_05:00_UTC with ACLs, large block/inode
numbers, no debug enabled.
Is it bug in xfs_repair? How can I repair this FS? Should I delete inode
with xfs_db? Can you write me how?
jan
--
|