Bug 78552 - Invalid argument error when attempting to use des option for encryption (losetup)
Invalid argument error when attempting to use des option for encryption (lose...
Status: CLOSED DUPLICATE of bug 56698
Product: Red Hat Linux
Classification: Retired
Component: util-linux (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-11-25 13:29 EST by Michael Lee Yohe
Modified: 2007-04-18 12:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-03 15:19:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Lee Yohe 2002-11-25 13:29:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
# dd if=/dev/zero of=encrypted.img bs=1k count=10000
10000+0 records in
10000+0 records out
# ls -laF
total 10024
drwx------    2 root     root         4096 Nov 25 12:25 ./
drwxr-xr-x    5 root     root         4096 Nov 25 12:25 ../
-rw-r--r--    1 root     root     10240000 Nov 25 12:25 encrypted.img
# losetup -e des /dev/loop0 /opt/secure/encrypted.img 
Init (up to 16 hex digits): 
ioctl: LOOP_SET_STATUS: Invalid argument

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create a file (for loopback setup)
2. attempt to setup encryption on that file for loopback device

Actual Results:  ioctl: LOOP_SET_STATUS: Invalid argument

Expected Results:  losetup should not have had a problem.

Additional info:
Comment 1 Michael Lee Yohe 2002-12-03 15:19:06 EST
Elliot (and public) - any progress in determining whether it is an isolated
issue?  I've been able to duplicate this on two different Red Hat Linux 8.0 boxes.
Comment 2 Elliot Lee 2002-12-03 17:17:24 EST
Sorry for the delay. Please read bug #56698 for the (stalled) status of a fix.

*** This bug has been marked as a duplicate of 56698 ***

Note You need to log in before you can comment on or make changes to this bug.