From: Hugo Mills <hugo@carfax.org.uk>
To: Dmitry Katsubo <dmitry.katsubo@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Recover btrfs volume which can only be mounded in read-only mode
Date: Thu, 15 Oct 2015 14:55:09 +0000 [thread overview]
Message-ID: <20151015145509.GS25907@carfax.org.uk> (raw)
In-Reply-To: <CAOGcOQGnHaZeiyuqm+rSX=MBNSFnE-JwSmnhTWZVU42FnSgXmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
On Thu, Oct 15, 2015 at 04:10:13PM +0200, Dmitry Katsubo wrote:
[snip]
> If I may ask:
>
> Provided that btrfs allowed to mount a volume in read-only mode – does
> it mean that add data blocks are present (e.g. it has assured that add
> files / directories can be read)?
>
> Do you have any ideas why "btrfs balance" has pulled all data to two
> drives (and not balanced between three)?
If you're using a non-striped RAID level (single, 1), btrfs will
start by filling up the largest devices first: balance attempts to
make the free space equal across the devices, not to make the used
space equal.
If you're using a striped RAID level (0, 5, 6), then the FS will
fill up the devices equally, until one is full, and then switch to
using the remaining devices (until one is full, etc).
> Does btrfs has the following optimization for mirrored data: if drive
> is non-rotational, then prefer reads from it? Or it simply schedules
> the read to the drive that performs faster (irrelative to rotational
> status)?
No, it'll read arbitrarily from the available devices at the moment.
Hugo.
--
Hugo Mills | People are too unreliable to be replaced by
hugo@... carfax.org.uk | machines.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Nathan Spring, Star Cops
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-10-15 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:28 Recover btrfs volume which can only be mounded in read-only mode Dmitry Katsubo
2015-10-14 14:40 ` Anand Jain
2015-10-14 20:27 ` Dmitry Katsubo
2015-10-15 0:48 ` Duncan
2015-10-15 14:10 ` Dmitry Katsubo
2015-10-15 14:55 ` Hugo Mills [this message]
2015-10-16 8:18 ` Duncan
2015-10-18 9:44 ` Dmitry Katsubo
2015-10-26 7:09 ` Duncan
2015-10-26 9:14 ` Duncan
2015-10-26 9:24 ` Hugo Mills
2015-10-27 5:58 ` 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=20151015145509.GS25907@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=dmitry.katsubo@gmail.com \
--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.