[GE users] occasional job failure - can't find user's home directory

m0zes adam.tygart at gmail.com
Wed Oct 27 18:44:38 BST 2010

In all honesty, there are good reasons to use the automounter on a
Beowulf cluster.
For example, my file server is running OpenSolaris, each of my users'
home directories falls on a different zfs "filesystem." (The reason
for this is simpler snapshots and better quota management).
Under your solution I would have to mount each of my 275 home
directories on each of my 125 nodes on the off chance that a
particular user is going to need access to those files on that node.
This would create an unnecessary strain on my file server. Using
automounter, only the users that are logged have their home
directories mounted.


On Wed, Oct 27, 2010 at 17:31, jlforrest <jlforrest at berkeley.edu> wrote:
> On 10/27/2010 10:19 AM, John Foley wrote:
>> Jon -
>> thanks for the reply - that's very interesting info. One
>> question, though - when you say you "turned off" the
>> automounter, I'm assuming that you also had to hard-mount
>> the user's home directory areas, and any other NFS
>> areas that the simulations require ?
> That's right. If the private network in a Beowulf
> cluster has the kind of problems that the automounter
> solves, then you have a sick cluster.
> I believe that for a standard Beowulf cluster an automounter
> isn't necessary on the compute nodes. In environments
> where compute nodes mount from "non-standard" file servers
> or have other unusual features this might not be true.
> But, in my Rocks cluster, I've had absolutely no problems
> due to turning off the automounter.
> Jon
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=290496
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].


To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].

More information about the gridengine-users mailing list