public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Ashton <mike@fysh.org>
To: xfs@oss.sgi.com
Subject: XFS and 4k stacks/newer kernels.
Date: Fri, 24 Aug 2007 11:38:47 +0100	[thread overview]
Message-ID: <20070824103846.GC13240@fysh.org> (raw)

Hi folks,

Firstly, I must apologise for the tremendously vague nature of this
"report".  I do hope it's of some use, and it's the best I can do at
the moment.

I've been using XFS for several years now on a raid6 partition on a
15-disk array on linux 2.6.19 without 4k stacks, and without incident.
And a very nice filesystem it is too.

I've just set up a new one based on exactly the same hardware but with
a 2.6.22.3 kernel (and thus with compulsory 4k stacks, as I understand
it?).  During a large rsync to populate the filesystem, the write to
local disk blocked in a fast device wait, but without any errors in
dmesg.  After giving it half an hour to wake up again, I hard rebooted
and the XFS superblock was unreadable; bye bye filesystem.

So I've rolled back to 2.6.19, unsurprisingly, but I wanted to let you
know that some issues with 4k stacks or other features of newer
kernels may not have been resolved yet.  Since there were no errors,
I've nothing specific to give you, which I appreciate gives you little
to go on.  It wouldn't be right to leave this anecdote unreported,
however.

Best of luck and thanks,
Mike.

             reply	other threads:[~2007-08-24 11:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 10:38 Mike Ashton [this message]
2007-08-24 15:35 ` XFS and 4k stacks/newer kernels Chris Wedgwood

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=20070824103846.GC13240@fysh.org \
    --to=mike@fysh.org \
    --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