All of lore.kernel.org
 help / color / mirror / Atom feed
From: Venelin Mihaylov <venelin@fcolor.bg>
To: Jamie Border <jborder@gmail.com>
Cc: Linux admin mailing list <linux-admin@vger.kernel.org>
Subject: Re: NFS behaviour on server crash
Date: Fri, 11 Feb 2005 17:22:04 +0200	[thread overview]
Message-ID: <1108135324.3885.14.camel@localhost.localdomain> (raw)
In-Reply-To: <8666c78705021107112ce03cd3@mail.gmail.com>

	Thank you very much for the provided information. 
	I am asking because I want to implement an centralized clamav mail
scanner, which AFAIK would work, only if I mount the directories in
which the mail is scanned on the server. First I mounted the directories
on the server so the clamav client is actually NFS server.
	Then I realized that I do not know what will happen if the clamav
client / NFS server will crash.
	The behavior which you described (for hard mounted directories) will
work just fine.

	Thanks for your time.

On Fri, 2005-02-11 at 15:11 +0000, Jamie Border wrote:
> s/kill killed/is killed/g
> 
> 
> On Fri, 11 Feb 2005 15:11:17 +0000, Jamie Border <jborder@gmail.com> wrote:
> > Venelin
> > 
> > It Depends :-)
> > 
> > Assuming hard mounting (see link below),
> > 
> > The client machine will behave normally until a process on the client
> > tries to open a file on the nfs server.  It will then block (hang)
> > until either:
> > 
> > 1) The nfs server is up and running again
> > 2) The client process kill killed (kill -KILL <processid>)
> > 
> > You could get round this by soft-mounting the nfs share, but this will
> > probably break software using files over it.
> > 
> > For more info, see:
> > 
> > http://nfs.sourceforge.net/nfs-howto/client.html#SOFT-VS-HARD
> > 
> > Or try searching for "nfs server crash" on google.
> > 
> > Hope this helps
> > 
> > Jamie
> > 
> > 
> > On Fri, 11 Feb 2005 16:50:42 +0200, Venelin Mihaylov <venelin@fcolor.bg> wrote:
> > > Hello list :),
> > >  I have the following question:
> > >   What will happen when an NFS server crashes while a client has mount a
> > > NFS directory from that server ?
> > >
> > > --
> > > Venelin Mihaylov, CCNA
> > > System Administrator
> > > HostColor LLC
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >
> >
> 
-- 
Venelin Mihaylov, CCNA
System Administrator
HostColor LLC


      parent reply	other threads:[~2005-02-11 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 14:50 NFS behaviour on server crash Venelin Mihaylov
     [not found] ` <8666c7870502110711585a5386@mail.gmail.com>
     [not found]   ` <8666c78705021107112ce03cd3@mail.gmail.com>
2005-02-11 15:22     ` Venelin Mihaylov [this message]

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=1108135324.3885.14.camel@localhost.localdomain \
    --to=venelin@fcolor.bg \
    --cc=jborder@gmail.com \
    --cc=linux-admin@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.