Vikrant, On our Beowulf cluster here at Boise State University (running FC3), I use the attached init scripts to start/stop the pvfs2 client daemon and mount/umount the filesystem on the pvfs2 client nodes. I just copy them to /etc/init.d and use chkconfig to set the runlevels. I've had to tweak the order that the daemons are started up, but they should atleast give you a starting point.. The scripts are composed from code I've gleaned from several different places and made into something useful (at least in our environment). Your milage may vary.
Also, the pvfs2-client script is designed to read a pvfs2-client.conf file from /etc/sysconfig. I've included our version of this file for your reference. I hope this is helpful. Have a good day, --Luke -- Luke Hindman Research Assistant Computer Science Department Boise State University, Boise, ID 83725 [EMAIL PROTECTED] On 11/15/06, Robert Latham <[EMAIL PROTECTED]> wrote:
On Wed, Nov 15, 2006 at 05:41:45PM +0530, Vikrant Kumar wrote: > 1. I understand that a 1.6 release is around the corner. Can anyone > provide a more definite time? Would be really helpful to plan things > on my side. You probably already saw this, but we released PVFS 2.6.0 today. > 2. I have a cluster with 11 nodes connected with Infiniband . Each > node has four Opteron cores. My application uses MPI IO and I would > like to test it up to 32 way. Given the cluster and the application > requirement, what would be the ideal number of servers for this > set-up? I was thinking either four or eight PVFS2 servers, being > shared with the computing-cores on some nodes. I have read the FAQ > entry and I guess this is a very general question. But I just > wanted to get a quick review of the layout from you guys. 8 is a good number for a lot of workloads. You can use fewer datafiles if you find your workload uses lots of small files, while still retaining the ablity to have all 8 servers working together for larger file accesses. > 3. Another thing is when a node is rebooted. The provided script > file "pvfs2-server.rc" can take care of the server but what about > client application, the kernel module and the mount point? Is there > a way to automate the startup of all these as well. I think this > would be a critical thing for this bigger installation. The problem with automating the kernel moudle and mounting process is that every distribution does it a little differently. This is an area where we really can't make too many assumptions. The best way to automate it is to create a script that does the appropriate things (load kernel module, start up pvfs2-client and pvfs2-client-core, mount the file system) for your system. Perhaps admins from other sites might have ideas for you. Have fun ==rob -- Rob Latham Mathematics and Computer Science Division A215 0178 EA2D B059 8CDF Argonne National Lab, IL USA B29D F333 664A 4280 315B _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
pvfs2-client
Description: Binary data
pvfs2-client.conf
Description: Binary data
pvfs2-mounts
Description: Binary data
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
