All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wendy Cheng <s.wendy.cheng@gmail.com>
To: Bernd Schubert <bs-PKu+Ek1N2UGzQB+pC5nmwQ@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: multiple instances of rpc.statd
Date: Fri, 25 Apr 2008 11:39:15 -0400	[thread overview]
Message-ID: <4811FB23.4010509@gmail.com> (raw)
In-Reply-To: <200804251630.36917.bs-PKu+Ek1N2UGzQB+pC5nmwQ@public.gmane.org>

Bernd Schubert wrote:
> Hello Wendy.
>
> On Friday 25 April 2008 15:47:03 Wendy Cheng wrote:
>   
>> The efforts have been attempted (to remedy this issue) and a complete
>> set of patches have been (kept) submitting for the past two years. The
>> patch acceptance progress is very slow (I guess people just don't want
>> to get bothered with cluster issues ?).
>>     
>
> Well, I think people are just ignorant. I did see your discussions about NLM 
> in the past on the NFS mailing list, but actually I didn't understand the 
> entire point of discussion ;) I was simply used to active-passive services 
> (mostly due to heartbeat-1.x) and there we just had /var/lib/nfs linked to 
> the exported directory.
>
> After I started to work here, I was confronted with the fact we do have 
> working active-active clusters here, but nobody besides me ever cared about 
> the locking problem :( NFS failovers just are done ignoring file locks.
> Seems so far also nobody run into a problem, but maybe the result was so 
> obscure that nobody ever bothered to complain...
> I'm just afraid most admins will simply do like this...
>   

That's an accurate observation :) .. people are just ignorant until they 
get bitten by the problem. Then they blush out nasty words  about Linux 
servers and go for proprietary solutions.

There are amazing amount of "workaround"(s) and funny setup(s) to bypass 
various Linux problems. Admins normally don't care the details but just 
know if they do certain "tricks", things work. I was looking at a 
performance issue last week why clustered mail servers ran miserably 
slow. As a person who don't know much about mail server, I was surprised 
to learn it is a common practice that linux email servers could be 
configured to grab flock, followed by posix lock, then wrote a lock file 
whenever a "write" occurs - all three actions are used concurrently to 
protect one single file (?).  It was a very interesting conversation.

-- Wendy 


  parent reply	other threads:[~2008-04-25 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 13:31 multiple instances of rpc.statd Bernd Schubert
     [not found] ` <200804251531.21035.bs-PKu+Ek1N2UGzQB+pC5nmwQ@public.gmane.org>
2008-04-25 13:47   ` Wendy Cheng
2008-04-25 14:30     ` Bernd Schubert
     [not found]       ` <200804251630.36917.bs-PKu+Ek1N2UGzQB+pC5nmwQ@public.gmane.org>
2008-04-25 15:39         ` Wendy Cheng [this message]
2008-04-25 22:07     ` J. Bruce Fields
2008-04-28  3:59       ` Wendy Cheng
2008-04-28 18:26         ` J. Bruce Fields
2008-04-28 19:19           ` Wendy Cheng
2008-04-29 16:20             ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4811FB23.4010509@gmail.com \
    --to=s.wendy.cheng@gmail.com \
    --cc=bs-PKu+Ek1N2UGzQB+pC5nmwQ@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.