From: Steve Lord <lord@xfs.org>
To: alistair@devzero.co.uk
Cc: Nathan Scott <nathans@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: Copying huge amount of data on ReiserFS, XFS and Silicon Image 3112 cause oops.
Date: Tue, 14 Sep 2004 09:12:09 -0500 [thread overview]
Message-ID: <4146FC39.40104@xfs.org> (raw)
In-Reply-To: <200409141159.54889.alistair@devzero.co.uk>
Alistair John Strachan wrote:
> On Tuesday 14 September 2004 09:14, you wrote:
>
>>
>>Was 4KSTACKS enabled in those kernels (I think so)? - XFS
>>has one known problem with that option when running low on
>>space (patch fixing that is being tested atm) and I think
>>the reiserfs folks had some 4k stack issues as well at one
>>point, so that might be another explanation.
>>
>
>
> Just out of interest, how low is "low space"? I've got a few machines I can't
> reboot running XFS+4K stacks; no problems so far but I'd like to sidestep
> them if possible.
>
You would need to be within the size of the physical memory of your
box to having a full filesystem - as a very rough approximation. So 1Gbyte
memory, 1 Gbyte disk free. There is a path when XFS is attempting to
free up pre-reserved disk space to make room for a new write, it
does this by flushing data out to disk. This means it has to work
out where it is physically going to go, which usually results in it
taking less metadata space to reference the data than the worst case
estimate it previously made. For lots of cases this probably still
does not overflow the stack, but if you add in drivers like lvm
and md and a complex scsi driver it probably pushes you over the
limit.
In general though, I would rebuild without the 4K stacks and at least
have the kernel ready for a convenient reboot.
Steve
next prev parent reply other threads:[~2004-09-14 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 22:44 Copying huge amount of data on ReiserFS, XFS and Silicon Image 3112 cause oops Marcin Garski
2004-09-14 8:14 ` Nathan Scott
2004-09-14 10:59 ` Alistair John Strachan
2004-09-14 14:12 ` Steve Lord [this message]
2004-09-14 15:01 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2004-09-14 15:42 Marcin Garski
2004-09-14 19:04 Christian Guggenberger
2004-09-18 21:18 Marcin Garski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4146FC39.40104@xfs.org \
--to=lord@xfs.org \
--cc=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox