[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47E6E8B4.5000602@tmr.com>
Date: Sun, 23 Mar 2008 19:33:08 -0400
From: Bill Davidsen <davidsen@....com>
To: Laurent Vivier <Laurent.Vivier@...l.net>
CC: axboe@...e.de, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org
Subject: Re: [PATCH][RESEND][v3] Modify loop device to be able to manage
partitions of the disk image
Laurent Vivier wrote:
> Le mercredi 19 mars 2008 à 16:24 -0400, Bill Davidsen a écrit :
>> Laurent Vivier wrote:
>>> v3 is an updated version of v2, replacing a "%d" by a "%lu".
>>>
>>> This patch allows to use loop device with partitionned disk image.
>>>
>> How does this compare in overhead to using nbd?
>
> What do you mean ?
>
> NBD doesn't manage partitions... but I also have a patch to do that.
> NBD implies an NBD server and an NBD client in userspace, so loop is
> better when disk image is in a raw format.
>
Actually the usual partitioning tools will create partitions on nbd
volumes, but without inodes they are not useful. I thought we used to
have that working, to work on virtual machine "disk" files which were
partitioned, but that was several years ago and I could be
misremembering. I did use fdisk on an nbd device before I asked about
overhead, but I didn't try to use the partitions.
In any case, if you have code to make nbd partitions work in a currently
useful way, that might be useful for keeping disk images handy for
mount. The kvm copy on write might let the fresh install image be shared
and VMs customize as needed.
--
Bill Davidsen <davidsen@....com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
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