From: Roman Mamedov <roman@rm.pp.ru>
To: Markus Hennig <mhennig@gmail.com>
Cc: linux-raid@vger.kernel.org, Neil Brown <neilb@suse.de>
Subject: Re: RAID5 crashed for unknown reason on old 2.6.16 kernel
Date: Thu, 15 Jul 2010 19:09:24 +0600 [thread overview]
Message-ID: <20100715190924.0f62890a@natsu> (raw)
In-Reply-To: <AANLkTilC9tPAVS2UWcJDykDyvkCDZbZjFD-R-h6OxRxi@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Thu, 15 Jul 2010 13:53:50 +0200
Markus Hennig <mhennig@gmail.com> wrote:
> I got all my data back from a degraded RAID5 array with 3 disks.
> The only point which is worth to mention: XFS as underlying file
> system is ineligible for small/cheap NAS because it is not edian safe.
> I bought a powerpc driven MAC to replay the XFS journal...
QEMU can emulate almost every modern architecture while running on almost any
different one, with various degrees of (understandable) slowness.
> That leads to my question to the list: does somebody know if BTRFS is
> endian safe or what is an endian-safe alternative to ext3/ext ?
I'd suggest to use Ext4 for now. You can always convert it to BTRFS at a later
time: https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-07-15 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 21:22 RAID5 crashed for unknown reason on old 2.6.16 kernel Markus Hennig
2010-06-28 15:29 ` Markus Hennig
2010-06-29 6:50 ` Neil Brown
2010-07-15 11:53 ` Markus Hennig
2010-07-15 13:09 ` Roman Mamedov [this message]
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=20100715190924.0f62890a@natsu \
--to=roman@rm.pp.ru \
--cc=linux-raid@vger.kernel.org \
--cc=mhennig@gmail.com \
--cc=neilb@suse.de \
/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).