It is just a confidence/testing issue. Since 1.6.4.1 is not a "bug- fix only" release, it will be essentially untested for us. Since we run a production cluster, this is not acceptable. We put 1.6.3 into service originally without the thorough testing it needed and we were *VERY* sorry. Applying a specific patch to a known code base is a good bit safer though not foolproof.
Charlie Taylor UF HPC Center On Jan 11, 2008, at 1:55 PM, Kilian CAVALOTTI wrote: > On Friday 11 January 2008 10:51:34 am Wojciech Turek wrote: >> Hi, >> >> Yes I came with same conclusion. I have tried to apply patches from >> this bug but patching process has FAILED. > > This may be a little off-topic, but since patches for bug #13917 have > been included in 1.6.4.1, is manually patching really worth the > hassle? > Unless you have a specific reason to stick with 1.6.3, of course. > > Cheers, > -- > Kilian > > _______________________________________________ > Lustre-discuss mailing list > [email protected] > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
