Hi,
On Jun 29, 2013, at 2:45, Rick Macklem rmack...@uoguelph.ca wrote:
Btw, a NFSv4 mounted root fs will not work correctly, because the client
name is generated from the host uuid, which isn't set when the root fs
is mounted. I'm not sure what the client would use as its client name,
but
Lars Eggert wrote:
Hi,
On Jun 29, 2013, at 2:45, Rick Macklem rmack...@uoguelph.ca wrote:
Btw, a NFSv4 mounted root fs will not work correctly, because the
client
name is generated from the host uuid, which isn't set when the root
fs
is mounted. I'm not sure what the client would use
Hi,
I should have mentioned that the server is FreeBSD -STABLE running newnfs, and
the network isn't partitioned (because I access the box over SSH at the same
time I see these messages.)
They only appear under heavy NFS load (portmaster build of math/R in this case.)
Lars
On Jun 29, 2013,
Thanks Rick! I will check these Monday.
Lars
On Jun 29, 2013, at 2:45, Rick Macklem rmack...@uoguelph.ca wrote:
Lars Eggert wrote:
Hi,
On Jun 28, 2013, at 16:37, Eggert, Lars l...@netapp.com wrote:
On Jun 28, 2013, at 16:14, Eggert, Lars l...@netapp.com wrote:
on a -CURRENT client, I get
Lars Eggert wrote:
Hi,
I should have mentioned that the server is FreeBSD -STABLE running
newnfs, and the network isn't partitioned (because I access the box
over SSH at the same time I see these messages.)
They only appear under heavy NFS load (portmaster build of math/R in
this case.)
Lars Eggert wrote:
Hi,
I should have mentioned that the server is FreeBSD -STABLE running
newnfs, and the network isn't partitioned (because I access the box
over SSH at the same time I see these messages.)
They only appear under heavy NFS load (portmaster build of math/R in
this case.)
Hi,
on a -CURRENT client, I get quite a number of console messages under heavy
NFSv4 load, such as:
nfsv4 expired locks lost
nfscl: never fnd open
nfscl: never fnd open
nfscl: never fnd open
nfsv4 expired locks lost
nfscl: never fnd open
nfscl: never fnd open
nfsv4 expired locks lost
nfsv4
Hi,
On Jun 28, 2013, at 16:14, Eggert, Lars l...@netapp.com wrote:
on a -CURRENT client, I get quite a number of console messages under heavy
NFSv4 load, such as:
nfsv4 expired locks lost
nfscl: never fnd open
actually, not sure if the nfscl message is from an NFSv4 mount point or not,
Hi,
On Jun 28, 2013, at 16:37, Eggert, Lars l...@netapp.com wrote:
On Jun 28, 2013, at 16:14, Eggert, Lars l...@netapp.com wrote:
on a -CURRENT client, I get quite a number of console messages under heavy
NFSv4 load, such as:
nfsv4 expired locks lost
nfscl: never fnd open
actually, not
Lars Eggert wrote:
Hi,
on a -CURRENT client, I get quite a number of console messages under
heavy NFSv4 load, such as:
nfsv4 expired locks lost
Means the lease expired on the NFSv4 server somehow. Lease
expiry is bad news and there is no way to recover locks
lost because of it.
nfscl:
Lars Eggert wrote:
Hi,
On Jun 28, 2013, at 16:37, Eggert, Lars l...@netapp.com wrote:
On Jun 28, 2013, at 16:14, Eggert, Lars l...@netapp.com wrote:
on a -CURRENT client, I get quite a number of console messages
under heavy NFSv4 load, such as:
nfsv4 expired locks lost
nfscl:
11 matches
Mail list logo