Rob Thanks for the suggestions. I aliased corona0 to tcp://corona:3334 and adjusted the rest. But just to note. I also had to change the value for tcp://coronaxxx:3334 within each pvfs2-server.conf-coronaxxxx as they also followed the values that the aliases had taken, i.e. tcp://corona1:3334 was in the pvfs2-server.conf-corona file, tcp://corona2:3334 in the pvfs2-server.conf-corona1 file, and so on. After that, restarted the daemons and the pvfs2 file system is working.
Patrick On Wednesday 17 May 2006 19:11, Robert Latham wrote: > On Wed, May 17, 2006 at 05:55:26PM +0100, Patrick Tuite wrote: > > (4) Searching for /mnt/pvfs2/ in pvfstab... > > > > PVFS2 servers: tcp://corona:3334 > > Storage name: pvfs2-fs > > Local mount point: /mnt/pvfs2 > > > > meta servers: > > tcp://corona1:3334 > > > > data servers: > > tcp://corona1:3334 > > tcp://corona2:3334 > > tcp://corona3:3334 > > tcp://corona:3334 > > Yup, that's the problem. > > > <Aliases> > > Alias corona tcp://corona1:3334 > > Alias corona1 tcp://corona2:3334 > > Alias corona2 tcp://corona3:3334 > > Alias corona3 tcp://corona:3334 > > </Aliases> > > another symptom, same cause. > > > Thanks for your help! > > Thanks for the report. No quick fix for this yet but we'll let you > know. It's due to the way pvfs2-genconfig sorts hostnames. In the > meantime, can you maybe add an alias for 'corona' called 'corona0' and > use that instead? > > ==rob -- Patrick Tuite Research IT Support UCD Computing Services Ext: 2037 _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
