Red Hat Bugzilla – Bug 141159
RHEL4 Beta 2 Write permission is denied on automounted fs- USB ext hd or Mem Key
Last modified: 2013-03-13 00:47:16 EDT
Description of problem:
(This happens on i686 and x86_64)
Under X Windows, a USB external hard drive is automounted.
The user can not create a directory on the file structure; the error
message is "Permission denied".
Seeing how that device is automounted in /etc/fstab when X Windows is
running, we can create an entry for a USB Memory Key and test that
We get the same problem. The write permission to create a directory
generates "Permission denied."
If however we mount the devices to user created directories and do
not let the devices be automounted, we do not have write permission
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Tested on PE2800 with RHEL 4 Beta 2 x86_64 and PE700 with RHEL 4 Beta
Be in run level 5 with X Windows running.
Use a USB external hard drive with a partition and ext2 or ext3 file
system on it.
Connect the USB external hard drive.
Check that it automounts.
Go to the autmounted directory (/media/usbdisk)
You will get a permission denied message.
If you unmount it and make a mount point then mount it manually,
creating a directory on the device does not generate a write
permission denied message, it just works.
Use a USB Memory Key which has an ext2 or ext3 file system on it.
You can insert a USB Memory key, but it does not automount.
You can manually mount it and then make a directory on the device
without any 'Permission denied" messages.
Next, unmount it and remove it.
Then create an entry for it in /etc/fstab, the next time you insert
it, it automounts it at /media/usbdisk1. You will then get a
permission denied message when trying to do mkdir boo
No write permission for drive.
Disk should be writable.
I'll try to get my hands on the fstab that was used here.
What version of selinux-policy-targeted are you running?
I have uploaded the latest to my peoples page. Please try this and see if it
resolved your problems.
It was running selinux-policy-targeted-1.17.30-2.11.noarch.rpm.
2.35 seems to have fixed the problem.
Will this be included in the release?
Yes, I took that RPM from the current build of RHEL. Thanks.
Verified fixed. Thanks.