From: Chris Mason <chris.mason@oracle.com>
To: Bill Pemberton <wfp5p@viridian.itc.virginia.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: assertion failures
Date: Fri, 26 Feb 2010 12:59:27 -0500 [thread overview]
Message-ID: <20100226175927.GG12841@think> (raw)
In-Reply-To: <20100226164151.9830F414B9@viridian.itc.virginia.edu>
On Fri, Feb 26, 2010 at 11:41:51AM -0500, Bill Pemberton wrote:
> > >
> > > No dmesg. This has happened on two different machines that both have
> > > other active btrfs filesystems, so I suspect it's not a memory issue.
> > > In both cases it was the same data that was being copied when the
> > > crash occurred.
> >
> > Ok, is there anything special about this data?
> >
>
> There shouldn't be, it's the various backup files from a few
> machines. The only thing odd that I've seen in the data is there is
> at least 1 file with some less-than-normally-used characters in the
> name.
>
> Rsyncing it from an ext4 fs to a btrfs fileystem on the same array
> didn't cause the problem. The original user was doing the rsync
> remotely, so I don't know the exact options he was using.
Ok, rsync doesn't do anything especially scarey.
>
>
> >
> > What kind of array is this? It really sounds like the IO isn't
> > happening properly.
> >
>
> Yeah, I'd be keen on blaming the arrays and/or machines if it weren't
> for the fact that we have other btrfs filesystems on these machines
> that hum along fine.
>
> The array is from RAIDKing. It's SCSI attached using SATA disks. I
> can get the exact module number if it'll help. The SCSI card is a LSI
> 53c1030 (again, let me know if you need exact make/model).
Does the array have any kind of writeback cache?
Are all of the filesystems spread across all of the drives? Or do some
filesystems use some drives only?
-chris
next prev parent reply other threads:[~2010-02-26 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 13:45 assertion failures Bill Pemberton
2010-02-25 0:40 ` Chris Mason
2010-02-25 14:04 ` Bill Pemberton
2010-02-25 18:28 ` Gustavo Alves
2010-02-26 16:13 ` Chris Mason
2010-02-26 16:15 ` Chris Mason
2010-02-26 19:57 ` Gustavo Alves
2010-02-26 21:10 ` Chris Mason
2010-02-26 21:26 ` Gustavo Alves
2010-02-26 16:17 ` Chris Mason
2010-02-26 16:41 ` Bill Pemberton
2010-02-26 17:59 ` Chris Mason [this message]
2010-02-26 18:11 ` Bill Pemberton
2010-02-26 19:09 ` Chris Mason
2010-02-26 20:43 ` Bill Pemberton
2010-02-26 20:49 ` Diego Calleja
2010-02-26 21:08 ` Chris Mason
2010-02-28 3:05 ` Cláudio Martins
2010-02-26 19:11 ` Mike Fedyk
2010-02-26 19:15 ` Chris Mason
2010-02-26 20:45 ` Bill Pemberton
2010-02-26 20:53 ` Chris Mason
2010-02-27 22:56 ` Bill Pemberton
2010-02-26 20:44 ` Bill Pemberton
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=20100226175927.GG12841@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wfp5p@viridian.itc.virginia.edu \
/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