On Fri, Oct 12, 2001 at 11:33:07AM +1100, Nathan Scott wrote:
> hi,
>
> On Thu, Oct 11, 2001 at 09:54:12AM +0200, Robert Sander wrote:
> > On Thu, Oct 11, 2001 at 12:26:31PM +1100, Nathan Scott wrote:
> >
> > > Could you try switching OFF XFS quota support
> > > (but leaving the normal Quota support ON), and see if the problem
> > > persists?
> >
> > When switching off only XFS quotas it works! Seems to be nailed down:
> >
>
> Uhrm. Well, thats very odd.
Indeed. I've just experienced this problem as well. On a 2.4.10 kernel
patched with the xfs 2.4.10-9/25 patch, I too experience the "File size
limit exceeded" error. At first, I did have Quotas enabled. Following
suggestions to the list, I've disabled quota support and built a new
kernel... but the problem persists. I am still unable to mkfs.xfs
without getting this error.
> Let me see if we're on the same page - you have a system with no XFS
My system is *entirely* XFS based (even root) with a small 500Mb "rescue"
install on ext2 that I can boot to that holds /boot as well.
> Your failure is seen in dd(1), copying at the 2Gb mark, it prints out
> something like "File size limit exceeded" (ie. it receives a SIGXFSZ
> signal), and exits.
This is what happens when I do the same (XFS and lvm though):
# lvcreate -L3G -ntest vg
# dd if=/dev/zero of=/dev/vg/testlv bs=1M count=3000
File size limit exceeded
++ungood
> - So far, I haven't been able to reproduce the problem, eg. when
> dd'ing one 3Gb partition to another on my local machine, all quota
> switched on, with an XFS CVS kernel;
So far, it seems to break for me as well.
> - There is no possibility that any XFS quota code is being exectued
> in your setup (no XFS code at all), other than at bootup - where we
> don't do much, mainly just some global initialization (locks, memory
> allocation, etc) - so, I'm a bit amazed that switching off XFS quota
> can change the outcome at all here;
It doesn't fix me. I'm still broken.
> Its all very, very strange... I'm a little inclined to suspect the
> recent block device changes in 2.4.10/11 - the only XFS quota change
> recently was some minor changes to the quotactl interface, and this
> code wouldn't be executed at all in your setup.
I'm willing to give anything a try at this point... The box in question
is one of a pair of machines that were built similarly (99.9% identically).
Both machines are running the same 2.4.10 kernel and are exhibiting the same
problem.
Oddly enough, the "rescue" 2.4.7-xfs kernel that they were built with work
fine... one box was able to create and format a large 40G xfs volume
yesterday with the "rescue" 2.4.7-xfs boot kernel, and I've been fighting
with the other machine to do the same under the "normal" 2.4.10-xfs boot
kernel. No dice.
> Do you see any system console messages when you get the error?
None.
- Ian C. Blenke <ian@xxxxxxxxxx>
|