From: Roman Mamedov <rm@romanrm.net>
To: "David C. Rankin" <drankinatty@suddenlinkmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recommendations for RAID setup needed
Date: Tue, 22 Sep 2015 10:03:04 +0500 [thread overview]
Message-ID: <20150922100304.2372d85c@natsu> (raw)
In-Reply-To: <5600D61A.6000908@suddenlinkmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On Mon, 21 Sep 2015 23:16:26 -0500
"David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
> This is the exact reason NOT to use btrfs at the moment. The issue is
> with the 'snap shotting' feature which can quietly fill your disk with
> snap shots to the point of space exhaustion that has resulted in the
> complete loss of information in a number of instances.
Snapshots is not something Btrfs "quietly" makes on its own, snapshots are
something *you* create. Snapshots of static and unmodified data are essentially
free in terms of disk space (due to CoW only the changes from the point
snapshot was taken and further on, will require additional space); and if you
heavily modify your files and want to also keep a trail of snapshots, it's of
course up to you to ensure you have enough disk space for that.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-09-22 5:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 17:39 Recommendations for RAID setup needed Alex
2015-09-15 18:08 ` Wols Lists
2015-09-15 18:44 ` Alex
2015-09-16 2:12 ` Adam Goryachev
2015-09-16 10:03 ` Jens-U. Mozdzen
2015-09-16 15:53 ` Alex
2015-09-18 11:25 ` Michael Tokarev
2015-09-18 12:55 ` Alex
2015-09-15 18:57 ` Roman Mamedov
2015-09-22 4:18 ` David C. Rankin
2015-09-22 4:16 ` David C. Rankin
2015-09-22 5:03 ` Roman Mamedov [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=20150922100304.2372d85c@natsu \
--to=rm@romanrm.net \
--cc=drankinatty@suddenlinkmail.com \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).