Closed Doc-Pixel closed 1 year ago
I can mount readonly
mount -t bcachefs /dev/nvme0n1:/dev/nvme1n1:/dev/sdb /data -o ro,nochanges,norecovery
and see the data.
Are you on IRC?
Since you can mount readonly, the dump tool should work - can you send me your filesystem metadata?
I'm in the IRC now, will pass a link to the files.
Closing since we were unable to repro, reopen if needed
Similar issues are #251 #265 #344
I'm running bcacheFS with two NVMEs and one HDD. After a reboot my bcachefs volume is empty when mounted, bcachefs fs usage shows there is still terabytes of data on the volume. fsck throws
invalid bkey format: field too large
My volume is set up as below
Context: I'm running several blockchains on the system (i9, 128GB, 2x 1TB nvme, 16TB HDD). One of the chains (erigon) uses MDBX as a database, which is a COW type of database that uses one file to store the database. My database was about 6.3TB and actively written to. Performance was really slow, erigon team advised not to use MDBX on top of bcacheFS. I deleted the erigon data after. My system became slow and unresponsive, I decided to reset.
After a hard reset I mounted my bcachefs volume and it was empty.
mount -t bcachefs /dev/nvme0n1:/dev/nvme1n1:/dev/sdb /data
I unmounted and performed fsckIt threw
error validating btree node on 0x5639cfac65e0g at btree extents level 0/2 u64s 11 type btree_ptr_v2 1744968794:174456:U32_MAX len 0 ver 0: seq 7b59fb704c6fa19a written 328 min_key 1744968793:2975960945:0 durability: 1 ptr: 0:1266968:512 gen 14 node offset 0 bset u64s 8771: invalid bkey format: field too large
Version
Make sure you're using a reasonably new version.
Generic info Provide the output of:
bcachefs fs usage
bcachefs show-super
Dmesg