Added the "P.S." about acpi=off
** Description changed:
This is about jaunty-netbook-remix Alpha 5 and 6 on a netbook (Atom
processor, internal ATA disk), booted from USB stick.
The following script (inspired by loop-aes testsuite) fails, usually within
20 iterations, upon one of the invocations of "losetup -d": ioctl: LOOP_CLR_FD:
Device or resource busy
#!/bin/bash
TLD=/dev/loop1
declare -i i=0
rm -f test-file*
dd if=/dev/zero of=test-file1 bs=1024 count=33
cp test-file1 test-file3
while true
do
echo "Iteration $((i+=1))"
/sbin/losetup /dev/loop1 test-file1
dd if=test-file3 of=/dev/loop1 bs=1024 count=33 conv=notrunc
if ! /sbin/losetup -d $TLD ; then exit 1 ; fi
/sbin/losetup /dev/loop1 test-file1
dd if=/dev/loop1 of=test-file4 bs=33792 count=1
if ! /sbin/losetup -d $TLD ; then exit 1 ; fi
done
When inserting "lsof /dev/loop1" or "fuser -m /dev/loop1" or "sleep 1"
before "losetup -d", the script runs endlessly, as expected. When using
the patched losetup of loop-aes (binary package loop-aes-utils as well
as hand-made patched v2.12r) with some form of encryption (e.g., XOR),
the above problem even arises when booting with kernel options "nosmp"
as well as with "single".
I'm reporting this as "linux" bug, not as "util-linux" one, as the above
script runs fine on the same hardware with a different distribution
(systemrescuecd).
+
+ P.S. losetup -d behaves as expected if I boot with "acpi=off".
--
losetup -d fails with "ioctl: LOOP_CLR_FD: Device or resource busy"
https://bugs.launchpad.net/bugs/345585
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
