Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Russell Coker <russell@coker.com.au>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: staggered stripes
Date: Thu, 15 May 2014 10:34:10 +0100	[thread overview]
Message-ID: <20140515093410.GJ23212@carfax.org.uk> (raw)
In-Reply-To: <2751140.Zb1qMBeNgk@xev>

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

On Thu, May 15, 2014 at 07:00:10PM +1000, Russell Coker wrote:
> http://www.cs.wisc.edu/adsl/Publications/corruption-fast08.html
> 
> Page 13 of the above paper says:
> 
> # Figure 12 presents for each block number, the number of disk drives of disk
> # model ‘E-1’ that developed a checksum mismatch at that block number. We see
> # in the figure that many disks develop corruption for a specific set of block
> # numbers. We also verified that (i) other disk models did not develop
> # multiple check-sum mismatches for the same set of block numbers (ii) the
> # disks that developed mismatches at the same block numbers belong to
> # different storage systems, and (iii) our software stack has no specific data
> # structure that is placed at the block numbers of interest.
> #
> # These observations indicate that hardware or firmware bugs that affect
> # specific sets of block numbers might exist. Therefore, RAID system designers
> # may be well-advised to use staggered stripes such that the blocks that form
> # a stripe (providing the required redundancy) are placed at different block
> # numbers on different disks.
> 
> Does the BTRFS RAID functionality do such staggered stripes?  If not could it 
> be added?

   Yes, it could, by simply shifting around the chunk locations at
allocation time. I'm working in this area at the moment, and I think
it should be feasible within the scope of what I'm doing. I'll add it
to my list of things to look at.

   Hugo.

> I guess there's nothing stopping a sysadmin from allocating an unused 
> partition at the start of each disk and use a different size for each disk.  
> But I think it would be best to do this inside the filesystem.
> 
> Also this is another reason for having DUP+RAID-1.
> 

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
         --- If you're not part of the solution, you're part ---         
                           of the precipiate.                            

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      parent reply	other threads:[~2014-05-15  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15  9:00 staggered stripes Russell Coker
2014-05-15  9:31 ` Duncan
2014-05-15 14:38   ` Russell Coker
2014-05-15 16:15     ` Brendan Hide
2014-05-15 16:18     ` Hugo Mills
     [not found]   ` <2Ee51o00g0uXw0U01Ee7j5>
2014-05-16  4:17     ` Duncan
2014-05-15  9:34 ` Hugo Mills [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=20140515093410.GJ23212@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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