Hey Folks, So I''m not sure if this is the proper forum, but.. does anyone know what happened to the binaries for lustre 1.6.7? They were released, that much I know. I even have them installed on some systems but... they''re no where to be found on the sun site. Was it pulled without announcement? ---------------- John White HPC Systems Engineer (510) 486-7307 One Cyclotron Rd, MS: 50B-3209C Lawrence Berkeley National Lab Berkeley, CA 94720
On Fri, Apr 10, 2009 at 3:38 PM, John White <jwhite at lbl.gov> wrote:> Hey Folks, > ? ? ? ?So I''m not sure if this is the proper forum, but.. does anyone know > what happened to the binaries for lustre 1.6.7? ?They were released, > that much I know. ?I even have them installed on some systems but... > they''re no where to be found on the sun site. ?Was it pulled without > announcement?To quote Peter Jones: A bug has been identified in 1.6.7 that can cause directory corruptions on the MDT. A patch and full details are in bug 18695 - https://bugzilla.lustre.org/show_bug.cgi?id=18695 We recommend to anyone running 1.6.7 on the MDS to unmount the MDT, run e2fsck against the MDT device and apply the patch from bug 18695 as soon as possible.
Hi John: Yes, I think it was pulled out. There was a serious issue with it. On Fri, Apr 10, 2009 at 8:14 PM, Aaron Porter <atporter at gmail.com> wrote:> On Fri, Apr 10, 2009 at 3:38 PM, John White <jwhite at lbl.gov> wrote: >> Hey Folks, >> ? ? ? ?So I''m not sure if this is the proper forum, but.. does anyone know >> what happened to the binaries for lustre 1.6.7? ?They were released, >> that much I know. ?I even have them installed on some systems but... >> they''re no where to be found on the sun site. ?Was it pulled without >> announcement? > > To quote Peter Jones: > > A bug has been identified in 1.6.7 that can cause directory corruptions > on the MDT. A patch and full details are in bug 18695 - > https://bugzilla.lustre.org/show_bug.cgi?id=18695 > > We recommend to anyone running 1.6.7 on the MDS to unmount the MDT, run > e2fsck against the MDT device and apply the patch from bug 18695 as soon > as possible. > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >
I just went production with 1.6.7 last week using the RPMs. I do not have the source code for 1.6.7 to apply the patch. What is the recommended path for correction? Regards, +Ryan On Sat, Apr 11, 2009 at 12:29 PM, Mag Gam <magawake at gmail.com> wrote:> Hi John: > > Yes, I think it was pulled out. There was a serious issue with it. > > > On Fri, Apr 10, 2009 at 8:14 PM, Aaron Porter <atporter at gmail.com> wrote: > > On Fri, Apr 10, 2009 at 3:38 PM, John White <jwhite at lbl.gov> wrote: > >> Hey Folks, > >> So I''m not sure if this is the proper forum, but.. does anyone > know > >> what happened to the binaries for lustre 1.6.7? They were released, > >> that much I know. I even have them installed on some systems but... > >> they''re no where to be found on the sun site. Was it pulled without > >> announcement? > > > > To quote Peter Jones: > > > > A bug has been identified in 1.6.7 that can cause directory corruptions > > on the MDT. A patch and full details are in bug 18695 - > > https://bugzilla.lustre.org/show_bug.cgi?id=18695 > > > > We recommend to anyone running 1.6.7 on the MDS to unmount the MDT, run > > e2fsck against the MDT device and apply the patch from bug 18695 as soon > > as possible. > > _______________________________________________ > > Lustre-discuss mailing list > > Lustre-discuss at lists.lustre.org > > http://lists.lustre.org/mailman/listinfo/lustre-discuss > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20090412/bd91e5bb/attachment.html