[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D2FFBED.6010406@ce.jp.nec.com>
Date: Fri, 14 Jan 2011 16:31:57 +0900
From: "Jun'ichi Nomura" <j-nomura@...jp.nec.com>
To: Milan Broz <mbroz@...hat.com>, Tejun Heo <tj@...nel.org>
CC: Jens Axboe <axboe@...nel.dk>, Valdis.Kletnieks@...edu,
Alexander Viro <viro@...iv.linux.org.uk>,
Neil Brown <neilb@...e.de>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-raid@...r.kernel.org,
device-mapper development <dm-devel@...hat.com>,
Kay Sievers <kay.sievers@...y.org>,
Alasdair G Kergon <agk@...hat.com>
Subject: Re: [PATCH] block: restore multiple bd_link_disk_holder() support
Hi,
On 01/14/11 03:42, Milan Broz wrote:
>> Milan, Jun, can you guys please verify this works correctly for the
>> multi holder dm case? Thank you.
>
> Hi,
>
> unfortunately not. And the problem is much worse,
> it breaks lvm resize operation completely.
For quick testing, try this:
("/dev/sdf" can be other block device.
"testA" and "testB" can be other dm names which aren't used in
your machine.)
# echo "0 10 linear /dev/sdf 0" | dmsetup create testA
# echo "0 10 linear /dev/sdf 10" | dmsetup create testB
(at this point, /dev/sdf has multiple holders)
# echo "0 20 linear /dev/sdf 10" | dmsetup load testB
(at this point, /dev/mapper/testB has 2 claims on /dev/sdf)
# dmsetup resume testB
(/dev/mapper/testB has 1 claim on /dev/sdf)
# dmsetup remove testA
# dmsetup remove testB
Thanks,
--
Jun'ichi Nomura, NEC Corporation
--
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