| To: | Amit Sahrawat <amit.sahrawat83@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS: Observed Crash followed by deadlock of khubd/sync/XFS |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 13 Sep 2011 11:26:08 -0400 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CADDb1s2S9R5RoaJ2NGSbCXORngx8PQVB6r3-QVJbjCUYh+B63Q@xxxxxxxxxxxxxx> |
| References: | <CADDb1s2QDk7y+JgMikoje35LviYQwzpgFihndUPuZx2VXYV4Ew@xxxxxxxxxxxxxx> <CADDb1s2S9R5RoaJ2NGSbCXORngx8PQVB6r3-QVJbjCUYh+B63Q@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Thu, Sep 08, 2011 at 10:58:35PM +0530, Amit Sahrawat wrote: > Since this is very hard to reproduce, to make it easy to debug. This > can be reproduce by introducing msleep in the kernel xfs_umountfs() > before xfs_log_sbcount(), just add a print before this function and > sleep and the moment the print appear unplug the USB device, same > scenario will be reproduced. > CRASH will show the backtrace and return to normal shell, but when > process state is checked, khubd will be shown in TASK-UNINTERRUPTIBLE > state 'D'. > Further if sync is issued that will also get converted to 'D' state, > the back-trace for each of the task is same as mentioned in the > previous mail. I've not been able to reproduce this using that method so far. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 3.1-rc4: spectacular kernel errors / filesystem crash, Eric Dumazet |
|---|---|
| Next by Date: | Re: Code Changes [Review Request]: xfs_trans_ail_delete() gets invoked with corrupted values ? Causing Crash and Deadlock., Christoph Hellwig |
| Previous by Thread: | Re: XFS: Observed Crash followed by deadlock of khubd/sync/XFS, Amit Sahrawat |
| Next by Thread: | Re: XFS: Observed Crash followed by deadlock of khubd/sync/XFS, Amit Sahrawat |
| Indexes: | [Date] [Thread] [Top] [All Lists] |