Hi, Just wondering is anyone else hitting this:
1.4.8 (correctly I guess!) started rejecting locks unless the "flock" mount option was used, as per changelog note for bug #10743. I guess in the past it faked success but the file wasn't really locked? Among other things, on RHEL4: modprobing locks... rpm locks... sqlite (and therefore yum) locks... This has blocked migration to 1.4.8 in our shared root setup. While the < 1.4.8 behaviour worked okay for us (in so far as most locks don't matter all that much anyway and so booting proceeds just fine if they're fake), I certainly don't consider it valid for us to have relied on it, so I don't consider this bug-fix behaviour change a bug: Obviously, we were skating on rather thin ice, but we kind of knew that already... => So, what's the latest on file lock support in general in lustre? Actually using the "flock" mount option doesn't seem to be a solution, as AFAIK it's known incomplete in 1.4.x (?): Unless flock is supposed to be working fully in 1.4.8, in which case, well, maybe there is a bug to be found... _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
