On Wed, Sep 16, 2009 at 12:57:22PM -0500, Steven Pratt wrote: > Steven Pratt wrote: > >Chris Mason wrote: > >>On Mon, Sep 14, 2009 at 04:41:48PM -0500, Steven Pratt wrote: > >>>Only bit of bad news is I did get one error that crashed the system > >>>on single threaded nocow run. So that data point is missing. > >>>Output below: > >> > >>I hope I've got this fixed. If you pull from the master branch of > >>btrfs-unstable there are fixes for async thread races. The single > >>patch I sent before is included, but not enough. > >Glad you said that. Keeps me from sending the email that said the > >patch didn't help :-) > > > >Steve > Well, still getting oopses even with new code. > > Lots of: > Sep 16 11:07:27 btrfs1 kernel: [ 1862.942754] BUG: soft lockup - > CPU#10 stuck for 61s! [btrfs-endio-1:30250] > Sep 16 11:07:27 btrfs1 kernel: [ 1862.942754] Pid: 30250, comm: > btrfs-endio-1 Not tainted 2.6.31-autokern1 #1 IBM x3950-[88726RU]- > Sep 16 11:07:27 btrfs1 kernel: [ 1862.942754] RIP: > 0010:[<ffffffff81153920>] [<ffffffff81153920>] crc32c+0x20/0x26
If I'm reading this right, you've got a softlockup in crc32c? Something has gone really wrong here. Are you reusing datasets from old runs? -chris -- 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
