'Twas brillig, and AL13N at 02/10/12 11:17 did gyre and gimble:
>> 'Twas brillig, and Guillaume Rousse at 01/10/12 18:45 did gyre and gimble:
> Last, you'd better use autofs to mount those filesystems on
> demand, rather than hardcoding them in /etc/fstab, which avoid to
> relies on ser
Le 02/10/2012 12:18, AL13N a écrit :
FWIW: my mga2 server and mga1 chrooted client don't need fsid=0 . but then
i'm using nfsver=3; don't want to be using nfsv4
Why ?
--
BOFH excuse #104:
backup tape overwritten with copy of system manager's favourite CD
> 'Twas brillig, and Guillaume Rousse at 01/10/12 21:41 did gyre and gimble:
>> With NFSv4, the server remaps its actual filesystem (/home, for
>> instance) in a pseudo-filesystem, which is seen by clients as a root
>> filesystem (/ here). Consider it as some kind of implicit chroot.
>>
>> With ear
> 'Twas brillig, and Guillaume Rousse at 01/10/12 18:45 did gyre and gimble:
Last, you'd better use autofs to mount those filesystems on
demand, rather than hardcoding them in /etc/fstab, which avoid to
relies on server availability during the boot.
>>>
>>> Replace nfs with autofs in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/12 02:31, Colin Guthrie wrote:
> 'Twas brillig, and Guillaume Rousse at 01/10/12 21:41 did gyre and
> gimble:
>> With NFSv4, the server remaps its actual filesystem (/home, for
>> instance) in a pseudo-filesystem, which is seen by clients as
'Twas brillig, and Guillaume Rousse at 01/10/12 21:41 did gyre and gimble:
> With NFSv4, the server remaps its actual filesystem (/home, for
> instance) in a pseudo-filesystem, which is seen by clients as a root
> filesystem (/ here). Consider it as some kind of implicit chroot.
>
> With earlier i
'Twas brillig, and Guillaume Rousse at 01/10/12 18:45 did gyre and gimble:
>>> Last, you'd better use autofs to mount those filesystems on
>>> demand, rather than hardcoding them in /etc/fstab, which avoid to
>>> relies on server availability during the boot.
>>
>> Replace nfs with autofs in those
Le 01/10/2012 22:34, AL13N a écrit :
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 owne
Le 01/10/2012 21:55, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
GOT IT!!!
Remembered that you said it would mount as /, to which I don't have
access of course.
That's not exactly what I said :)
With old NFS versions (2/3), the server exports an actual filesystem
(/ho
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
GOT IT!!!
Remembered that you said it would mount as /, to which I don't have
access of course. I removed 'fsid=0', restarted, and all is well. I
can see all my data!
Thanks for your patience.
Anne
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 mom
> 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.
Anne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/12 19:02, Guillaume Rousse wrote:
> Le 01/10/2012 17:46, Anne Wilson a écrit :
>> The good news (after rebooting server and client) that the server
>> now is running nfs and nfs_acl
> Over IPv4, or over IPv6 only as previously ?
>
>> The less
Le 01/10/2012 17:46, Anne Wilson a écrit :
The good news (after rebooting server and client) that the server now
is running nfs and nfs_acl
Over IPv4, or over IPv6 only as previously ?
The less good news is that the laptop still can't mount
My crystall ball is empty... what is the output of a
Le 01/10/2012 19:45, Guillaume Rousse a écrit :
Also, take cares, with NFSv4, you don't mount the actual server
filepath, but the exported filepath: the root filesystem (the one with
fsid=0) will be available as /, whatever its actual path.
Forget about it, configuration handling has evolved a bi
Le 01/10/2012 17:26, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 01 Oct 2012 13:18:36 Guillaume Rousse wrote:
Le 22/09/2012 21:16, Anne Wilson a écrit :
udp0 0 *:nfs *:*
unfsd
Ouch... You're running an obsolete alternative
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/12 12:18, Guillaume Rousse wrote:
> Le 22/09/2012 21:16, Anne Wilson a écrit :
>> udp0 0 *:nfs *:* unfsd
> Ouch... You're running an obsolete alternative nfs server. You
> should uninstall the unfs3 package,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 01 Oct 2012 13:18:36 Guillaume Rousse wrote:
> Le 22/09/2012 21:16, Anne Wilson a écrit :
>> udp0 0 *:nfs *:*
>>
>> unfsd
>
> Ouch... You're running an obsolete alternative nfs server. You
> should uninsta
Le 22/09/2012 21:16, Anne Wilson a écrit :
udp0 0 *:nfs *:*
unfsd
Ouch... You're running an obsolete alternative nfs server. You should
uninstall the unfs3 package, and this package should get removed from
the distribution.
To summarize, h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/09/12 08:26, Thierry Vignaud wrote:
> On 23 September 2012 11:18, Anne Wilson
> wrote:
Package nfs-utils blahblah is already installed
>>> nfs-common service, sorry.
>>>
>> That may well point to the problem, though I've no idea what
>> ne
On 23 September 2012 11:18, Anne Wilson wrote:
>>> Package nfs-utils blahblah is already installed
>> nfs-common service, sorry.
>>
> That may well point to the problem, though I've no idea what needs
> doing to solve it:
>
> service nfs-commons status
> Cannot find nfs-commons service
that's "nf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/09/12 07:04, Guillaume Rousse wrote:
> Le 22/09/2012 20:53, Anne Wilson a écrit :
>> and if
>>> rpc.idmapd is running on both side (service nfs-utils status
>>> on both side).
>>>
>> This is driving me mad. 'service nfs-utils status' on the
>>
Le 22/09/2012 20:53, Anne Wilson a écrit :
and if
rpc.idmapd is running on both side (service nfs-utils status on
both side).
This is driving me mad. 'service nfs-utils status' on the server
tells me "cannot find nfs-utils service".
Package nfs-utils blahblah is already installed
nfs-common
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just wondered whether these msec lines tell you anything useful -
tcp0 0 *:imaps *:*
LISTEN dovecot
tcp0 0 *:4001 *:*
LISTEN rpc.statd
tcp0 0 *:nfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/09/12 11:01, Guillaume Rousse wrote:
> Le 21/09/2012 20:54, Anne Wilson a écrit :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 20/09/12 21:37, Guillaume Rousse wrote:
>>>
>>> If everything else fails, you may also inhibit IPv6 comp
Le 22/09/2012 00:48, Barry Jackson a écrit :
Not sure if this is related, but did you apply Derek's patch? :-
https://bugs.mageia.org/show_bug.cgi?id=207#c79
Which has nothing to do with the underlying issue here, just with
pushing discussable features to the configuration wizard, such as using
Le 21/09/2012 20:54, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
If everything else fails, you may also inhibit IPv6 completly: just
add 'install ipv6 /bin/true' in any file under /etc/modprobe.d, and
reboot.
Using MCC, I dis
On 21/09/12 19:54, Anne Wilson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
If everything else fails, you may also inhibit IPv6 completly: just
add 'install ipv6 /bin/true' in any file under /etc/modprobe.d, and
reboot.
Using MCC, I disabled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
>
> If everything else fails, you may also inhibit IPv6 completly: just
> add 'install ipv6 /bin/true' in any file under /etc/modprobe.d, and
> reboot.
>
Using MCC, I disabled IPv6 and rebooted. Now 'mount
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 21:37, Guillaume Rousse wrote:
> Le 20/09/2012 20:17, Anne Wilson a écrit :
Looks as though the problem relates to rpc on the server. I
don't mind doing the digging, but can you point me to the
right place to start the hol
Op donderdag 20 september 2012 22:37:27 schreef Guillaume Rousse:
> Le 20/09/2012 20:17, Anne Wilson a écrit :
> >>> Looks as though the problem relates to rpc on the server. I
> >>> don't mind doing the digging, but can you point me to the right
> >>> place to start the hole?
> >>
> >> I'd try t
Le 20/09/2012 20:17, Anne Wilson a écrit :
Looks as though the problem relates to rpc on the server. I
don't mind doing the digging, but can you point me to the right
place to start the hole?
I'd try to understand why the nfs daemon (rpc.nfsd) is listening on
IPv6 only, whereas the mount daemon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 16:27, Guillaume Rousse wrote:
> Le 20/09/2012 15:00, Anne Wilson a écrit :
>>> Also, you can check available NFS version on your servers:
>>> rpcinfo -s 192.168.0.40
>> rpcinfo -s 192.168.0.40 program version(s) netid(s)
>> service own
Le 20/09/2012 15:00, Anne Wilson a écrit :
Also, you can check available NFS version on your servers: rpcinfo
-s 192.168.0.40
rpcinfo -s 192.168.0.40
program version(s) netid(s) service owner
10 2,3,4 local,udp,tcp,udp6,tcp6 portmapper
super
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/09/12 11:59, Guillaume Rousse wrote:
> Le 20/09/2012 11:54, Anne Wilson a écrit :
>>> and -v option to mount.nfs on client side to get more verbose
>>> error reporting.
>>>
>>
>> How do I do that? mount.nfs is an executable, not a shell
>> scr
Le 20/09/2012 11:54, Anne Wilson a écrit :
and -v option to mount.nfs on client side to get more verbose error
reporting.
How do I do that? mount.nfs is an executable, not a shell script, so
I can't add it there. Attempting to add it in the mount command says
it is an invalid option.
This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/09/12 21:47, Guillaume Rousse wrote:
> Le 19/09/2012 19:46, Anne Wilson a écrit :
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> My laptop uses fstab lines to mount directories on the old server
>> and also on a QNAS box. I've no idea w
Le 19/09/2012 19:46, Anne Wilson a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My laptop uses fstab lines to mount directories on the old server and
also on a QNAS box. I've no idea what version of Linux is running on
the QNAS, but the mounts are working there. The old server is runn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My laptop uses fstab lines to mount directories on the old server and
also on a QNAS box. I've no idea what version of Linux is running on
the QNAS, but the mounts are working there. The old server is running
Mageia 2, and mount to that don't work.
40 matches
Mail list logo
