Hello all,
Do you guys use NFS v4 in production? Is the Linux implementation ready enough?
The feeling I'm getting by looking at RH doc and other web sites is that v4 was added in a hurry and is not mainstream yet. I don't want to use something too cutting edge that will break down the road. Is that the case?
In my case, it would be a CentOS5 server with CentOS4 client.
Thanks,
On 06/06/07, Francois Caen frcaen@gmail.com wrote:
Hello all,
Do you guys use NFS v4 in production? Is the Linux implementation ready enough?
The feeling I'm getting by looking at RH doc and other web sites is that v4 was added in a hurry and is not mainstream yet. I don't want to use something too cutting edge that will break down the road. Is that the case?
In my case, it would be a CentOS5 server with CentOS4 client.
I tried implementing it a year/18 months or so back for an NFS mounted Qmail mailstore for around 8000 accounts.
NFS v2/3 had been running fine off an FC-based server for a few years but we wanted to standardise on CentOS 4. During the migration I managed to get NFSv4 working to my satisfaction and rudimentary load tests all seemed fine.
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented. Maybe the EL5 implementation behaves better?
Will.
On 6/6/07, Will McDonald wmcdonald@gmail.com wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented.
Will, could you please expand on what went wrong? What kind of symptoms did you experience? And did everything work prefectly when you just reverted to v3?
Thanks,
On 06/06/07, Francois Caen frcaen@gmail.com wrote:
On 6/6/07, Will McDonald wmcdonald@gmail.com wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented.
Will, could you please expand on what went wrong? What kind of symptoms did you experience? And did everything work prefectly when you just reverted to v3?
I can't recall *exactly* what was going on as it was a while back.
We had 3 or 4 identical clients mounting maildirs. Under relatively light real user load NFS 4 mounts would lock up and all sorts of other weirdness. reverting back to v3 resolved the problems.
I never got round to trying again. I would probably have waitied until we moved to a newer major version of CentOS.
Will
On Wed, 6 Jun 2007 10:32:04 +0200, Will wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented. Maybe the EL5 implementation behaves better?
I use one of my CentOS 5 boxen for low-load fileserver with NFS4. I've been noticing that although MP3s plays fine from that box, it can take a minute or two to write a dozen tags--something that should happen in the blink of an eye. I've been wondering what the problem is. Maybe it's NFS4!
Miark
Miark wrote:
On Wed, 6 Jun 2007 10:32:04 +0200, Will wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented. Maybe the EL5 implementation behaves better?
I use one of my CentOS 5 boxen for low-load fileserver with NFS4. I've been noticing that although MP3s plays fine from that box, it can take a minute or two to write a dozen tags--something that should happen in the blink of an eye. I've been wondering what the problem is. Maybe it's NFS4!
Miark _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I've been experiencing 5 to 20 seconds freezes ever since I upgraded my nfs server. This serves about 30 people. Anytime someone writes a big file to their home directory, the freezes happen. You can experience the freezes when browsing the internet, I guess because firefox is constantly writing data (cache, cookies, etc...). Other apps freeze up too.
Now the question on my side is: can I force centos4 for serve nfs3 as opposed to nfs4. If I am not mistaken this is dependent on the client?
The reason Im asking is that if I can force the server to serve nfs3 then the clients will default to nfs3 themselves. right?
-Jean
Jean Figarella wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented. Maybe the EL5 implementation behaves better?
I use one of my CentOS 5 boxen for low-load fileserver with NFS4. I've been noticing that although MP3s plays fine from that box, it can take a minute or two to write a dozen tags--something that should happen in the blink of an eye. I've been wondering what the problem is. Maybe it's NFS4!
I've been experiencing 5 to 20 seconds freezes ever since I upgraded my nfs server. This serves about 30 people. Anytime someone writes a big file to their home directory, the freezes happen. You can experience the freezes when browsing the internet, I guess because firefox is constantly writing data (cache, cookies, etc...). Other apps freeze up too.
Now the question on my side is: can I force centos4 for serve nfs3 as opposed to nfs4. If I am not mistaken this is dependent on the client?
The reason Im asking is that if I can force the server to serve nfs3 then the clients will default to nfs3 themselves. right?
Are these mounted with the sync or async option? If it is sync, the client waits for the physical flush to disk to happen on every operation, something that is horribly slow and that you never do for local disks except for transaction boundaries in databases and other unusual situations.
Les Mikesell wrote:
Jean Figarella wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented. Maybe the EL5 implementation behaves better?
I use one of my CentOS 5 boxen for low-load fileserver with NFS4. I've been noticing that although MP3s plays fine from that box, it can take a minute or two to write a dozen tags--something that should happen in the blink of an eye. I've been wondering what the problem is. Maybe it's NFS4!
I've been experiencing 5 to 20 seconds freezes ever since I upgraded my nfs server. This serves about 30 people. Anytime someone writes a big file to their home directory, the freezes happen. You can experience the freezes when browsing the internet, I guess because firefox is constantly writing data (cache, cookies, etc...). Other apps freeze up too.
Now the question on my side is: can I force centos4 for serve nfs3 as opposed to nfs4. If I am not mistaken this is dependent on the client?
The reason Im asking is that if I can force the server to serve nfs3 then the clients will default to nfs3 themselves. right?
Are these mounted with the sync or async option? If it is sync, the client waits for the physical flush to disk to happen on every operation, something that is horribly slow and that you never do for local disks except for transaction boundaries in databases and other unusual situations.
At first the sync option was being used, and the freezes happened very frequently. About a month and a half ago I started using async, and now I get far fewer freezes, like maybe 3 in an 8hr span.
-Jean
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jean Figarella Sent: Wednesday, June 06, 2007 12:14 PM To: CentOS mailing list Subject: Re: [CentOS] NFS v4
Les Mikesell wrote:
Jean Figarella wrote:
Under real user load though it just fell on its arse very quickly and a quick fall back to v3 was implemented. Maybe the EL5 implementation behaves better?
I use one of my CentOS 5 boxen for low-load fileserver with NFS4. I've been noticing that although MP3s plays fine from that box, it can take a minute or two to write a dozen tags--something that should happen in the blink of an eye. I've been wondering what the problem is. Maybe it's NFS4!
I've been experiencing 5 to 20 seconds freezes ever since
I upgraded
my nfs server. This serves about 30 people. Anytime
someone writes a
big file to their home directory, the freezes happen. You can experience the freezes when browsing the internet, I guess because firefox is constantly writing data (cache, cookies, etc...). Other apps freeze up too.
Now the question on my side is: can I force centos4 for
serve nfs3 as
opposed to nfs4. If I am not mistaken this is dependent on
the client?
The reason Im asking is that if I can force the server to
serve nfs3
then the clients will default to nfs3 themselves. right?
Are these mounted with the sync or async option? If it is
sync, the
client waits for the physical flush to disk to happen on every operation, something that is horribly slow and that you
never do for
local disks except for transaction boundaries in databases
and other
unusual situations.
At first the sync option was being used, and the freezes happened very frequently. About a month and a half ago I started using async, and now I get far fewer freezes, like maybe 3 in an 8hr span.
You can also couple the async with the anticipatory scheduler so reads will get higher priority then writes which can help readers during a page-cache flush.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
On 06/06/07, Jean Figarella jfigarella@vecna.com wrote:
I've been experiencing 5 to 20 seconds freezes ever since I upgraded my nfs server. This serves about 30 people. Anytime someone writes a big file to their home directory, the freezes happen. You can experience the freezes when browsing the internet, I guess because firefox is constantly writing data (cache, cookies, etc...). Other apps freeze up too.
Now the question on my side is: can I force centos4 for serve nfs3 as opposed to nfs4. If I am not mistaken this is dependent on the client?
The reason Im asking is that if I can force the server to serve nfs3 then the clients will default to nfs3 themselves. right?
If no other suggestions help then you can mount NFS v2/3 only. Have a quick browse though...
$ man 5 nfs
Will.
-
Francois Caen -
Jean Figarella -
Les Mikesell -
Miark -
Ross S. W. Walker -
Will McDonald