Red Hat Bugzilla – Bug 129497
default mount vfat usb_storage gives ReadOnly without EROFS
Last modified: 2015-01-04 17:08:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040625
Description of problem:
Mounting a USB flash memory device "succeeds" but with ReadOnly
instead of ReadWrite, and no error code is given to /bin/mount.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Plug in USB flash memory device (such as 16MB CompUSA:
P: Vendor=09a6 ProdID=8001 Rev= 1.00
S: Manufacturer=AVC Technology Ltd.
S: Product=INSTANT Drive
2. # mount /dev/sda1 /mnt/sda1
Actual Results: mount "succeeds" (no error code in shell, and strace
execve("/bin/mount", ["mount", "/dev/sda1", "/mnt/sda1"], [/* 33
vars */]) = 0
mount("/dev/sda1", "/mnt/sda1", "vfat", 0xc0ed0000, 0) = 0
but actual mount is ReadOnly (no file can be created in the mounted-on
directory) and /var/log/messages shows:
Aug 9 11:20:12 fc3test1 kernel: FAT: codepage or iocharset option
Aug 9 11:20:12 fc3test1 kernel: File name can not access
proper (mounted as read-only)
which contains an incomplete and poorly-worded message.
Expected Results: Successful ReadWrite mount with default codepage
437 [as given in "man mount":
Sets the codepage for converting to shortname characters
and VFAT filesystems. By default, codepage 437 is used.
/bin/mount is from util-linux-2.12a-2 .
That was when booting with SELinux disabled via "selinux=0" on kernel
command line. When SELinux is in the targeted permissive mode, there
is an additional line in /var/log/messages:
Aug 9 10:23:42 fc3test1 kernel: SELinux: initialized (dev sda1, type
vfat), uses genfs_contexts
but the mount is still ReadOnly with no EROFS.
any better with the latest updates ?
Works properly using kernel-2.6.9-1.6_FC2, independent of SELinux in targeted
permissive mode, or turned off with "selinux=0" on boot command line.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.