Prev: redirecting http to https with iptables
Next: pure-ftpd and SuSE 11.1
From: J G Miller on 5 Aug 2010 15:51
On Thu, 05 Aug 2010 12:15:42 -0500, Ignoramus16841 wrote:

> standard nfs client

but using NFS v3 or v4?

> Yes. I am not sure yet what exactly is going on.

Could be some sort of timing bug in the NFS server code?

From: Ignoramus16841 on 5 Aug 2010 15:56
On 2010-08-05, J G Miller <miller(a)yoyo.ORG> wrote:
> On Thu, 05 Aug 2010 12:15:42 -0500, Ignoramus16841 wrote:
>
>> standard nfs client
>
> but using NFS v3 or v4?

NFS 3

>> Yes. I am not sure yet what exactly is going on.
>
> Could be some sort of timing bug in the NFS server code?
>

It could be anything, but I am more inclined to blame the client, as

1) Many clients work just fine
2) Even my bad desktop works fine when it connects after a reboot
From: Rahul on 5 Aug 2010 17:31
Ignoramus16841 <ignoramus16841(a)NOSPAM.16841.invalid> wrote in news:5
_KdnW29vrfPisbRnZ2dnUVZ_rmdnZ2d(a)giganews.com:

> Could be some sort of timing bug in the NFS server code?
>>
>
> It could be anything, but I am more inclined to blame the client, as
>
> 1) Many clients work just fine
> 2) Even my bad desktop works fine when it connects after a reboot
>

Does it matter if it is a soft or hard mount?

I'm just guessing here. I've a long mount option string on my server:

eustorage:/opt /opt nfs rw,nodev,noatime,nfsvers=3,timeo=110,retrans=
50,hard,intr,proto=udp,rsize=32768,wsize=32768 0 0

But I'd be hard pressed to explain why I chose each option that I have in
there. :)


--
Rahul
From: J G Miller on 6 Aug 2010 09:36
On Fri, 06 Aug 2010 07:22:31 +0000, Huge wrote:
>
> Hard NFS mounts are not necessarily a good idea. If the server hangs, so
> will the client.

Exactly. If you are doing read-only mounting, then mounting with the hard
option is less necessary, and if using NFS v4 with TCP even less critical
again.

From man 5 nfs

NB: A so-called "soft" timeout can cause silent data
corruption in certain cases. As such, use the soft
option only when client responsiveness is more important
than data integrity. Using NFS over TCP or increasing
the value of the retrans option may mitigate some of the
risks of using the soft option.

If rriting data to an NFS mounted disk, then it is much safer to use
hard to avoid possible data corruption issues, but if your data is
really that critical, you should not be writing it to an NFS mounted disk,
eg save locally and then use rsync, and obviously for multi client
operation you would be using a database anyways ...
From: Rahul on 6 Aug 2010 17:20
Huge <Huge(a)nowhere.much.invalid> wrote in news:8c1rhnFc72U1
@mid.individual.net:

> Hard NFS mounts are not necessarily a good idea. If the server hangs, so
> will the client.
>
>

True. But doesn't the seciton of the NFS manuals also reccomend
hard mounts to prevent data loss?

>As such, use the soft option only when client responsiveness is more
>>important than data integrity.

So, does one have to chose between the devil (data loss) and the deep sea
(hung client)?

I thought the way to go was using hard + intr to get both integrity and
responsiveness. Unfortunately never got it to work that way but that's
another story.

--
Rahul
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: redirecting http to https with iptables
Next: pure-ftpd and SuSE 11.1