NTFS 3G Unable to automount with the new kernel

Jonathan Berry berryja at gmail.com
Sun Jul 29 01:55:34 UTC 2007


On 7/28/07, Ian Malone <ibmalone at gmail.com> wrote:
> On 28/07/07, Antti J. Huhtala <ahuhtal4 at welho.com> wrote:
> > Sat, 28 Jul 2007 16:28:41 +0530, Rogue wrote:
> >
> > > Hi all,
> > >
> > > I have been noticing that the ntfs mounts are no longer auto-mounting
> > > with the new kernel. I have filed bug 249943 regarding the same. Would
> > > appreciate if others observing the same problem could provide further
> > > information in the bug.
> > >
> > > thanks,
> > > Rogue
> > >
> > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249943
> >
> > I looked at bugzilla and noted your bug report was about external USB
> > drives and i386. I added my similar experience concerning hard disk NTFS
> > partitions and x86_64. Automounting stopped on 25th July, the date
> > selinux-policy and selinux-policy-targeted packages were updated here.
> > Then I was still using 2.6.21-1.3228.fc7 kernel, but the same thing (no
> > automount) is still true now that I'm using 2.6.22.1-33.fc7 kernel.
> >
>
> Pretty sure it's selinux related, as the following appears in
> my dmesg corresponding to the failure to mount at startup
> and double clicking the drives in the ntfs configuration
> tool mounts them with no trouble.  Will add to the bug report
> when I get a chance.
>
> audit(1185632349.536:4): avc:  denied  { search } for  pid=1548
> comm="mount.ntfs-3g" name="media" dev=dm-0 ino=163841
> scontext=system_u:sys
> tem_r:mount_ntfs_t:s0 tcontext=system_u:object_r:mnt_t:s0 tclass=dir
> audit(1185632349.536:5): avc:  denied  { search } for  pid=1557
> comm="mount.ntfs-3g" name="media" dev=dm-0 ino=163841
> scontext=system_u:sys
> tem_r:mount_ntfs_t:s0 tcontext=system_u:object_r:mnt_t:s0 tclass=dir

I am seeing the same thing, x86_64 with external USB hard drive as
well as internal hard drive Windows partition.  SELinux troubleshooter
indicates that SELinux is disallowing mount.ntfs-3g from accessing
/media (brilliant!).  Found this bug report suggesting that the issue
has been fixed in an updated package (that is not quite available
yet):
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249695

Jonathan




More information about the fedora-list mailing list