From: Mike Grant <mggr@pml.ac.uk>
To: xfs@oss.sgi.com
Subject: XFS stack overflows
Date: Thu, 17 May 2012 20:09:18 +0100 [thread overview]
Message-ID: <4FB54CDE.9010100@pml.ac.uk> (raw)
I was googling around for stack overflow problems with large XFS
filesystems and came across http://lwn.net/Articles/476562/ where Dave
asked people to email in occurrences of this problem (good article
btw!). I can confirm that we've had regular crashes on our RHEL6 box
(2.6.32-131.6.1.el6.x86_64) with a 60TB XFS filesystem*. We've
confirmed the crashes are stack overflows in XFS allocation from looking
at crash dumps. This is medium-reproducible by writing to the
filesystem over NFS. RH have had a case open (#00414047) open on this
issue since Feb 2011, though I don't know if it's been filtered upstream.
The last email I see on the subject on this list was
http://oss.sgi.com/archives/xfs/2011-12/msg00264.html where Dave
mentioned a patch, but recommended rebuilding the kernel with 16k
stacks. Is this patch likely to be applied or has it been already? If
not, presumably the 16k stack rebuild is the best way to go for a
working system?
Cheers,
Mike.
* Subsequently we've been limiting all XFS filesystems to a maximum of
30TB and haven't seen problems with those (other than data management
issues because our datasets are much bigger than 30TB). While this is
still somewhat of a niche issue, cheap 48TB NAS servers are increasingly
common (~$10k). As XFS is the only mainstream Linux filesystem capable
of handling these volumes, I imagine more people are likely to run into
this issue over time.
--
PGP: 0xD4925D35 (5A17 756C 3F78 27DB C641 F50C 05EC 4F23 D492 5D35)
*******************************************************************
Plymouth Marine Laboratory, Prospect Place, Plymouth, UK. PL4 9PN.
PML is a company limited by guarantee and a registered charity.
Registered England & Wales company no:4178503; charity no:1091222
http://www.pml.ac.uk/
This email is confidential and for the intended recipient(s) only.
Terms and legal disclaimers apply: http://rsg.pml.ac.uk/email.html
*******************************************************************
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2012-05-17 19:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FB54CDE.9010100@pml.ac.uk \
--to=mggr@pml.ac.uk \
--cc=xfs@oss.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