It is usually best to use the newest e2fsprogs release, since it has the most fixes. This is currently 1.42.7.wc2 though we are just in the process of releasing 1.42.9.wc1.
That said, I would not run e2fsck on the failing device. That can cause extra stress on the device and cause it to fail sooner. Better to copy it to a new device using "rescue_dd" or "dd conv=sync,noerror if=/dev/old of=/dev/new" and then run e2fsck on the new device. Not only is that less likely to induce more errors on the failing device, if there are any problems with e2fsck you can copy the data again. Cheers, Andreas On May 13, 2014, at 14:20, "Gretchen Zwart" <zw...@astro.umass.edu<mailto:zw...@astro.umass.edu>> wrote: Hi, I have one of 10 OSTs with underlying hardware failure (not catastrophic yet just flakey). Initially e2fsck resolved errors but the last pass came up with "short read" and I am dealing with harwdare issues on ailing OST. I have inactivated this OST but the remaining data is not much use without it. I am running lustre 1.8.7 (sles11 kernel/debian 6.0). I would like to know which is best e2fsck version to use. I have 1.41.12.2.ora1. Regards, Gretchen -- Gretchen Zwart UMass Astronomy Dept. 619E Lederle 710 North Pleasant ST Amherst,MA 01003 (413) 577-2108 _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org<mailto:Lustre-discuss@lists.lustre.org> http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
