From: Goffredo Baroncelli <kreijack@gmail.com>
To: Harald Glatt <mail@hachre.de>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Martin Steigerwald <Martin@lichtvoll.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/5] [RFC] RAID-level terminology change
Date: Sun, 10 Mar 2013 23:59:56 +0100 [thread overview]
Message-ID: <513D106C.4000806@gmail.com> (raw)
In-Reply-To: <CAFWF=amgMRcBaoTXZiFSEQnJkmayf7SPXddktbGuvN0q3qd7UA@mail.gmail.com>
On 03/10/2013 10:45 PM, Harald Glatt wrote:
> I've noticed through my own tests that on a single device I can
> corrupt around 5% of the data completely before btrfs fails. Up to
> that point both filesystem as well as data integrity stays at 100%.
> However the default layout for one disk seems to be having the data
> once, the metadata DUP and the system DUP too.
How make you the corruption ? Does btrfs return wrong data ? How is
calculated the 5% ?
> Having these 5% isn't
> mentioned anywhere... Is this a value that could maybe be manipulated
> and could it be introduced into a naming scheme like this? Also where
> do the 5% redundancy come from?
On a single device, the metadata are DUPlicated but the data have only 1
copy.
This means that if you corrupt the 1 copy of the metadata, btrfs
survives using the other copy. Instead if you corrupt the data btrfs
return an error.
> --
> 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
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2013-03-10 22:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 20:31 [PATCH 0/5] [RFC] RAID-level terminology change Hugo Mills
2013-03-09 20:31 ` [PATCH 1/5] Use nCmSpP format for mkfs Hugo Mills
2013-03-09 20:31 ` [PATCH 2/5] Move parse_profile to utils.c Hugo Mills
2013-03-09 20:31 ` [PATCH 3/5] Convert balance filter parser to use common nCmSpP replication-level parser Hugo Mills
2013-03-09 20:31 ` [PATCH 4/5] Change output of btrfs fi df to report new (or old) RAID names Hugo Mills
2013-03-09 20:31 ` [PATCH 5/5] Add man page description for nCmSpP replication levels Hugo Mills
2013-03-10 14:01 ` Goffredo Baroncelli
2013-03-10 17:20 ` Hugo Mills
2013-03-10 17:52 ` Goffredo Baroncelli
2013-03-09 21:38 ` [PATCH 0/5] [RFC] RAID-level terminology change Harald Glatt
[not found] ` <CAFWF=am4ki529Zez4123gYk3BD+Z9RONRpAK7NZe=skHzcdMiw@mail.gmail.com>
2013-03-09 21:46 ` Hugo Mills
2013-03-09 22:25 ` Roger Binns
2013-03-10 1:44 ` Hugo Mills
2013-03-10 5:41 ` Roger Binns
2013-03-10 6:29 ` Harald Glatt
2013-03-10 6:37 ` Harald Glatt
2013-03-10 11:31 ` Martin Steigerwald
2013-03-10 11:48 ` Roger Binns
2013-03-10 22:04 ` Hugo Mills
2013-03-11 0:21 ` Roger Binns
2013-03-27 4:27 ` Brendan Hide
2013-03-27 5:24 ` Roger Binns
2013-03-10 11:23 ` Martin Steigerwald
2013-03-10 14:11 ` Goffredo Baroncelli
2013-03-10 21:36 ` Hugo Mills
2013-03-10 21:45 ` Harald Glatt
2013-03-10 22:59 ` Goffredo Baroncelli [this message]
2013-03-10 22:06 ` Harald Glatt
2013-03-10 23:06 ` Diego Calleja
2013-03-10 15:43 ` Goffredo Baroncelli
2013-03-10 22:24 ` Hugo Mills
2013-03-10 22:42 ` Harald Glatt
2013-03-10 23:40 ` sam tygier
2013-03-10 23:49 ` Hugo Mills
2013-03-11 14:14 ` David Sterba
2013-03-10 23:55 ` sam tygier
2013-03-11 8:56 ` Hugo Mills
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=513D106C.4000806@gmail.com \
--to=kreijack@gmail.com \
--cc=Martin@lichtvoll.de \
--cc=hugo@carfax.org.uk \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=mail@hachre.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 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.