All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waxhead <waxhead@online.no>
To: linux-btrfs@vger.kernel.org
Subject: Is btrfsck really required?
Date: Sun, 25 Mar 2012 18:36:34 +0200	[thread overview]
Message-ID: <4F6F4992.9030100@online.no> (raw)

After playing around with btrfs for a while, reading about it and also 
watching Avi Miller's presentation on youtube I am starting to wonder 
why one would need btrfsck at all. I am no expert in filesystems so I 
apologize if any of these questions may sound a bit stupid.

1. How "self-healing" is btrfs really?! According to Miller's talk btrfs 
is making a (circular?) backup of the root tree every 30 seconds.
If I remember correctly the root tree is also mirrored several places on 
disk and on rotational media all those are updated in tandem. This is 
leading me to believe that there should be no problem in recovering from 
a corruption.

2. Also in addition to question 1. Is there some sanity checking when 
writing the root tree? e.g. if you write garbage to the root tree by 
accident will there be some recovery mechanism there to protect you as well?

3. What is the point with the mount -o recovery ? If there already is a 
corruption there is there any reason btrfs should not recover 
automatically by itself?

4. If a disk responds slowly, Will btrfs throw it out of a raid 
configuration and if so will a btrfsck be less strict about timeouts and 
will it automatically rebalance the data from the bad disk over to other 
good disks?!


                 reply	other threads:[~2012-03-25 16:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F6F4992.9030100@online.no \
    --to=waxhead@online.no \
    --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.