| To: | Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 6 Oct 2009 21:19:26 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>, Bas Couwenberg <bas@xxxxxxxxxxxxxxxx>, XFS List <xfs@xxxxxxxxxxx> |
| In-reply-to: | <4ACB080D.3010708@xxxxxxxxxxxxxxxx> |
| References: | <20090930124104.GA7463@xxxxxxxxxxxxx> <4AC60D27.9060703@xxxxxxxxxxxxxxxx> <20091005214348.GA15448@xxxxxxxxxxxxx> <4ACB080D.3010708@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.19 (2009-01-05) |
On Tue, Oct 06, 2009 at 11:04:13AM +0200, Patrick Schreurs wrote: > Christoph Hellwig wrote: >> It helps a bit, but not so much. I suspect it could be a double free >> of an inode, and I have identified a possible race window that could >> explain it. But all the traces are really weird and I think only show >> later symptoms of something that happened earlier. I'll come up with >> a patch for the race window ASAP, but could you in the meantime turn on >> CONFIG_XFS_DEBUG for the test kernel to see if it triggers somehwere >> and additionally apply the tiny patch below for additional debugging? > > Will try this. > > Could this by any change be releated (from 2.6.32.2)? I doubt it, but it's losely in the same area. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] mkfs: add discard support, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH] mkfs: add discard support, Nathan Scott |
| Previous by Thread: | Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim, Patrick Schreurs |
| Next by Thread: | Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim, Patrick Schreurs |
| Indexes: | [Date] [Thread] [Top] [All Lists] |