From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-btrfs@vger.kernel.org
Subject: Re: general thoughts and questions + general and RAID5/6 stability?
Date: Mon, 22 Sep 2014 22:51:08 +0200 [thread overview]
Message-ID: <54208BBC.1000700@xunil.at> (raw)
In-Reply-To: <pan$5a87e$97e2e260$54942ad0$cefe56f1@cox.net>
Am 20.09.2014 um 11:32 schrieb Duncan:
> What I do as part of my regular backup regime, is every few kernel cycles
> I wipe the (first level) backup and do a fresh mkfs.btrfs, activating new
> optional features as I believe appropriate. Then I boot to the new
> backup and run a bit to test it, then wipe the normal working copy and do
> a fresh mkfs.btrfs on it, again with the new optional features enabled
> that I want.
Is re-creating btrfs-filesystems *recommended* in any way?
Does that actually make a difference in the fs-structure?
So far I assumed it was enough to keep the kernel up2date, use current
(stable) btrfs-progs and run some scrub every week or so (not to mention
backups .. if it ain't backed up, it was/isn't important).
Stefan
next prev parent reply other threads:[~2014-09-22 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 20:50 general thoughts and questions + general and RAID5/6 stability? William Hanson
2014-09-20 9:32 ` Duncan
2014-09-22 20:51 ` Stefan G. Weichinger [this message]
2014-09-23 12:08 ` Austin S Hemmelgarn
2014-09-23 13:06 ` Stefan G. Weichinger
2014-09-23 13:38 ` Austin S Hemmelgarn
2014-09-23 13:51 ` Stefan G. Weichinger
2014-09-23 14:24 ` Tobias Holst
2014-09-24 1:08 ` Qu Wenruo
[not found] ` <CAGwxe4i2gQXSPiBGXbUKWid3o1tmD_+YtbOj=GQ11vzGx8CuTw@mail.gmail.com>
2014-09-23 14:47 ` Austin S Hemmelgarn
2014-09-23 15:25 ` Kyle Gates
2014-09-25 7:15 ` Stefan G. Weichinger
-- strict thread matches above, loose matches on Subject: below --
2014-08-31 4:02 Christoph Anton Mitterer
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=54208BBC.1000700@xunil.at \
--to=lists@xunil.at \
--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.