Skip to contentSkip to conversation

mount ... or other error?

DISCUSSION Ulli Horlacher 2 participants 3 messages Mar 12, 2024 – Mar 13, 2024 Btrfs file system

lore
Share & tools
lore
#0 lore raw

I have (on Ubuntu 22.04):

root@fextest:~# lsblk -o NAME,SIZE,FSTYPE,LABEL /dev/sdd
NAME    SIZE FSTYPE LABEL
sdd    13.5T
`-sdd1 13.5T btrfs  spool
root@fextest:~# blkid | grep sdd1
/dev/sdd1: LABEL="spool" UUID="4d8b313d-5710-406b-bdba-b01625bf45ef" UUID_SUB="a57d255f-24af-4562-9421-a1eb6e76c051" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="a409c49c-2b2d-654f-a0aa-9d0b5ea4307f"
root@fextest:~# file -s /dev/sdd1
/dev/sdd1: BTRFS Filesystem label "spool", sectorsize 4096, nodesize 16384, leafsize 16384, UUID=4d8b313d-5710-406b-bdba-b01625bf45ef, 223643512832/44530217717760 bytes used, 3 devices
root@fextest:~# mount -t btrfs /dev/sdd1 /mnt/tmp
mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error.

How can I debug this further?

Signature · 6 lines
Ullrich Horlacher              Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart         E-Mail: [email protected]
Allmandring 30a                Tel:    ++49-711-68565868
70569 Stuttgart (Germany)      WWW:    https://www.tik.uni-stuttgart.de/
REF:<[email protected]>
#1 lore raw
Quoted 12 lines · Ulli Horlacher

I have (on Ubuntu 22.04):

root@fextest:~# lsblk -o NAME,SIZE,FSTYPE,LABEL /dev/sdd
NAME    SIZE FSTYPE LABEL
sdd    13.5T
`-sdd1 13.5T btrfs  spool
root@fextest:~# blkid | grep sdd1
/dev/sdd1: LABEL="spool" UUID="4d8b313d-5710-406b-bdba-b01625bf45ef" UUID_SUB="a57d255f-24af-4562-9421-a1eb6e76c051" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="a409c49c-2b2d-654f-a0aa-9d0b5ea4307f"
Quoted 8 lines
root@fextest:~# file -s /dev/sdd1
/dev/sdd1: BTRFS Filesystem label "spool", sectorsize 4096, nodesize 16384, leafsize 16384, UUID=4d8b313d-5710-406b-bdba-b01625bf45ef, 223643512832/44530217717760 bytes used, 3 devices
root@fextest:~# mount -t btrfs /dev/sdd1 /mnt/tmp
mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error.

How can I debug this further?

dmesg output would be useful.

#2 lore raw
Quoted 1 line · Andrei Borzenkov

dmesg output would be useful.

root@fextest:~# dmesg | tail
[110309.184692] BTRFS: device label spool devid 1 transid 15334 /dev/sdd1 scanned by mount (5281)
[110309.190879] BTRFS info (device sdd1): using crc32c (crc32c-intel) checksum algorithm
[110309.190886] BTRFS info (device sdd1): disk space caching is enabled
[110309.190886] BTRFS info (device sdd1): has skinny extents
[110309.196830] BTRFS error (device sdd1): devid 3 uuid 24b0f302-ada1-41fe-8aec-0b353b592046 is missing
[110309.196834] BTRFS error (device sdd1): failed to read the system array: -2
[110309.196940] BTRFS error (device sdd1): open_ctree failed

Ahhh.. I have an idea:

root@fextest:~# lshd sdd
Device    Size Type      Label               Mountpoint
sdd     13824G SCSI:GPT  "NETAPP_LUN_C-Mode"
 sdd1   13824G btrfs     "spool"

This is probably an iSCSI device which was part of a RAID0 btrfs filesystem and has been retired some years ago.

My storage admin gave me on my request a "new LUN" which is indeed this old retired LUN. Some meta data like filesystem id and label are still there but I cannot mount it anymore, because the second part of the RAID0 is missing.

Could this be an explanation?

I do not need the data any longer, I just want to know what happend.

Addon question:

Why does the mount command not also display the error messages from dmesg? Or at least say something like "for more information, call dmesg"?

Signature · 6 lines
Ullrich Horlacher              Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart         E-Mail: [email protected]
Allmandring 30a                Tel:    ++49-711-68565868
70569 Stuttgart (Germany)      WWW:    https://www.tik.uni-stuttgart.de/
REF:<CAA91j0XZGSA1oNTDZXm_PRTjnaFcYbf5F+gXTSJ9kCivPuZ1gQ@mail.gmail.com>