From: Ferenc Wagner <wferi@niif.hu>
To: Barry Naujok <bnaujok@melbourne.sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Bug#387057: xfsprogs: repeated xfs_repair does not fix the filesystem
Date: Fri, 15 Sep 2006 13:41:23 +0200 [thread overview]
Message-ID: <87mz91mk64.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <200609140157.LAA22186@larry.melbourne.sgi.com> (Barry Naujok's message of "Thu, 14 Sep 2006 12:03:28 +1000")
"Barry Naujok" <bnaujok@melbourne.sgi.com> writes:
>> -----Original Message-----
>> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com]
>> On Behalf Of Ferenc Wagner
>> Sent: Wednesday, 13 September 2006 7:46 PM
>> To: Nathan Scott
>> Cc: 387057@bugs.debian.org; xfs@oss.sgi.com
>> Subject: Re: Bug#387057: xfsprogs: repeated xfs_repair does
>> not fix the filesystem
>>
>>
>> Still, xfs_check reported:
>> => link count mismatch for inode 400254 (name ?), nlink 0, counted 2
>> => link count mismatch for inode 4239409 (name ?), nlink 0, counted 2
>> => link count mismatch for inode 8388736 (name ?), nlink 39,
>> counted 38
>>
>> Further runs of xfs_repair didn't bring any change. On the root
>> filesystem the results are much the same, but xfs_check reports:
>> => sb_ifree 3042, counted 3041
>
> This has been reported before, can you try running an older xfsprogs before
> 2.8.10 and see how that goes? I think with the dir2 fixes, the nlink stuff
> might be a tad broken. I'll also look into it from my end.
Thanks. I tried xfsprogs 2.8.4 with the following result:
# xfs_repair /dev/main/usr
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
- 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
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
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
resetting inode 400254 nlinks from 0 to 2
resetting inode 4239409 nlinks from 0 to 2
resetting inode 8388736 nlinks from 39 to 38
done
# xfs_check /dev/main/usr
#
That is, my /usr partition looks fixed. On the other hand:
# xfs_repair -d /dev/main/root
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
- 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
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
- traversal finished ...
- traversing all unattached subtrees ...
- traversals finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done
# xfs_check /dev/main/root
sb_ifree 3044, counted 3043
#
That is, almost like before, but with incremented numbers (there was
filesystem activity since then).
So, there is some progress, but part of the problem remained.
--
Thanks,
Feri.
prev parent reply other threads:[~2006-09-15 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060911223008.5160.98142.reportbug@szonett.ki.iif.hu>
[not found] ` <20060912085025.A3552962@wobbly.melbourne.sgi.com>
2006-09-13 9:46 ` Bug#387057: xfsprogs: repeated xfs_repair does not fix the filesystem Ferenc Wagner
2006-09-14 2:03 ` Barry Naujok
2006-09-15 3:10 ` Peter Palfrader
2006-09-15 11:41 ` Ferenc Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mz91mk64.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=bnaujok@melbourne.sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox