From: Chris Meadors <clubneon@hereintown.net>
To: linux-kernel@vger.kernel.org
Subject: Re: xfs problems (2.6.0-test2)
Date: 01 Aug 2003 00:38:02 -0400 [thread overview]
Message-ID: <1059712682.1982.3.camel@clubneon.clubneon.com> (raw)
In-Reply-To: <20030801024041.GA732@frodo>
On Thu, 2003-07-31 at 22:40, Nathan Scott wrote:
> Hi there,
>
> What XFS blocksize are you using, and what is your page size?
> There are known issues when using blocksizes smaller than the
> page size in the 2.6 XFS code at the moment.
>
> Feel free to open bugs for this and your repair problems on the
> XFS site on oss.sgi.com; the gdb backtrace of the failed repair
> attempts will be useful as well.
I believe there was a post this past weekend about block sizes (or maybe
fragment sizes) on the Opteron. It wasn't with XFS I'm pretty sure. I
tried searching for it, but can't find it again.
I'm going to start playing with an Opteron pretty soon. I will be using
XFS. What are the recommended settings when creating file systems?
--
Chris
next prev parent reply other threads:[~2003-08-01 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 2:31 xfs problems (2.6.0-test2) Mariusz Zielinski
2003-08-01 2:40 ` Nathan Scott
2003-08-01 4:38 ` Chris Meadors [this message]
2003-08-01 7:58 Jose Luis Alarcon
2003-08-01 13:55 ` Steve Lord
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=1059712682.1982.3.camel@clubneon.clubneon.com \
--to=clubneon@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).