From: Austin Schuh <austin@peloton-tech.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: XFS crash?
Date: Wed, 5 Mar 2014 16:53:06 -0800 [thread overview]
Message-ID: <CANGgnMb=2dYGQO4K36pQ9LEb8E4rT6S_VskLF+n=ndd0_kJr_g@mail.gmail.com> (raw)
In-Reply-To: <20140305233551.GK6851@dastard>
Hi Dave,
On Wed, Mar 5, 2014 at 3:35 PM, Dave Chinner <david@fromorbit.com> wrote:
> On Wed, Mar 05, 2014 at 03:08:16PM -0800, Austin Schuh wrote:
>> Howdy,
>>
>> I'm running a config_preempt_rt patched version of the 3.10.11 kernel,
>> and I'm seeing a couple lockups and crashes which I think are related
>> to XFS.
>
> I think they ar emore likely related to RT issues....
>
That very well may be true.
> Your usb device has disconnected and gone down the device
> removal/invalidate partition route. and it's trying to flush the
> device, which is stuck on IO completion which is stuck waiting for
> the device error handling to error them out.
>
> So, this is a block device problem error handling problem caused by
> device unplug getting stuck because it's decided to ask the
> filesystem to complete operations that can't be completed until the
> device error handling progress far enough to error out the IOs that
> the filesystem is waiting for completion on.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
I unplugged the USB device _after_ the rest of the system started
locking up to see if that might unstick things.
Austin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-03-06 0:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 23:08 XFS crash? Austin Schuh
2014-03-05 23:35 ` Dave Chinner
2014-03-06 0:53 ` Austin Schuh [this message]
2014-05-13 1:29 ` Austin Schuh
2014-05-13 3:10 ` Austin Schuh
2014-05-13 3:33 ` Austin Schuh
2014-05-13 3:46 ` Dave Chinner
2014-05-13 4:03 ` Austin Schuh
2014-05-13 6:39 ` Dave Chinner
2014-05-13 7:02 ` Austin Schuh
2014-05-13 9:03 ` Dave Chinner
2014-05-13 17:11 ` Austin Schuh
2014-06-23 20:05 ` Austin Schuh
2014-06-24 3:02 ` On-stack work item completion race? (was Re: XFS crash?) Dave Chinner
2014-06-24 3:02 ` Dave Chinner
2014-06-24 3:25 ` Tejun Heo
2014-06-24 3:25 ` Tejun Heo
2014-06-25 3:05 ` Austin Schuh
2014-06-25 14:00 ` Tejun Heo
2014-06-25 14:00 ` Tejun Heo
2014-06-25 17:04 ` Austin Schuh
2014-06-25 17:04 ` Austin Schuh
2014-06-25 3:16 ` Austin Schuh
2014-06-25 3:16 ` Austin Schuh
2014-06-25 5:56 ` Dave Chinner
2014-06-25 5:56 ` Dave Chinner
2014-06-25 14:18 ` Tejun Heo
2014-06-25 14:18 ` Tejun Heo
2014-06-25 22:08 ` Dave Chinner
2014-06-25 22:08 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANGgnMb=2dYGQO4K36pQ9LEb8E4rT6S_VskLF+n=ndd0_kJr_g@mail.gmail.com' \
--to=austin@peloton-tech.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.