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
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
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
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
