Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
*** Description of problem:
In the kernel source tree, "Documentation/filesystems/udf.txt" writes,
> The uid= and gid= options need a bit more explaining. They will
> accept a decimal numeric value and all inodes on that mount will then
> appear as belonging to that uid and gid. Mount options also accept
> the string "forget". The forget option causes all IDs to be written to
> disk as -1 which is a way of UDF standard to indicate that IDs are not
> supported for these files .
>
> For typical desktop use of removable media, you should set the ID to
> that of the interactively logged on user, and also specify the forget
> option. This way the interactive user will always see the files on
> the disk as belonging to him.
However, on RHEL7, the "uid=forget" option doesn't work; "mount" prints
> mount: failed to parse mount options
*** Version-Release number of selected component (if applicable):
util-linux-2.23.2-61.el7.x86_64
*** How reproducible:
Always.
*** Steps to Reproduce:
1. Plug in a USB flash drive for testing (note: data on it will be lost)
2. Make sure it's unmounted.
3. Erase all partitions with "fdisk"
4. zero out the first 1MB or so on the disk with "dd" or otherwise
5. Format the UDF filesystem:
LABEL=...
DEVICE=/dev/disk/by-id/usb-...
mkudffs \
--blocksize=512 \
--udfrev=0x0201 \
--media-type=hd \
--utf8 \
--lvid="${LABEL}" \
--vid="${LABEL}" \
"$DEVICE"
(The logical volume ID (--lvid) is shown by Windows, while the volume ID
("--vid") is used by Linux in the "/dev/disk/by-label/${VID}" pathname,
and also shown in the dmesg. It makes sense to set both IDs to the same
label, for getting the same label under Linux and Windows.)
6. Mount the flash disk:
MOUNTPOINT=/mnt/...
mount \
-t udf \
-o nosuid,nodev,noexec,uid=1000,uid=forget,gid=1000,gid=forget,umask=077 \
"$DEVICE" \
"$MOUNTPOINT"
*** Actual results:
Error message:
> mount: failed to parse mount options
*** Expected results:
The "mount" command should succeed, and "dmesg" should contain:
> UDF-fs: INFO Mounting volume '${LABEL}', timestamp ... (1000)
*** Additional info:
Already fixed in upstream v2.34 / v2.27.1, apparently:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801527https://github.com/karelzak/util-linux/commit/440a355a3d39
Thank you.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (util-linux bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:3963