[Help?] "errors" found in fs roots

[Help?] "errors" found in fs roots

[Neko-san]

Hello; I'm having a bit of trouble resizing my BTRFS partition...
It mounts fine, but "btrfs check" reports errors and prevented my GUI disk management software from performing the operation.

I would appreciate help in figuring out how to fix this without destroying ~2 TBs of data... please. >_<

```
neko-san@ARCH ~> btrfs check --readonly --progress /dev/sda3 &> btrfs-check.log

neko-san@ARCH ~> uname -a
                       btrfs --version
                       btrfs fi show
                       btrfs fi df /mnt/extraStorage/
                       sudo dmesg > dmesg.log
Linux ARCH 5.17.2-256-tkg-pds-llvm #1 TKG SMP PREEMPT Wed, 13 Apr 2022 20:30:30 +0000 x86_64 GNU/Linux
btrfs-progs v5.17
Label: none  uuid: 5761f276-9f47-4195-a5b2-c21ff4f3fea5
        Total devices 1 FS bytes used 181.35GiB
        devid    1 size 198.11GiB used 198.11GiB path /dev/nvme0n1p2

Label: 'extraStorage'  uuid: 9d14e17d-66d4-41e7-95a4-8125f75b4d2b
        Total devices 1 FS bytes used 2.16TiB
        devid    1 size 2.18TiB used 2.18TiB path /dev/sda3

Data, single: total=194.01GiB, used=179.33GiB
System, single: total=4.00MiB, used=48.00KiB
Metadata, single: total=4.09GiB, used=2.03GiB
GlobalReserve, single: total=370.78MiB, used=0.00B
doas (neko-san@ARCH) password:
neko-san@ARCH ~>
```
(The logs are too big for this email, so here's a cloud link:
https://mega.nz/file/QrJRUQ5D#NCt5T6dpwS8VGWOrxPGdFK2M9nkURJ2ekH-YugFvVuc )

Re: [Help?] "errors" found in fs roots

[Neko-san]

Is no one willing to help with this?

------- Original Message -------
On Monday, May 2nd, 2022 at 6:19 AM, Neko-san <nekoNexus@proton.me> wrote:


> Hello; I'm having a bit of trouble resizing my BTRFS partition...
> It mounts fine, but "btrfs check" reports errors and prevented my GUI disk management software from performing the operation.
>
> I would appreciate help in figuring out how to fix this without destroying ~2 TBs of data... please. >_<
>
>
> ```
> neko-san@ARCH ~> btrfs check --readonly --progress /dev/sda3 &> btrfs-check.log
>
>
> neko-san@ARCH ~> uname -a
>
> btrfs --version
> btrfs fi show
> btrfs fi df /mnt/extraStorage/
> sudo dmesg > dmesg.log
>
> Linux ARCH 5.17.2-256-tkg-pds-llvm #1 TKG SMP PREEMPT Wed, 13 Apr 2022 20:30:30 +0000 x86_64 GNU/Linux
> btrfs-progs v5.17
> Label: none uuid: 5761f276-9f47-4195-a5b2-c21ff4f3fea5
> Total devices 1 FS bytes used 181.35GiB
> devid 1 size 198.11GiB used 198.11GiB path /dev/nvme0n1p2
>
> Label: 'extraStorage' uuid: 9d14e17d-66d4-41e7-95a4-8125f75b4d2b
> Total devices 1 FS bytes used 2.16TiB
> devid 1 size 2.18TiB used 2.18TiB path /dev/sda3
>
> Data, single: total=194.01GiB, used=179.33GiB
> System, single: total=4.00MiB, used=48.00KiB
> Metadata, single: total=4.09GiB, used=2.03GiB
> GlobalReserve, single: total=370.78MiB, used=0.00B
> doas (neko-san@ARCH) password:
> neko-san@ARCH ~>
>
> ```
> (The logs are too big for this email, so here's a cloud link:
> https://mega.nz/file/QrJRUQ5D#NCt5T6dpwS8VGWOrxPGdFK2M9nkURJ2ekH-YugFvVuc )

Re: [Help?] "errors" found in fs roots

[Roman Mamedov]

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

On Mon, 02 May 2022 16:51:09 +0000
Neko-san <nekoNexus@proton.me> wrote:

> Is no one willing to help with this?

  "here's a cloud link"

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.

Thanks

-- 
With respect,
Roman

[-- Attachment #2: btrfs-check.log.gz --]
[-- Type: application/gzip, Size: 214684 bytes --]

[-- Attachment #3: dmesg.log.gz --]
[-- Type: application/gzip, Size: 25372 bytes --]

Re: [Help?] "errors" found in fs roots

[Roman Mamedov]

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