| To: | Lachlan McIlroy <lachlan@xxxxxxx> |
|---|---|
| Subject: | Re: assertion failure with latest xfs |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 23 Oct 2008 13:31:49 -0400 |
| Cc: | xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <49003EFF.4090404@sgi.com> |
| References: | <49003EFF.4090404@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Thu, Oct 23, 2008 at 07:08:15PM +1000, Lachlan McIlroy wrote: > Just encountered this after pulling in the latest changes. We are trying to > initialise an inode that should have an i_count of 1 but instead it is 2. I > was running XFSQA test 167 when it happened. I think the assert is incorrect. The inode has been added to the radix tree in xfs_iget_cache_miss, and starting from that point an igrab can kick in from the sync code and bump the refcount. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH V2] xfs_repair: print superblock offsets and why they can't be verified, Eric Sandeen |
|---|---|
| Next by Date: | subscribe, Joseph Silverman |
| Previous by Thread: | assertion failure with latest xfs, Lachlan McIlroy |
| Next by Thread: | Re: assertion failure with latest xfs, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |