From: Daniel Pocock <daniel@pocock.com.au>
To: linux-btrfs@vger.kernel.org
Subject: Re: interaction with hardware RAID?
Date: Mon, 27 Aug 2012 16:53:21 +0200 [thread overview]
Message-ID: <503B89E1.7030809@pocock.com.au> (raw)
In-Reply-To: <5034BD0D.8050706@pocock.com.au>
Just following up on this... does anyone know if any of this is
technically feasible even if not implemented/supported today?
Also, do any hardware RAID1 implementations offer something like the
full btrfs checksum functionality?
I've seen HP promoting their `Advanced Data Mirroring' in new Smart
Array products, but I've got no idea if that is just a marketing
gimmick, like the way they use the name `Advanced Data Guard' as a
moniker for RAID6
Looking around in Google, I was pleasantly disturbed to find so many web
sites (including some vendors) using the term `checksum' to refer to a
parity bit
On 22/08/12 13:05, Daniel Pocock wrote:
>
>
>
> It is well documented that btrfs data recovery (after silent corruption)
> is dependent on the use of btrfs's own RAID1.
>
> However, I'm curious about whether any hardware RAID vendors are
> contemplating ways to integrate more closely with btrfs, for example,
> such that when btrfs detects a bad checksum, it would be able to ask the
> hardware RAID controller to return all alternate copies of the block.
>
> Is this technically possible within any hardware RAID device today, even
> though not implemented in btrfs?
>
> Has there been any suggestion that vendors would support this in future,
> presumably for the benefit of btrfs, ZFS and other checksumming filesystems?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-08-27 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 11:05 interaction with hardware RAID? Daniel Pocock
2012-08-27 14:53 ` Daniel Pocock [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=503B89E1.7030809@pocock.com.au \
--to=daniel@pocock.com.au \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.