--- Eric Sandeen <sandeen@xxxxxxx> wrote: > On Mon,
23 Feb 2004, Alexander Fisher wrote:
> > create by default. I would like to 'fix' my
> kernel so
> > that allocation group sizes above 4GB don't result
> > lockups.
> > Is there a patch I can use against the 1.3.1 xfs
> > release? I've looked at the fix included in
> > changeset 1.1276.1.2
> > but it doesn't apply to the official xfs release.
> That looks like the right patchset, I would not
> that it is -too- difficult to backport to 1.3.1,
> I have not looked... Your other workaround is to
> an older mkfs that does not make AGs > 4G (or
> specify 4G AGs with your mkfs).
> > On a related point, are there any plans to
> > any more official xfs releases or is it just
> > that people will use upto date linux kernels?
> Probably the latter, although I'm not quite certain
Unfortunately backporting the fix in any sensible time
period is beyond me. At least one of the files being
patched doesn't even exist in the 1.3.1 release. If I
try to remedy this by applying other updates to the
xfs code first I'm going to get into the situation
where other core kernel updates are also required.
These will too have their dependencies. I think it
really needs somebody who knows the xfs code and
understands the problem to produce a 1.3.1 fix.
You said that one of my workarounds would be to
downgrade xfstools (or at least mkfs.xfs). Wouldn't
it be better if the latest released version of
xfstools worked correctly with the latest released
version of xfs? Perhaps its possible for mkfs.xfs to
detect the use of xfs1.3.1 (and earlier?) and not
create large allocation groups under those conditions.
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now