[Mageia-dev] Any progress on the NFS mount problem? - One step further
AL13N
alien at rmail.be
Mon Oct 1 22:34:54 CEST 2012
Op maandag 1 oktober 2012 20:43:26 schreef Anne Wilson:
> On 01/10/12 20:16, Anne Wilson wrote:
> >> Argh!! re-reading those lines, it's giving the IP address
> >> instead of the mount point.
> >
> > Garbage. Ignore.
> >
> > I've obviously stared at this too long and I'm not making any
> > sense at all now.
>
> For a moment I thought I had cracked it. I hand edited the lines,
> took out the '/export' since that seemed to be handled as yet another
> export, took out the IP address (my attempts in the GUI at confining
> it to the LAN) and put '*' in front of the bracketed options.
>
> Back on the laptop 'mount -t nfs 192.168.0.40:/ /mnt/borg2_Data1'
> gives to errors - and I was just about to cheer, when I realised that
> Dolphin still couldn't see any files. There are no error messages or
> anything at first, then the popup box told me that /mnt/borg2_Data1
> was either busy or already mounted (can't remember the exact words).
>
> That was quickly replaced by "An error occurred while accessing 'home
> on 192.168.0.40', the system responded: mount.nfs: access denied by
> server while mounting 192.168.0.40:/home
>
> I edited the lines to
>
> [root at tosh ~]# mount -t nfs 192.168.0.40:/Data1 /mnt/borg2_Data1
> [root at tosh ~]# mount -t nfs 192.168.0.40:/home/anne /mnt/borg2_home
>
> but get the same errors.
>
> Hah! suddenly I have /home/anne/ on 192.168.0.40 and it's readable.
>
> That's obviously an improvement, but I still need the Data1 directory
> tree. Root can umount it. It shows every sign of being mounted, yet
> I can't read any of it. All the data there is owned anne:users so it
> shouldn't be a permissions issue.
user ids and names still need to be the same on both systems. (or somehow
mapped; which is what v4 has more than v3; but i never used v4)
also, root typically has no access to nfs exports, you need to be regular
user, (unless you specify the root_no_squash options, or similar)
More information about the Mageia-dev
mailing list