| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: INFO: task mount:11202 blocked for more than 120 seconds |
| From: | Milan Broz <mbroz@xxxxxxxxxx> |
| Date: | Fri, 14 Mar 2008 10:27:07 +0100 |
| Cc: | Christian Kujau <lists@xxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, dm-devel@xxxxxxxxxx |
| In-reply-to: | <20080309213441.GQ155407@xxxxxxx> |
| References: | <alpine.DEB.1.00.0803072116420.7723@xxxxxxxxxxxxxxxxxx> <20080307224040.GV155259@xxxxxxx> <alpine.DEB.1.00.0803080032020.7723@xxxxxxxxxxxxxxxxxx> <20080309213441.GQ155407@xxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.12 (X11/20080226) |
David Chinner wrote: >>> Also, the iolock can be held across I/O so it's possible you've lost an >>> I/O. Any I/O errors in the syslog? >> No, no I/O errors at all. See the kern.log above, I could even do dd(1) >> from the md1 (dm-crypt on raid1), no errors either. > > Oh, dm-crypt. Well, I'd definitely start looking there. XFS has a > history of exposing dm-crypt bugs, and these hangs appear to be I/O > congestion/scheduling related and not XFS. Also, we haven't changed > anything related to plug/unplug of block devices in XFS recently, so > that also points to some other change as well... Yes, there is bug in dm-crypt... Please try if the patch here helps: http://lkml.org/lkml/2008/3/14/71 Thanks, Milan -- mbroz@xxxxxxxxxx |
| Previous by Date: | Re: XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c, Christian Røsnes |
|---|---|
| Next by Date: | xfs_repair on root filesystem, Massimiliano Adamo |
| Previous by Thread: | Re: INFO: task mount:11202 blocked for more than 120 seconds, Samuel Tardieu |
| Next by Thread: | Re: INFO: task mount:11202 blocked for more than 120 seconds, Christian Kujau |
| Indexes: | [Date] [Thread] [Top] [All Lists] |