Skip to contentSkip to conversation

Allow NBD to be used locally

PATCH [email protected] 3 participants 3 messages Feb 2, 2008 – Feb 3, 2008

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines

How will that work? Fuse makes up a filesystem - not helpful if you have a raw disk without a known fs to mount.

take zfs-fuse or ntfs-3g for example.
you have a blockdevice or backing-file containing data structures and fuse makes those show up as a filesystem. i think vmware-mount is not different here.

Quoted 1 line

This still does not account for compressed disk images, for example.

unfortunately, not

Quoted 14 lines · On Feb 2 2008 15:40, [email protected] wrote:
Quoted 7 lines
Quoted 4 lines

In fact, VMware uses local nbd today for its vmware-loop helper utility, most likely because of the above-mentioned reasons. (Though it quite often hung last time I tried.)

seems this will go away. recent vmware versions (e.g. server 2.0 beta) have a fuse based replacement for that.

How will that work? Fuse makes up a filesystem - not helpful if you have a raw disk without a known fs to mount.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

So what we have is non-linearity -- LBA 22 comes after LBA 40 -- loop does not deal with that.

maybe dm-loop does? http://sources.redhat.com/lvm2/wiki/DMLoop

This still does not account for compressed disk images, for example.

________________________________________________________
Bis 50 MB Dateianhänge? Kein Problem!
http://www.digitaledienste.web.de/freemail/club/lp/?lp=7

#1 lore raw
Quoted 7 lines · On Feb 2 2008 18:31, [email protected] wrote:
Quoted 3 lines

How will that work? Fuse makes up a filesystem - not helpful if you have a raw disk without a known fs to mount.

take zfs-fuse or ntfs-3g for example.
you have a blockdevice or backing-file containing data structures and fuse makes those show up as a filesystem. i think vmware-mount is not different here.

vmware-mount IS different, it provides the _block_ device, which is then mounted through the usual mount(2) mechanism (if there is a filesystem driver for it).

#2 lore raw

Whoops, only hit "Reply" on the first email, sorry Jan.

Quoted 5 lines · Jan Engelhardt
Quoted 4 lines · On Feb 2 2008 18:31, [email protected] wrote:
Quoted 3 lines

How will that work? Fuse makes up a filesystem - not helpful if you have a raw disk without a known fs to mount.

Quoted 7 lines
Quoted 3 lines

take zfs-fuse or ntfs-3g for example.
you have a blockdevice or backing-file containing data structures and fuse makes those show up as a filesystem. i think vmware-mount is not different here.

vmware-mount IS different, it provides the _block_ device, which is then mounted through the usual mount(2) mechanism (if there is a filesystem driver for it).

As far as I can tell, vmware-mount should be re-implemented as a little perl script around "dmsetup" and/or "losetup", possibly with "dm-userspace" patched into the kernel to allow you to handle non-mapped blocks in your userspace daemon when somebody tries to access them. If you don't need that ability then straight dm-loop and dm-linear will work.

Cheers,
Kyle Moffett