[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49pqicnapu.fsf@segfault.boston.devel.redhat.com>
Date: Tue, 04 Oct 2011 09:32:45 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: Christophe Saout <christophe@...ut.de>
Cc: device-mapper development <dm-devel@...hat.com>,
linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>
Subject: Re: [dm-devel] Block regression since 3.1-rc3
Christophe Saout <christophe@...ut.de> writes:
> Hi Jeff,
>
>> Anyway, it would help a great deal if you could retrigger the failure
>> and provide the full failure output. You can get that by issuing the
>> 'dmesg' command and redirecting it to a file.
>
> Oh, sorry, yes, there's a line missing.
>
> Line 323 is this one: BUG_ON(!rq->bio || rq->bio != rq->biotail);
>
> The bug is not specific to GFS2, I also get it when using an ext3 mount
> on that multipath storage pool when writing to a file.
Great, thanks! I tried ext3 and ext4 as well, and was unable to trigger
this problem. I setup a linear volume on top of a multipath device. Is
that the configuration you are using? Anyway, this may be enough to get
me on the right path...
Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists