[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1317740769.25998.11.camel@localhost>
Date: Tue, 04 Oct 2011 17:06:09 +0200
From: Christophe Saout <christophe@...ut.de>
To: Jeff Moyer <jmoyer@...hat.com>
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
Hi Jeff,
> > 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...
Yes - the device-mapper tables looks like:
vserv81:/root # dmsetup table RAID_A-test.root
0 20971520 linear 253:6 384
(this is one the FS which causes the crash when mounting via ext3)
And 253:6 is the multipath device:
vserv81:/root # dmsetup table 3600d023100065bef0000000009f337c0
0 15626018816 multipath 0 0 2 1 round-robin 0 1 1 8:16 1000 round-robin 0 1 1 8:48 1000
And 8:16, 8:48 are two qla2xxx FC ports.
Cheers,
Christophe
--
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