From: Hugo Mills <hugo@carfax.org.uk>
To: "Christian Völker" <cvoelker@knebb.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Resizing BTRFS - raw partition
Date: Wed, 2 Nov 2016 09:29:26 +0000 [thread overview]
Message-ID: <20161102092926.GM16645@carfax.org.uk> (raw)
In-Reply-To: <6050c1f3-ff13-204c-ec32-3bcb62db7c5a@knebb.de>
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
On Wed, Nov 02, 2016 at 10:18:03AM +0100, Christian Völker wrote:
> Hi Hugo,
>
> thanks for the quick reply. Regarding version- I prefer to use stable
> Linux versions....and I am not going to upgrade just btrfs outside of
> the verndors builds. So I am stuck happily with this version. And I run
> Linux since more than 10years, so I am really fine with it, I guess :D
Well, btrfs-progs 0.19 was last released several years ago. If your
kernel is of the same kind of age, then you're going to be seeing a
whole load of really nasty data-corrupting or filesystem-breaking bugs
which have since been fixed. Basically, if something goes wrong with
your FS when you're running a kernel that old, the main rsponse you'll
get is, "well, that was silly of you, wasn't it?", and you'll have to
make a new filesystem and restore from your backups and hope it
doesn't happen again.
I would currently recommend running a 4.4 kernel or later. If you
want a "stable" kernel version from a distribution, and want some kind
of support for it when it goes wrong, you're probably going to have to
pay someone (Red Hat or SuSE, most likely) to support your
configuraion.
Hugo.
> And thanks again for your proposal. Yes, your command worked.
>
> I had to tell betrfs the devid!
>
> So this did NOT work:
>
> btrfs fi resize max /srv/share/
>
> Instead the following two commands worked:
>
> btrfs fi resize 1:max /srv/share/
> btrfs fi resize 2:max /srv/share/
>
> And now boths phydevices show the correct size.
>
> This sound really strange for me that I have to tell btrfs to resize
> just a single disk insteag of automatically resizing all disks...I bet
> next time I have it forgotten again :-(
>
>
> Greetings
>
>
> Christian
>
>
>
--
Hugo Mills | In one respect at least, the Martians are a happy
hugo@... carfax.org.uk | people: they have no lawyers
http://carfax.org.uk/ |
PGP: E2AB1DE4 | John Carter, A Princess of Mars
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-11-02 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 8:58 Resizing BTRFS - raw partition Christian Völker
2016-11-02 9:12 ` Hugo Mills
2016-11-02 9:18 ` Christian Völker
2016-11-02 9:29 ` Hugo Mills [this message]
2016-11-02 10:14 ` Adam Borowski
2016-11-02 10:16 ` Christian Völker
2016-11-02 11:40 ` Austin S. Hemmelgarn
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=20161102092926.GM16645@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=cvoelker@knebb.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 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.