I can't reproduce the problem. The sequence of comands that failed
repeatedly are are now working as I expect. The cheap'o thumdrive is
indeed slow. mkfs took just under 15min and didn't generate the journal
entry. The device busy message from cryptsetup is gone.
Between the bugreport and re-t
Why do you think this is a e2fsprogs bug?
You didn't say what kind of usb drive this was, but if it was a USB
thumb drive, the 120 second stall was probably because USB thumb drives was
slow.
Also, mke2fs must have completed if the shell script had gotten to the
"cryptsetup close prn" command.
Package: e2fsprogs
Version: 1.42.13-1
Severity: normal
File: /sbin/mke2fs
While attempting to setup encrypted thumb drive saw the following weirdness:
shell code fragment
dd if=/dev/zero of=/dev/sdi bs=4096 count=10
cryptsetup luksFormat /dev/sdi
cryptsetup open /dev/sdi prn
mkfs
3 matches
Mail list logo
