I see it is fixed now as we were being bit by this. We would like to put the new filesystem into use on Monday thus we are trying to get this resolved. Question, because it is just a parsing problem in mkfs, can after the filesystem is created can the problem be corrected? If not, how can we work around this? Do I just need to build the mkfs out of CVS for 1.6.6 ? Brock Palen www.umich.edu/~brockp Center for Advanced Computing brockp at umich.edu (734)936-1985
Hi, I never did get a reply for this. We are faced with planned production on Monday, so we could really use some guidance. What is the quickest work around for working around bug 15912, there are patches now but they are for unreleased versions. We need a solution for the current 1.6.5.1. Can I change the MGSSPEC for the OST''s after the fact? And will that work? How would this be done? Thanks ahead of time. Brock Palen www.umich.edu/~brockp Center for Advanced Computing brockp at umich.edu (734)936-1985 On Aug 14, 2008, at 11:15 AM, Brock Palen wrote:> I see it is fixed now as we were being bit by this. > We would like to put the new filesystem into use on Monday thus we > are trying to get this resolved. > > Question, because it is just a parsing problem in mkfs, can after the > filesystem is created can the problem be corrected? > > If not, how can we work around this? Do I just need to build the > mkfs out of CVS for 1.6.6 ? > > > Brock Palen > www.umich.edu/~brockp > Center for Advanced Computing > brockp at umich.edu > (734)936-1985 > > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss > >
Ignore, After days of banging head against the wall and trying to use tunefs.lustre which appears to maybe suffer from the same bug. I found the alternative that specifying --mgsnode= more than once was valid. This mixed with the wonderful --print option to mkfs.lustre I think I have my work around. mkfs.lustre --reformat --ost --fsname=nobackup --mgsnode=mds1 -- mgsnode=mds2 --mkfsoptions -j "-J device=/dev/md27" /dev/md17 Thanks, Though I am scared about behavior of tunefs.lustre if we ever needed to re-ip the nodes. Re-formating is not really an option. Brock Palen www.umich.edu/~brockp Center for Advanced Computing brockp at umich.edu (734)936-1985 On Aug 18, 2008, at 8:16 PM, Brock Palen wrote:> Hi, > I never did get a reply for this. We are faced with planned > production on Monday, so we could really use some guidance. > > What is the quickest work around for working around bug 15912, > there are patches now but they are for unreleased versions. We > need a solution for the current 1.6.5.1. > > Can I change the MGSSPEC for the OST''s after the fact? And will > that work? > How would this be done? > > Thanks ahead of time. > > Brock Palen > www.umich.edu/~brockp > Center for Advanced Computing > brockp at umich.edu > (734)936-1985 > > > > On Aug 14, 2008, at 11:15 AM, Brock Palen wrote: >> I see it is fixed now as we were being bit by this. >> We would like to put the new filesystem into use on Monday thus we >> are trying to get this resolved. >> >> Question, because it is just a parsing problem in mkfs, can after the >> filesystem is created can the problem be corrected? >> >> If not, how can we work around this? Do I just need to build the >> mkfs out of CVS for 1.6.6 ? >> >> >> Brock Palen >> www.umich.edu/~brockp >> Center for Advanced Computing >> brockp at umich.edu >> (734)936-1985 >> >> >> >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss >> >> > > >
On Tuesday 19 August 2008 03:57:55 Brock Palen wrote:> Ignore, > > After days of banging head against the wall and trying to use > tunefs.lustre which appears to maybe suffer from the same bug. I > found the alternative that specifying --mgsnode= more than once was > valid. This mixed with the wonderful --print option to mkfs.lustre > I think I have my work around. > > mkfs.lustre --reformat --ost --fsname=nobackup --mgsnode=mds1 -- > mgsnode=mds2 --mkfsoptions -j "-J device=/dev/md27" /dev/md17Yes, this way I also do it all the time.> > Thanks, > Though I am scared about behavior of tunefs.lustre if we ever needed > to re-ip the nodes. Re-formating is not really an option.But tunefs.lustre also accepts more than one "--mgsnode". Cheers, Bernd -- Bernd Schubert Q-Leap Networks GmbH