| To: | Barry Naujok <bnaujok@xxxxxxx> |
|---|---|
| Subject: | Re: REVIEW: Don't reset dirty inode flag in xfs_repair |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 29 Sep 2008 10:23:18 -0400 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <op.uhy9dlyz3jf8g2@pc-bnaujok.melbourne.sgi.com> |
| References: | <op.uhy9dlyz3jf8g2@pc-bnaujok.melbourne.sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Wed, Sep 24, 2008 at 06:47:35PM +1000, Barry Naujok wrote: > If an inode is dirtied due to some error in an inode, the very last > check (nlink version) in process_dinode_int() in xfs_repair sets the > dirty flag rather than just bumping it if it dirtied the inode. > > So, if something earlier dirtied the inode without marking it bad > (eg. resetting the inode's next unlinked field in the example that > detected this issue), that dirty state will be lost if the nlink > version checks out fine. Looks good, but the diff you posted also includes a hunk in db/check.c that introduces another sanity check in process_inode() which seems unrelated. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 3/3] Add timeout feature, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [REVIEW] Check for valid agf_btreeblks with lazy counters enabled, Christoph Hellwig |
| Previous by Thread: | REVIEW: Don't reset dirty inode flag in xfs_repair, Barry Naujok |
| Next by Thread: | TAKE 985583 - implement semi-generic xfs_btree_new_root, Lachlan McIlroy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |