Hi Chris,

After booting the fedora usb stick (running rc2), I got the same results.

On Mon, 1 Apr 2019 at 08:35, Chris Murphy <li...@colorremedies.com> wrote:
>
> On Sat, Mar 30, 2019 at 5:43 PM Glenn Trigg <ggtr...@gmail.com> wrote:
...
>
> I'm confused because "can't read superblock" isn't found in fs/btrfs.
> I'm only finding it in fs/gfs2/ops_fstype.c
>
> From what you provided, /dev/sda1 definitely has a valid btrfs
> superblock. I wonder if there's some other stale something or other on
> this partition?
>
> What do you get for
>
> $ sudo blkid

/dev/sda1: LABEL="data" UUID="d5e50511-3e31-4de6-ba37-c5841895be9f"
UUID_SUB="a28b0f34-f14d-492b-995b-2dd8a78ec9bb" TYPE="btrfs"
PARTUUID="efa240ec-01"
/dev/sdc1: LABEL="data" UUID="d5e50511-3e31-4de6-ba37-c5841895be9f"
UUID_SUB="d9c56d7a-21a1-4197-a701-5493392e1ae1" TYPE="btrfs"
PARTUUID="1aae1443-c03e-4509-ad06-124a64c4df4f"

> $ sudo wipefs -an /dev/sda1 /dev/sdc1

/dev/sda1: 8 bytes were erased at offset 0x00010040 (btrfs): 5f 42 48
52 66 53 5f 4d
/dev/sdc1: 8 bytes were erased at offset 0x00010040 (btrfs): 5f 42 48
52 66 53 5f 4d

> $ sudo mount -v -o ro,nologreplay,usebackuproot

mount: /data: can't read superblock on /dev/sda1.

and in dmesg...

[ 1045.029981] BTRFS info (device sda1): use lzo compression, level 0
[ 1045.029987] BTRFS info (device sda1): disabling log replay at mount time
[ 1045.029991] BTRFS info (device sda1): trying to use backup root at mount time
[ 1045.029992] BTRFS info (device sda1): disk space caching is enabled
[ 1045.029994] BTRFS info (device sda1): has skinny extents
[ 1045.127375] BTRFS info (device sda1): bdev /dev/sda1 errs: wr 0, rd
0, flush 0, corrupt 1, gen 0
[ 1045.127381] BTRFS info (device sda1): bdev /dev/sdc1 errs: wr 0, rd
0, flush 0, corrupt 4, gen 0
[ 1045.154198] BTRFS error (device sda1): parent transid verify failed
on 628168376320 wanted 37601 found 37712
[ 1045.178310] BTRFS error (device sda1): parent transid verify failed
on 628168376320 wanted 37601 found 37712

I.e. the same as before. It's puzzling!

Regards,
Glenn

>
> --
> Chris Murphy

Reply via email to