[Buildd-tools-devel] Bug#475515: Bug#475515: [schroot] impossible to use loopback mounts

[Emanuele Aina]

Roger Leigh investigò:

> > schroot checks in schroot-releaselock/schroot-releaselock-main.cc that
> > the configured block device is really a block device, failing if not so:
> > 
> >   if (!S_ISBLK(statbuf.st_mode))
> >     throw error(this->opts->device, DEVICE_NOTBLOCK);
> > 
> > This breaks for me as I'd like to mount a loopback filesystem by specifying
> > "-o loop" in the mount options, so I'm currently doing the mount manually.
> 
> Please could you provide some details about your schroot configuration and what
> you are trying to do?
> 
> As far as I understand, the loopback mounts use /dev/loopn, which should
> be real block devices.

Yes, but I'd like to specify the file containing the filesystem directly
as block-device, avoiding the preliminary setting up of a /dev/loopN
device with losetup, just like "mount" does with the "-o loop" option.

So, if I have the filesystem in a file, say /srv/filesystems/devel.img,
I'd like to use this configuration:

[devel]
type=block-device
device=/srv/filesystems/devel.img
mount-options=-o loop

and let schroot just call "mount /srv/filesystems/devel.img -o loop
${DEST}" without checking if /srv/filesystems/devel.img is a block
device.

Currently I have to manually mount the filesystem using a 'directory'
chroot type or I have to use losetup to add the /dev/loopN device before
calling schroot.

Thanks for the quick reply!

-- 
Emanuele Aina
http://initd.org