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.
DescriptionOrion Poplawski
2018-09-25 20:46:48 UTC
Description of problem:
# mkfs -t exfat /dev/sdd1
mkexfatfs 1.3.0
Creating... done.
Flushing... done.
File system created successfully.
# mount /dev/sdd1 /mnt
mount: /dev/sdd1: more filesystems detected. This should not happen,
use -t <type> to explicitly specify the filesystem type or
use wipefs(8) to clean up the device.
# lsblk --fs
NAME FSTYPE LABEL UUID
sdd
└─sdd1
# exfatlabel /dev/sdd1 'data'
# lsblk --fs
NAME FSTYPE LABEL UUID
sdd
└─sdd1 exfat data 0125-EC34
Version-Release number of selected component (if applicable):
util-linux-2.23.2-58.el7.x86_64
This works with Fedora 28 and util-linux-2.32.1-1.fc28.x86_64:
# lsblk --fs
NAME FSTYPE LABEL UUID
sdb
└─sdb1 exfat 0125-EC34
according to https://github.com/relan/exfat/issues/75, stock util-linux 2.23.2 works as well.
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, 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-2019:2252
Description of problem: # mkfs -t exfat /dev/sdd1 mkexfatfs 1.3.0 Creating... done. Flushing... done. File system created successfully. # mount /dev/sdd1 /mnt mount: /dev/sdd1: more filesystems detected. This should not happen, use -t <type> to explicitly specify the filesystem type or use wipefs(8) to clean up the device. # lsblk --fs NAME FSTYPE LABEL UUID sdd └─sdd1 # exfatlabel /dev/sdd1 'data' # lsblk --fs NAME FSTYPE LABEL UUID sdd └─sdd1 exfat data 0125-EC34 Version-Release number of selected component (if applicable): util-linux-2.23.2-58.el7.x86_64 This works with Fedora 28 and util-linux-2.32.1-1.fc28.x86_64: # lsblk --fs NAME FSTYPE LABEL UUID sdb └─sdb1 exfat 0125-EC34 according to https://github.com/relan/exfat/issues/75, stock util-linux 2.23.2 works as well.