| To: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 3.5.0-rc5: inconsistent lock state |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 5 Jul 2012 03:43:07 -0400 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <alpine.DEB.2.01.1207041206390.5568@xxxxxxxxxxxxxx> |
| References: | <alpine.DEB.2.01.1207041206390.5568@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Wed, Jul 04, 2012 at 12:13:32PM -0700, Christian Kujau wrote: > Hi, > > this powerpc machine is running 3.5.0-rc5 for 2 days now and this happened > today: See my "do not take the iolock in inode reclaim context" series from yesterday, which should take care of this. Btw, if you hit this it's a sign you have out of the inode attributes, so if this isn't just a single inode with them you might be better off using larger inodes. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: bug? "directory flags set on non-directory inode 2877105", Dave Chinner |
|---|---|
| Next by Date: | Re: bug? "directory flags set on non-directory inode 2877105", Arkadiusz MiÅkiewicz |
| Previous by Thread: | Re: 3.5.0-rc5: inconsistent lock state, Christian Kujau |
| Next by Thread: | Re: 3.5.0-rc5: inconsistent lock state, Christian Kujau |
| Indexes: | [Date] [Thread] [Top] [All Lists] |