[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-isp
Subject:    Re: freebsd-isp Digest, Vol 136, Issue 6
From:       rtsit <rtsit () yahoo ! com>
Date:       2005-10-31 19:36:10
Message-ID: 20051031193610.11696.qmail () web53015 ! mail ! yahoo ! com
[Download RAW message or body]


On thing you may notice is that you won't be able to
run certain disk commands on the client boxes while
your NFS server is in the middle of being rebooted.

If your NFS is doing an fsck, the time to reboot may
be even longer, which will cause a noticable problem.

For instance, if your NFS server is offline for
whatever reason, and you login to a client box and do
a "df -k" -- the file system list will print out until
it hits the NFS mounts, and then it will just hang
there. Hitting CTRL-C or CTRL-Z will not help, and
you'll have to open a new SSH session to do anything
else.

If your NFS server comes back online, then everything
will continue as normal -- but you will have hung
processes while the NFS server is out to lunch if the
processes on the client are trying to access the NFS
mount for whatever reason.

I think it would be nice for something like "df -k" to
timeout after 30 seconds, rather than sit there
hanging for several minutes or longer when it can't
get a reply from the NFS server.


--- freebsd-isp-request@freebsd.org wrote:

> Date: Sat, 29 Oct 2005 18:50:16 +0000
> From: Marcin Jessa <lists@yazzy.org>
> Subject: Re: NFS & rebooting
> To: Troy Settle <troy@psknet.com>
> 
> On Sat, 29 Oct 2005 14:41:01 -0400
> Troy Settle <troy@psknet.com> wrote:
> 
> > All,
> Hi Troy.
> 
> > A long time ago (3.x days?), whenver I rebooted an
> NFS server, all
> > the client machines with mounted filesystems would
> completely freak
> > out. I'm not talking about application errors, but
> that the nfs
> > mounts were totally unresponsive.  I couldn't
> unmount the filesystems
> > and I couldn't remount them, the only thing I
> could do, was to force
> > a reboot on the client boxes, after which, they
> would come up and
> > mount their filesystems without issue.
> > 
> > I'm looking again, at using NFS for my mail server
> setup, but need to 
> > know what the ramifications are if I need to
> reboot the NFS server,
> > or if it's forced to reboot without the clients
> first dismounting any 
> > filesystems.
>  
> A whole lot has changed since the 3.x times.
> >From my experience, the clients (FreeBSD, NetBSD
> and Linux) were fully
> responsive and could reach the NFS mounts when the
> NFS server came back
> up after reboot.
> 
> Cheers,
> Marcin
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Sat, 29 Oct 2005 14:59:51 -0400
> From: Troy Settle <troy@psknet.com>
> Subject: NFS & Consumer-grade GigE switches
> To: freebsd-isp@freebsd.org
> Message-ID: <4363C6A7.10808@psknet.com>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
> 
> Hey, while I'm switching over to NFS and
> distributing some front-end 
> services, does anyone have any experience with
> putting a consumer grade 
> (<$100) GigE switch into production?
> 
> While I should probably get a managed switch, I just
> gotta wonder how 
> far consumer-grade equipment has come and if it'll
> work for an NFS-only LAN.
> 
> Thanks,
> 
> --
>   Troy Settle
>   Pulaski Networks
>   http://www.psknet.com
>   866.477.5638
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> freebsd-isp@freebsd.org mailing list
>
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to
> "freebsd-isp-unsubscribe@freebsd.org"
> 
> End of freebsd-isp Digest, Vol 136, Issue 6
> *******************************************
> 



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs
_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]