From: Emmanuel Florac <eflorac@intellique.com>
To: Ralf Gross <Ralf-Lists@ralfgross.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error xfs_da_do_buf(2)
Date: Wed, 22 Sep 2010 10:31:34 +0200 [thread overview]
Message-ID: <20100922103134.4e652651@galadriel.home> (raw)
In-Reply-To: <20100922072653.GA23326@pirx.askja.de>
Le Wed, 22 Sep 2010 09:26:53 +0200 vous écriviez:
> Infortrend RAID with BBU -> DRBD -> LVM -> XFS
I'm not sure to understand; DRBD is used to mirror devices, are you
using 2 Infortrend arrays, or one split into two volumes?
In any case, battery protected write cache shouldn't create any
corruption (OTOH it will enhance performance dramatically). AFAIK all
RAID arrays mirror the drives cache in the array cache until it hits
platters. There may be some "cheating" hard drives (I heard that WD
isn't always totally clear about cache policies) but Seagate and Hitachi
professional grade drives definitely are OK. Hint: don't use desktop
hard drives in any case because they probably cheat about cache
synchronisation.
I see that you may have been running rsync at the time of failure; there
are quite a lot of quite unclear (to me at least) cases of XFS failures
when running rsync to copy large amount of data. I it a fully 64 bits
system?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-22 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 7:26 XFS internal error xfs_da_do_buf(2) Ralf Gross
2010-09-22 8:31 ` Emmanuel Florac [this message]
2010-09-22 19:23 ` Ralf Gross
2010-09-22 8:32 ` Dave Chinner
2010-09-22 12:11 ` Ralf Gross
2010-09-22 23:24 ` Dave Chinner
2010-09-23 8:48 ` Ralf Gross
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=20100922103134.4e652651@galadriel.home \
--to=eflorac@intellique.com \
--cc=Ralf-Lists@ralfgross.de \
--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