Hello!
Given that there was no followup on my last quite verbose mail to
this bug report where I investigated the reported problem I have
to conclude that there is nothing left to fix and thus closing
the bug report.
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to
On Sat, Aug 02, 2014 at 12:33:53PM +0200, Andreas Henriksson wrote:
Hello!
Given that there was no followup on my last quite verbose mail to
this bug report where I investigated the reported problem I have
to conclude that there is nothing left to fix and thus closing
the bug report.
I
Hello ael!
On Sat, Aug 02, 2014 at 01:03:07PM +0100, ael wrote:
[...]
I don't have the original report on screen just now, but I thought
that it amounted to a bug in the man page.
The man page contains all the relevant information, so the bug
would in that case be that it's too verbose and
Control: tags -1 + confirmed
Hello!
I can confirm the described behaviour.
I can reproduce it the official debian kernel.
ii linux-image-3.14-1-amd64 3.14.7-1 amd64Linux 3.14 for 64-bit PCs
The problem manifests when assigning a loop device explicitly.
ie. mount -v -o
Package: mount
Version: 2.20.1-5.5
Severity: normal
Loop mounting has started to fail. Suspect this might be a kernel
change/bug, but reporting against mount since this is where the problem
is manifest.
Example:
# losetup -f
/dev/loop0
# export f=1; mount -v -o loop=/dev/loop0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/14/2013 05:52 AM, ael wrote:
# losetup -f /dev/loop0
# export f=1; mount -v -o loop=/dev/loop0
debian-testing-source-DVD-${f}old.iso /loopmnt1 mount: enabling
autoclear loopdev flag mount: going to use the loop device
/dev/loop0 mount:
6 matches
Mail list logo
