Bug 236665 - distro independant client fails to nfs mount ntfs-3g shares
Summary: distro independant client fails to nfs mount ntfs-3g shares
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
(Show other bugs)
Version: 6
Hardware: i386 Linux
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-17 01:52 UTC by Sean Buehler
Modified: 2008-04-04 12:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 12:40:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Sean Buehler 2007-04-17 01:52:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.6 (like Gecko)

Description of problem:
NFS shares of a ntfs-3g filesystem fail to mount on various clients.

Fedora Core release 6 (Zod)

Gentoo Base System release 1.12.9
Fedora Core release 6 (Zod)

Attempting to mount the nfs share shows successful on the server yet the 
clients give permission denied.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Mount NTFS-3G parition, set up in /etc/exports, reset exports
2. Attempt to mount nfs share externaly 

Actual Results:
reason given by server: Permission denied

Yet the server shows successful authentication

Expected Results:
successful nfs mount 

Additional info:

Comment 1 Steve Dickson 2007-04-25 18:42:10 UTC
Is there any errors being logged in /var/log/messages?

Comment 2 Sean Buehler 2007-04-28 05:21:58 UTC

dell skiingsean # mount -t nfs ./sean
mount: failed, reason given by server: Permission denied


Only relevant line in messages:

Apr 28 00:18:29 home mountd[14244]: authenticated mount request from for /sean (/sean)

Comment 3 Bug Zapper 2008-04-04 06:52:23 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Note You need to log in before you can comment on or make changes to this bug.