From: Roman Mamedov <rm@romanrm.net>
To: Neko-san <nekoNexus@proton.me>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [Help?] "errors" found in fs roots
Date: Tue, 3 May 2022 15:31:28 +0500 [thread overview]
Message-ID: <20220503153128.6a641de6@nvm> (raw)
In-Reply-To: <20220502222210.6893657f@nvm>
On Mon, 2 May 2022 22:22:10 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> It could be most people thought it was too much of a barrier to entry to just
> "take a look". I have downloaded your files and attaching them to this E-Mail
> now. Let's see if it goes through -- raw files didn't, but in gzip it's not
> anything huge after all.
I'm not a Btrfs developer, so not sure if those btrfs check errors matter much
or not.
Some general advice though, maybe you could try command-line tools to resize?
I always do:
- btrfs fi resize to a lower size than planned, to leave some safety
headroom (10-100 GB) and not get bitten by any possible GB vs GiB
confusion;
- resize the partition with GNU fdisk, or the volume with lvresize;
- btrfs fi resize again, this time to "max", to fill the exact resulting size
of the partition.
--
With respect,
Roman
prev parent reply other threads:[~2022-05-03 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 6:19 [Help?] "errors" found in fs roots Neko-san
2022-05-02 16:51 ` Neko-san
2022-05-02 17:22 ` Roman Mamedov
2022-05-03 10:31 ` 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=20220503153128.6a641de6@nvm \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nekoNexus@proton.me \
/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.