Hi Bill, This might seem like a naive solution, but what I've done in the past is to simply stop the pvfs2-client daemon on all the nodes except the one I'm running pvfs2-fsck from. This worked for me, but I don't pretend to fully understand all the ins and outs of pvfs2.
--Luke -- Luke Hindman Research Assistant Computer Science Department Boise State University, Boise, ID 83725 [EMAIL PROTECTED] On 8/31/07, Bill Wichser <[EMAIL PROTECTED]> wrote: > > We'd finally like to run an fsck to try and clean up our pvfs2 > filesystem (see my previous post about kernel crashes) but are concerned > about users' jobs still accessing the filesystem while we are running > these checks. > > From the kernel interface, this is easy, we simply disable the kernel > module. The other method though, direct access via the API/MPI-ROMIO, > remains an issue. Is there some method we can use to disable access > through this interface? Or can we just run the fsck without worrying > about this? > > Thanks, > Bill > _______________________________________________ > Pvfs2-users mailing list > [email protected] > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users >
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
