public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <lionel-subscription@bouton.name>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Error: Failed to read chunk root, fs destroyed
Date: Fri, 24 Jul 2020 01:50:34 +0200	[thread overview]
Message-ID: <afcc2974-b85b-1963-4a8f-e06727d1b567@bouton.name> (raw)
In-Reply-To: <CAPtuuyGHcpqmCgQeXb6841zK=JLiHmJwJ80OdxKPFJ1KH=q=hw@mail.gmail.com>

Hi,

Le 23/07/2020 à 23:51, Davide Palma a écrit :
> Dear Lionel,
>
> > I probably won't be able to help but while this is fresh in your memory
> > please try to remember the exact sequence.
>
> I wish I could give you the .bash_history file,  but the sequence is
> the one I wrote. I tried running many balances before the ramdisk
> stuff by starting with -musage=0 and -dusage=0 and got to about 30
> before it started looping, I don't think this is useful but now you
> have 100% of my memory :)
>
> > If that's indeed the case, removing the loop device later on will indeed
> > break the filesystem as several metadata block groups will be entirely
> > missing (dup will probably have allocated the two duplicates on the loop
> > block device where space was available).
>
> Doesn't this defeat the whole point of raid1?

My point is that I saw nothing that pointed to raid1 being used on your
filesystem in the list of steps you described. I understand it was your
intent to use raid1 (although it isn't clear why as you didn't provide a
link for the advice you were following) but I'm not sure you actually did.

Simply adding a device to a BTRFS filesystem doesn't convert your
filesystem block groups it only adds usable space. You'd need to use a
balance command for converting the block groups to raid1.
Something like :
btrfs balance start -mconvert=raid1 -dconvert=raid1 <yourfs>

Best regards,

Lionel

  parent reply	other threads:[~2020-07-23 23:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 21:15 Error: Failed to read chunk root, fs destroyed Davide Palma
2020-07-23 21:40 ` Lionel Bouton
     [not found]   ` <CAPtuuyGHcpqmCgQeXb6841zK=JLiHmJwJ80OdxKPFJ1KH=q=hw@mail.gmail.com>
2020-07-23 23:50     ` Lionel Bouton [this message]
     [not found]     ` <15da0462-de7e-17ab-f89c-9f373a34fd97@bouton.name>
2020-07-24 12:43       ` Davide Palma
2020-07-26  0:01 ` Zygo Blaxell
2020-07-26  0:11   ` Zygo Blaxell
2020-07-30  9:26     ` Davide Palma

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=afcc2974-b85b-1963-4a8f-e06727d1b567@bouton.name \
    --to=lionel-subscription@bouton.name \
    --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