public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Raz <raziebe@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: raid50 and 9TB volumes
Date: Mon, 16 Jul 2007 23:01:40 +1000	[thread overview]
Message-ID: <20070716130140.GC31489@sgi.com> (raw)
In-Reply-To: <5d96567b0707160542t2144c382mbfe3da92f0990694@mail.gmail.com>

On Mon, Jul 16, 2007 at 03:42:28PM +0300, Raz wrote:
> Hello
> I found that using xfs over raid50, ( two raid5's 8 disks each and
> raid 0 over them ) crashes the file system when the file system is ~
> 9TB. crashing is easy: we simply create few hundred of files, then
> erase them in bulk. the same test passes in 6.4TB filesystems.
> this bug happens in 2.6.22 as well as 2.6.17.7.
> thank you .
> 
> 4391322.839000] Filesystem "md3": XFS internal error
> xfs_alloc_read_agf at line 2176 of file fs/xfs/xfs_alloc.c.  Caller
> 0xc10d31ea
> [4391322.863000]  <c10d36e9> xfs_alloc_read_agf+0x199/0x220
> <c10d31ea> xfs_alloc_fix_freelist+0x41a/0x4b0

Judging by the kernel addresses (<c10d36e9>) you're running
an i386 kernel right? Which means there's probably a wrapping
issue at 8TB somewhere in the code which has caused an AGF
header to be trashed somewhere lower down in the filesystem.
what does /proc/partitions say? I.e. does the kernel see
the whole 9TB of space?

What does xfs_repair tell you about the corruption? (assuming
it doesn't OOM, which is a good chance if you really are on
i386).

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-07-16 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 12:42 raid50 and 9TB volumes Raz
2007-07-16 13:01 ` David Chinner [this message]
2007-07-16 13:57   ` Raz
2007-07-16 15:24     ` Eric Sandeen
     [not found]   ` <5d96567b0707160653m5951fac9v5a56bb4c92174d63@mail.gmail.com>
2007-07-16 22:18     ` David Chinner
2007-07-16 23:56       ` Neil Brown
2007-07-17  0:12         ` David Chinner
2007-07-17  0:54           ` Neil Brown
2007-07-17  0:58             ` David Chinner
2007-07-23  6:09               ` Raz
2007-07-24  1:01                 ` David Chinner
2007-08-07  9:20                   ` Raz
2007-09-03 14:24                     ` Raz
2007-09-03 18:55                       ` Christian Kujau
2007-09-04  2:50                         ` Eric Sandeen

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=20070716130140.GC31489@sgi.com \
    --to=dgc@sgi.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=raziebe@gmail.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