[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [Linux-cluster] Cluster NFS causes kernel bug


Thanks for the tip on CentOS.  My working cluster is now:
3node 64bit AMD opteron 2GHz
CentOS 5 (good)
GFS 1 0.1.11(good)
Apache 2.2.3 (good)
Samba 3.0.23c-2 (good)
NFS 1.0.9-16 (BAD)

So I am avoiding Fedora and GFS2 until you've had more time to "bake"

I am reading up on Wendy Chang's NFS linux-cluster postings to
understand why NFS fail over is not consistent.
- Has anyone successfully setup a failover NFS cluster?
- Does nfsv4 work better?  It appears by default fedora6 uses nfsv3
(tcp) client and is flaky.



From: Kevin Anderson [mailto:kanderso redhat com] 
Sent: Monday, October 08, 2007 3:09 PM
To: Ward, Timothy - SSD
Subject: Re: [Linux-cluster] Cluster NFS causes kernel bug

On Mon, 2007-10-08 at 09:52 -0400, Ward, Timothy - SSD wrote: 

	I completely reinstalled my cluster and gotten back to Apache
and Samba
	working and NFS using a GFS2 filesystem making a Kernel bug and
	the whole cluster.

Yeah, we have posted a large number of patches to fix most of the major
problems with gfs2.  Those should be percolating through upstream and
then will get pulled into a fedora kernel at some point. 

	How are the GFS1/FC7 rpms coming? Where should I look to
download them?

Not as well as we had hoped.  We have been swamped with multiple RHEL
releases/updates occurring pretty much at the same time.  We will likely
need to have our own version of the kernel since gfs1 requires access to
three symbols in the gfs2 code in order to access the lock managers.  

	If I can get a stable setup of GFS (1 or 2) working to show
management I
	will be able to get a testbed for testing 64bit versions for
you. So
	basically I need some flavor of FC and GFS that are stable so I
can put
	it into production and show it off.

Have you considered using the CENTOS instead of Fedora?  Since CentOS
essentially replicates the RHEL rpms, everything is already built and

This e-mail and any files transmitted with it may be proprietary 
and are intended solely for the use of the individual or entity to 
whom they are addressed. If you have received this e-mail in 
error please notify the sender. Please note that any views or
opinions presented in this e-mail are solely those of the author 
and do not necessarily represent those of ITT Corporation. The 
recipient should check this e-mail and any attachments for the 
presence of viruses. ITT accepts no liability for any damage 
caused by any virus transmitted by this e-mail.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]