[Beowulf] Transient NFS Problems in New Cluster
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Prentice Bisbal prentice at ias.eduWed Feb 3 07:27:35 PST 2010
- Previous message: [Beowulf] Transient NFS Problems in New Cluster
- Next message: [Beowulf] Transient NFS Problems in New Cluster
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joe Landman wrote: > Jon Forrest wrote: >> I have a new cluster running CentOS 5.3. >> The cluster uses a Sun 7310 storage server >> that provides NFS service over a private >> 1Gb/s ethernet with 9K jumbo frames to the >> cluster. >> >> We've noticed that a number of the compute >> nodes sometimes generate the >> >> automount[15023]: umount_autofs_indirect: ask umount returned busy /home > > [...] > >> Any advice on what to do? > > We still recommend turning off autofs for home directories. We've seen > lots of problems with it on many clusters. Hard mounts are IMO better. > That server should be able to handle it. > How do you handle situations where home directories are spread across multiple servers? Do have a large /etc/fstab on ever NFS client? -- Prentice
- Previous message: [Beowulf] Transient NFS Problems in New Cluster
- Next message: [Beowulf] Transient NFS Problems in New Cluster
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
