| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Badness in mutex_destroy at kernel/mutex-debug.c:458 |
| From: | Nicolas KOWALSKI <Nicolas.Kowalski@xxxxxxx> |
| Date: | Fri, 31 Mar 2006 10:06:50 +0200 |
| In-reply-to: | <20060331100859.B952320@wobbly.melbourne.sgi.com> |
| References: | <vqozmj8nu2d.fsf@corbeau.imag.fr> <20060331100859.B952320@wobbly.melbourne.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Nathan Scott <nathans@xxxxxxx> writes: > On Thu, Mar 30, 2006 at 11:46:50AM +0200, Nicolas KOWALSKI wrote: >> Hello, >> >> On my 2.6.16.1 system, when I umount the XFS filesystem, I have this >> message: > > That should be fixed now up now. > >> It does not seem to cause any harm. I can still mount it, and >> xfs_check reports nothing. > > Yep, its harmless. That's good news! >> Subject: TAKE 949149 - fix mutex diagnostic >> >> Is this fix pending for 2.6.17 ? > > Thats been merged now, yes. Ok, Thanks. -- Nicolas |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_growfs tutorial?, Eric Sandeen |
|---|---|
| Next by Date: | Re: Could not allocate buf during xfs_fsr?, Justin Piszcz |
| Previous by Thread: | Re: Badness in mutex_destroy at kernel/mutex-debug.c:458, Nathan Scott |
| Next by Thread: | Metadata on separate volume, Mike McElroy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |