Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Lukas Pirl <btrfs@lukas-pirl.de>
To: linux-btrfs@vger.kernel.org
Subject: implications of mixed mode
Date: Fri, 27 Nov 2015 12:54:57 +1300	[thread overview]
Message-ID: <56579BD1.4030401@lukas-pirl.de> (raw)

Dear list,

if a larger RAID file system (say disk space of 8 TB in total) is
created in mixed mode, what are the implications?

>From reading the mailing list and the Wiki, I can think of the following:

+ less hassle with "false positive" ENOSPC
- data and metadata have to have the same replication level
  forever (e.g. RAID 1)
- higher fragmentation
  (does this reduce with no(dir)atime?)
  -> more work for autodefrag

Is that roughly what is to be expected? Any implications on recovery etc.?

In the specific case, the file system usage is as follows:
* data spread over ~20 subvolumes
  * snapshotted with various frequencies
  * compression is used
* mostly archive storage
  * write once
  * read infrequently
* ~500GB of daily rsync'ed system backup

Thanks in advance,

Lukas

             reply	other threads:[~2015-11-26 23:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 23:54 Lukas Pirl [this message]
2015-11-27  2:21 ` implications of mixed mode Qu Wenruo
2015-11-27  5:40   ` Roman Mamedov
2015-11-27  3:11 ` Duncan
2015-11-27 10:30   ` Lukas Pirl
2015-11-28  6:08     ` Duncan

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=56579BD1.4030401@lukas-pirl.de \
    --to=btrfs@lukas-pirl.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox