On Fri, Jul 31, 2009 at 10:54:45PM +0200, Michael Buesch wrote:
> The following oops happened while doing an mke2fs -j on a luks mapping.
> I think (I'm not entirely sure) that it was triggered by running the "sync"
> command
> simultaneously to the mke2fs. Both sync and mke2fs are stuck in D stat
The following oops happened while doing an mke2fs -j on a luks mapping.
I think (I'm not entirely sure) that it was triggered by running the "sync"
command
simultaneously to the mke2fs. Both sync and mke2fs are stuck in D state after
the oops.
root 10916 0.4 0.0 1888 460 ?D<
