On Wed, May 28, 2014 at 04:56:56PM +0200, Torbjørn wrote:
> On 05/28/2014 03:41 PM, Chris Mason wrote:
> >On 05/28/2014 01:53 AM, Torbjørn wrote:
> >
> >>It's actually a raid10 array of 11 dm-crypt devices.
> >>I'm able to read data from the array (accessing files), and also read
> >>directly from all the underlying dm-crypt devices using dd, if that's
> >>what you meant.
> >>
> >>I have not rebooted the system since that dmesg, so it's still stuck in
> >>the same state.
> >>I can keep it like that for some days. The system is not critical at all.
> >>
> >Thanks,
> >
> >Can you please capture the result of sysrq-t and sysrq-l? Maybe the IO
> >is stuck in a thread that isn't in the D state.
> >
> >-chris
> The output of sysrq-t was too much data for pastebin, will send both
> to you as attachments outside of the list.
Considering I have experienced this with with 3.15rc but wasn't able to
save a sysrq since my save file and syslog got lost, did you find out
anything from that?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
