NFS exports file errors
I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot Aug 29 14:20:41 host mountd[1587]: can't export /var Aug 29 14:20:41 host mountd[1587]: bad exports list line /var -ro -maproot Aug 29 14:20:41 host mountd[1587]: can't export /home Aug 29 14:20:41 host mountd[1587]: bad exports list line /home -ro -maproot Aug 29 14:20:44 host mountd[1587]: mount request denied from 192.x.x.x I googled on that error and the only thing I could find was if there were simlinks on the exports file, which there isn't...I built the server with the following file systems: / /usr /var /home Note that there is no error for the root volume.../usr and /var will actually mount fine, despite the errors, but /home will not...I keep getting a permission denied error. Ideas? Thanks. James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS exports file errors
In response to [EMAIL PROTECTED]: I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot You have to map root to something ... i.e. /usr -ro -maproot root -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS exports file errors
On Tue, 29 Aug 2006, Bill Moran wrote: In response to [EMAIL PROTECTED]: I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot You have to map root to something ... i.e. /usr -ro -maproot root I did, using this sytax, like I always have: / -ro -maproot=0 192.x.x.1 /usr -ro -maproot=0 root 192.x.x.1 /var -ro -maproot=0 root 192.x.x.1 /home -ro -maproot=0 root 192.x.x.1 where 192.x.x.1 is the IP of the only host I want to have access. I tried switching to your syntax (taking out the -0 and putting in root but I get the same results... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS exports file errors
On Tue, 29 Aug 2006, Bill Moran wrote: In response to [EMAIL PROTECTED]: I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot You have to map root to something ... i.e. /usr -ro -maproot root I did, using this sytax, like I always have: / -ro -maproot=0 192.x.x.1 /usr -ro -maproot=0 root 192.x.x.1 /var -ro -maproot=0 root 192.x.x.1 /home -ro -maproot=0 root 192.x.x.1 where 192.x.x.1 is the IP of the only host I want to have access. I tried switching to your syntax (taking out the -0 and putting in root but I get the same results... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am i thought the syntax was maproot=root, thus, / -ro -maproot=root 192.x.x.1 /usr -ro -maproot=root 192.x.x.1 /var -ro -maproot=root 192.x.x.1 /home -ro -maproot=root 192.x.x.1 if that doesnt work, then i would remove the -ro, out of wondering if it could be colliding with the maproot=root. hth, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS exports file errors
In response to [EMAIL PROTECTED]: On Tue, 29 Aug 2006, Bill Moran wrote: In response to [EMAIL PROTECTED]: I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot You have to map root to something ... i.e. /usr -ro -maproot root I did, using this sytax, like I always have: / -ro -maproot=0 192.x.x.1 /usr -ro -maproot=0 root 192.x.x.1 /var -ro -maproot=0 root 192.x.x.1 /home -ro -maproot=0 root 192.x.x.1 where 192.x.x.1 is the IP of the only host I want to have access. I tried switching to your syntax (taking out the -0 and putting in root but I get the same results... My mistake -- I mistook the errors in your original post to be the entire exports line. What do your physical mounts look like again? In my experience, if any one exports line is wrong, the whole file fails. Try commenting out all but one of the lines and seeing if the problem goes away. With clever commenting, you can then narrow it down. In the lines above, root will be taken as a machine name. While that's unlikely to be the cause of your error, I don't expect it's what you want. The exports man page specifically states that maproot can specify either a username or a uid. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS exports file errors
On Tue, 29 Aug 2006, Jonathan Horne wrote: On Tue, 29 Aug 2006, Bill Moran wrote: In response to [EMAIL PROTECTED]: I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot You have to map root to something ... i.e. /usr -ro -maproot root I did, using this sytax, like I always have: / -ro -maproot=0 192.x.x.1 /usr -ro -maproot=0 root 192.x.x.1 /var -ro -maproot=0 root 192.x.x.1 /home -ro -maproot=0 root 192.x.x.1 where 192.x.x.1 is the IP of the only host I want to have access. I tried switching to your syntax (taking out the -0 and putting in root but I get the same results... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am i thought the syntax was maproot=root, thus, / -ro -maproot=root 192.x.x.1 /usr -ro -maproot=root 192.x.x.1 /var -ro -maproot=root 192.x.x.1 /home -ro -maproot=root 192.x.x.1 if that doesnt work, then i would remove the -ro, out of wondering if it could be colliding with the maproot=root. According to the man pages and the FreeBSD manual (years old) either sytax should work (numeric UID or username), but I tried it anyway, to no avail. I just did a mount on the server, and here's what I have: su-2.05b# mount /dev/ad0s1a on / (ufs, NFS exported, local) devfs on /dev (devfs, local) /dev/ad0s1f on /home (ufs, local, soft-updates) /dev/ad0s1d on /usr (ufs, NFS exported, local, soft-updates) /dev/ad0s1e on /var (ufs, NFS exported, local, soft-updates) So, in spite of the errors for the /usr and /var file system, they get exported (and I can access them from the client), the /home FS is NOT exported and I cannot access it. The / file system has no errors and is fine... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS exports file errors
On Tue, 29 Aug 2006 [EMAIL PROTECTED] wrote: On Tue, 29 Aug 2006, Jonathan Horne wrote: On Tue, 29 Aug 2006, Bill Moran wrote: In response to [EMAIL PROTECTED]: I'm getting the following errors when trying to mount volumes via NFS between to FBSD 6.1-STABLE machines: Aug 29 14:20:41 host mountd[1587]: can't export /usr Aug 29 14:20:41 host mountd[1587]: bad exports list line /usr -ro -maproot You have to map root to something ... i.e. /usr -ro -maproot root I did, using this sytax, like I always have: / -ro -maproot=0 192.x.x.1 /usr -ro -maproot=0 root 192.x.x.1 /var -ro -maproot=0 root 192.x.x.1 /home -ro -maproot=0 root 192.x.x.1 where 192.x.x.1 is the IP of the only host I want to have access. I tried switching to your syntax (taking out the -0 and putting in root but I get the same results... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am i thought the syntax was maproot=root, thus, / -ro -maproot=root 192.x.x.1 /usr -ro -maproot=root 192.x.x.1 /var -ro -maproot=root 192.x.x.1 /home -ro -maproot=root 192.x.x.1 if that doesnt work, then i would remove the -ro, out of wondering if it could be colliding with the maproot=root. According to the man pages and the FreeBSD manual (years old) either sytax should work (numeric UID or username), but I tried it anyway, to no avail. I just did a mount on the server, and here's what I have: su-2.05b# mount /dev/ad0s1a on / (ufs, NFS exported, local) devfs on /dev (devfs, local) /dev/ad0s1f on /home (ufs, local, soft-updates) /dev/ad0s1d on /usr (ufs, NFS exported, local, soft-updates) /dev/ad0s1e on /var (ufs, NFS exported, local, soft-updates) So, in spite of the errors for the /usr and /var file system, they get exported (and I can access them from the client), the /home FS is NOT exported and I cannot access it. The / file system has no errors and is fine... Replying to my own post...I've since tried stopping and restarting rpcbind, nfsd and mountd on the NFS server...I tried binding rpcbind and nfsd to the main IP address of that server (it has multiple). Now, I get the errors for all file system but root and can only mount the remote root file system, not /usr, /var or /home. I killed portsentry on both client and server before starting, since I noticed rpcbind was complaining about an address already in use (it went away after I killed portsentry and restarted it all). What really makes no sense is that it is functioning partly...the root fs mounts fine.../usr and /var did earlier, but no longer do. It makes no sense to me. James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]