On 07/20/2012 06:29 PM, Dietmar Maurer wrote: >> This looks strange to me. It acts like we need mkfs the directory >> before run the sheep, where as we actually make nothing to it, just >> create a file lock. This extra step might solve some problems >> (which could be solved by other means), but it will cause great >> inconvenience to all users: we have to run sheep with sheep -i for >> the first time, and for following restarting, we don't need it. > > BTW, to prevent the problem, you (or chris) suggested to use mklabel > to label the whole file system. For me that is much more > 'inconvenient' (and is also an extra step). > Well this is the problem of the sheepdog itself. This is the problem caused by users usage of other resource. So I think this should be handled outside the sheep. Thanks, Yuan |