Thanks for the pointer to this. After thinking on this a bit, I believe I can see my way clear to using it. Testing time....
bob On 12/7/2010 5:45 PM, Cliff White wrote: > On 12/07/2010 06:51 AM, Bob Ball wrote: >> We have 6 OSS, each with at least 8 OST. It sometimes happens that I >> need to do maintenance on an OST, so to avoid hanging processes on the >> client machines, I use lctl to disable access to that OST on active >> client machines. >> >> So, now, it may happen during this maintenance that a client machine is >> rebooted. So far so good, until it comes time for the Lustre mount. At >> this point, the reboot will hang, as the under-maintenance OST that is >> expected to be found by this rebooting client, is not found. >> >> Is there some way around this Catch-22? > This is covered in the Lustre Manual, see the 'exclude' option to mount: > http://wiki.lustre.org/manual/LustreManual18_HTML/ConfiguringLustre.html#50651184_pgfId-1298889 > > cliffw >> Thanks, >> bob >> >> _______________________________________________ >> Lustre-discuss mailing list >> [email protected] >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss > > _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
