From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: runtime btrfsck
Date: Thu, 11 May 2017 14:03:24 +0000 (UTC) [thread overview]
Message-ID: <pan$4d4b8$c6068466$2883d412$cf40ce2b@cox.net> (raw)
In-Reply-To: 20170510135255.790fbe39@natsu
Roman Mamedov posted on Wed, 10 May 2017 13:52:55 +0500 as excerpted:
> So even with a minor corruption (something wonky in just ONE block of a
> multi-terabyte FS) the answer is way too often "nuke the entire thing
> and restore from backups".
Just another case where my "keep it small enough to be maintainable"
policy triggers. If that double-digit-TB fs is instead broken along
functional/logical lines into say a dozen 1 TB each fs and that single
block is corrupted, it can only be corrupted in one of them, so 11 of the
dozen will be fine, and nuking to restore from backups just the single 1
TB filesystem of a dozen, instead of the single 12-TB fs, isn't such a
big deal -- it remains realistically maintainable.
Of course if at your scale 12 TB... or 12000 TB... is considered
maintainable, great, but then we'd be unlikely to be having this
discussion...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2017-05-11 14:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 6:29 runtime btrfsck Stefan Priebe - Profihost AG
2017-05-06 5:56 ` Stefan Priebe - Profihost AG
2017-05-10 7:02 ` Stefan Priebe - Profihost AG
2017-05-10 7:18 ` Roman Mamedov
2017-05-10 7:36 ` Stefan Priebe - Profihost AG
2017-05-10 7:40 ` Hugo Mills
2017-05-10 8:40 ` Stefan Priebe - Profihost AG
2017-05-10 9:08 ` Hugo Mills
2017-05-10 9:20 ` Stefan Priebe - Profihost AG
2017-05-10 9:54 ` Hugo Mills
2017-05-10 11:23 ` Stefan Priebe - Profihost AG
2017-05-10 7:24 ` Marat Khalili
2017-05-10 7:48 ` Martin Steigerwald
2017-05-10 8:42 ` Stefan Priebe - Profihost AG
2017-05-10 8:52 ` Roman Mamedov
2017-05-11 14:03 ` Duncan [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='pan$4d4b8$c6068466$2883d412$cf40ce2b@cox.net' \
--to=1i5t5.duncan@cox.net \
--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.