Bug#754411: udev: loop mounts fail after 204-14 update

2014-10-27 Thread Peter Pöschl
notfound 754411 215-5+b1 thanks Hello Michael, Am Mo August 18 2014, 12:29:18 schrieb Michael Biebl: > Am 11.07.2014 13:42, schrieb Marco d'Itri: > > On Jul 11, Michael Biebl wrote: > >> This seems to be setup correctly afaics: > > It is, I can reproduce this on my system as well. > > > >> Is o

Bug#754411: udev: loop mounts fail after 204-14 update

2014-08-18 Thread Michael Biebl
Am 11.07.2014 13:42, schrieb Marco d'Itri: > On Jul 11, Michael Biebl wrote: > >> This seems to be setup correctly afaics: > It is, I can reproduce this on my system as well. > >> Is our mount version too old or should it work irregardless of the mount > It is: Peter, this particular issue is s

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-11 Thread Marco d'Itri
On Jul 11, Michael Biebl wrote: > This seems to be setup correctly afaics: It is, I can reproduce this on my system as well. > Is our mount version too old or should it work irregardless of the mount It is: # strace -e trace=file -o /tmp/mount-log mount -o loop /boot/grml/grml64-full_2013.02.i

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-11 Thread Kay Sievers
On Fri, Jul 11, 2014 at 1:35 PM, Michael Biebl wrote: > Am 11.07.2014 05:01, schrieb Kay Sievers: >> The logic in util-linux, libmount, losetup, ... tries to access >> /dev/loop-control which will block and trigger a kernel-side module >> auto-load. >> >> All that is needed is that tmpfiles have c

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-11 Thread Michael Biebl
Am 11.07.2014 05:01, schrieb Kay Sievers: > The logic in util-linux, libmount, losetup, ... tries to access > /dev/loop-control which will block and trigger a kernel-side module > auto-load. > > All that is needed is that tmpfiles have created the "dead" device > node to access from userspace, and

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-10 Thread Kay Sievers
On Thu, Jul 10, 2014 at 10:55 PM, Michael Biebl wrote: > Am 10.07.2014 22:02, schrieb Peter Poeschl: >> Package: udev >> Version: 204-14 >> Severity: important >> >> Dear Maintainer, >> >>* What led up to the situation? >> udev upgrade from 204-8 to 204-14 removed the file /etc/udev/links.conf

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-10 Thread Peter Pöschl
> Could you post the fstab entry for completeness sake. /home/xyz/wk/an_image.img /home/xyz/wk/mnt auto rw,user,noauto,loop 0 2 The corresponding output of mount is /home/xyz/wk/an_image.img on /home/xyz/wk/mnt type ext3 \ (rw,nosuid,nodev,noexec,relatime,data=ordered,user=xyz) -- To UNS

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-10 Thread Michael Biebl
Am 10.07.2014 22:02, schrieb Peter Poeschl: > Package: udev > Version: 204-14 > Severity: important > > Dear Maintainer, > >* What led up to the situation? > udev upgrade from 204-8 to 204-14 removed the file /etc/udev/links.conf. > >* What exactly did you do (or not do) that was effecti

Bug#754411: udev: loop mounts fail after 204-14 update

2014-07-10 Thread Michael Biebl
Am 10.07.2014 22:02, schrieb Peter Poeschl: > Package: udev > Version: 204-14 > Severity: important > > Dear Maintainer, > >* What led up to the situation? > udev upgrade from 204-8 to 204-14 removed the file /etc/udev/links.conf. > >* What exactly did you do (or not do) that was effecti