On Sun, Mar 20, 2011 at 11:32:32PM +0100, Luk Claes wrote:
> > As noted above, I only had version 4 configured in one of them:
> > might that have upset the negotiation/default somehow?
>
> It might if the export was not configured to be for NFSv4 (with an
> fsid=0 entry etc). Another possibility
On 03/20/2011 11:11 PM, ael wrote:
> On Sun, Mar 20, 2011 at 07:40:47PM +0100, Luk Claes wrote:
>> Hi
>>
>>> Mounting an nfs file system suddenly stopped working with errors
>>> like this:
>>> --
>>> # mount.nfs exact:/ /mnt/exact -v
>>> mount.nfs: t
On Sun, Mar 20, 2011 at 07:40:47PM +0100, Luk Claes wrote:
> Hi
>
> > Mounting an nfs file system suddenly stopped working with errors
> > like this:
> > --
> > # mount.nfs exact:/ /mnt/exact -v
> > mount.nfs: timeout set for Wed Feb 3 16:09:00 201
Hi
> Mounting an nfs file system suddenly stopped working with errors
> like this:
> --
> # mount.nfs exact:/ /mnt/exact -v
> mount.nfs: timeout set for Wed Feb 3 16:09:00 2010
> mount.nfs: trying text-based options
'addr=192.168.0.5,vers=4,clienta
4 matches
Mail list logo