[Bug 1931790] Re: Unable to mount btrfs RAID 1 filesystem after reboot - Error - device total_bytes should be at most X but found Y
Andreas Mewes
1931790 at bugs.launchpad.net
Fri Dec 17 13:30:52 UTC 2021
Hi, I have the same problem, raid1 partition does not mount after upgrade from 5.8 to 5.11 kernel.
(Ubuntu 20.04LTS > 21.04)
Mount is ok with Kernel up to 5.10. (SystemRescue-USB)
BTRFS error (device sdb): device total_bytes should be at most 4000780910592 but found 4000785960960
Why the difference of 5050368 bytes (9864 sectors) ?
Łukasz had a difference of 568942592 bytes (1111216 sectors)
sdb is the only Harddrive with both. 512 bytes Sector size
(logical/physical)!
sda: root/boot SDD
sdb,sdc,sdd,sde: RAID1 btrfspool
sdf: clean 16TB btrfs HDD
Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 10239 8192 4M BIOS boot
/dev/sda2 10240 1034239 1024000 500M EFI System
/dev/sda3 1034240 488397134 487362895 232.4G Linux filesystem
Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HUS726T4TAL
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sdb1 10240 7814035455 7814025216 3.6T Linux filesystem
/dev/sdb2 2048 10239 8192 4M BIOS boot
Disk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: WDC WD8003FRYZ-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sdc1 10240 15628053134 15628042895 7.3T Linux filesystem
/dev/sdc2 2048 10239 8192 4M BIOS boot
Disk /dev/sdd: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD40EFRX-68N
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sdd1 10240 7814035455 7814025216 3.6T Linux filesystem
/dev/sdd2 2048 10239 8192 4M BIOS boot
Disk /dev/sde: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD4003FFBX-6
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sde1 10240 7814035455 7814025216 3.6T Linux filesystem
/dev/sde2 2048 10239 8192 4M BIOS boot
Disk /dev/sdf: 14.55 TiB, 16000900661248 bytes, 31251759104 sectors
Disk model: TOSHIBA MG08ACA1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sdf1 2048 31251759070 31251757023 14.6T Linux filesystem
Comparision (extract) between sdb1 and sdd1, sde1:
[root at sysrescue ~]# btrfs inspect-internal dump-super /dev/sdb1 /dev/sdd1 /dev/sde1
superblock: bytenr=65536, device=/dev/sdb1
---------------------------------------------------------
label btrfspool
generation 1003437
total_bytes 20003910791168
bytes_used 8994780921856
sectorsize 4096
dev_item.total_bytes 4000780910592
dev_item.bytes_used 3532610600960
dev_item.io_align 4096
dev_item.io_width 4096
dev_item.sector_size 4096
superblock: bytenr=65536, device=/dev/sdd1
---------------------------------------------------------
label btrfspool
generation 1003437
total_bytes 20003910791168
bytes_used 8994780921856
sectorsize 4096
dev_item.total_bytes 4000785960960
dev_item.bytes_used 3532610600960
dev_item.io_align 4096
dev_item.io_width 4096
dev_item.sector_size 4096
superblock: bytenr=65536, device=/dev/sde1
---------------------------------------------------------
label btrfspool
generation 1003437
total_bytes 20003910791168
bytes_used 8994780921856
sectorsize 4096
dev_item.total_bytes 4000785960960
dev_item.bytes_used 3532644155392
dev_item.io_align 4096
dev_item.io_width 4096
dev_item.sector_size 4096
To make it short, I sent a Snapshot to the new big drive (sdf1), made it writeable and used it as new mountpoint in my /etc/fstab
mount /dev/sdb1 /source
btrfs sub snapshot -r /source /@snap
btrfs send /source/@snap | btrfs receive /target
btrfs property set -ts /target/@snap ro false
mv /target/@snap /target/@
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to btrfs-progs in Ubuntu.
https://bugs.launchpad.net/bugs/1931790
Title:
Unable to mount btrfs RAID 1 filesystem after reboot - Error - device
total_bytes should be at most X but found Y
Status in Ubuntu:
Confirmed
Status in btrfs package in Ubuntu:
Confirmed
Status in btrfs-progs package in Ubuntu:
Confirmed
Bug description:
Hi,
I'm unable to mount my newly created btrfs RAID 1 filesystem after
reboot..I performed the below steps with my 2 X 1 TB drives:
* created a new btrfs filesystem
mkfs.btrfs /dev/sdd1
* mounted it to /mnt/datanew
mount -t btrfs /dev/sdd1 /mnt/datanew
* copied over data from my previous NTFS volume on /dev/sde1 (which I
intended to add later as a mirror) - took 3.5 hrs
* added a new volume
mkfs.btrfs device add /dev/sde1
* started balance and convert to raid 1 - took 8 to 10
hours..overnight
btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/datanew
* rebooted next morning
I seeing below errors:
[ 792.045980] BTRFS info (device sdd1): allowing degraded mounts
[ 792.045988] BTRFS info (device sdd1): disk space caching is enabled
[ 792.045990] BTRFS info (device sdd1): has skinny extents
[ 792.047498] BTRFS error (device sdd1): device total_bytes should be at most 1000201841152 but found 1000203804672
[ 792.049207] BTRFS error (device sdd1): failed to read chunk tree: -22
[ 792.051525] BTRFS error (device sdd1): open_ctree failed
* Manual mount has below error additonally
mount: /mnt/datanew: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error.
* Verified the data seems intact (apparently no errors), superblock
seems fine.. tried btrfs rescue commands.. no issues found to fix
* Found several hits on search but not many solutions..except "btrfs filesystem resize max /" which doesnt work as I'm unable to mount in the first place..
btrfs filesystem resize max /mnt/datanew/
ERROR: not a btrfs filesystem: /mnt/datanew/
Any suggestions? Thanks
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubuntu-release-upgrader-core 1:21.04.13
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
Date: Sun Jun 13 11:17:02 2021
InstallationDate: Installed on 2021-05-16 (27 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_IN:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1931790/+subscriptions
More information about the foundations-bugs
mailing list