As some might've guessed… that `fsck` is still grinding away.
24+ hours. I thought large EXT2 volumes took a long time to check, but it seems BTRFS can be just as bad.
```
ref mismatch on [77402689536 8192] extent item 1, found 0
data extent[77402689536, 8192] bytenr mimsmatch, extent item bytenr 77402689536 file item bytenr 0
data extent[77402689536, 8192] referencer count mismatch (root 256 owner 227855 offset 33595392) wanted 1 have 0
backpointer mismatch on [77402689536 8192]
owner ref check failed [77402689536 8192]
repair deleting extent record: key [77402689536,168,8192]
Repaired extent references for 77402689536
```
Not sure what number that's expected to climb to. Maybe with some luck I might be "back home" this afternoon, but at this rate, who knows?
Stuart Longland (VK4MSL)
npub12h…vts7y
2026-04-11 21:17:08 UTC
in reply to nevent1q…vgxl
Author Public Key
npub12h9s2ds73gxsjmewpdf0z66q0elhx4xk6tww4w98d32p7u9kp60qyvts7ySeen on
wss://relay.momostr.pinkPublished at
2026-04-11 21:17:08 UTCEvent JSON
{
"id": "58d259a5e513d9004a57683508c58e1a75d9598e57358024b7d7e6eaf23f0902",
"pubkey": "55cb05361e8a0d096f2e0b52f16b407e7f7354d6d2dceab8a76c541f70b60e9e",
"created_at": 1775942228,
"kind": 1,
"tags": [
[
"e",
"763e0ca1fbe60cfeaf7dc0224eefd25013583d0fcafdbcbeba3c569e27d24b0a",
"",
"root",
"55cb05361e8a0d096f2e0b52f16b407e7f7354d6d2dceab8a76c541f70b60e9e"
],
[
"proxy",
"https://aus.social/@vk4msl/116388149901643939",
"web"
],
[
"p",
"55cb05361e8a0d096f2e0b52f16b407e7f7354d6d2dceab8a76c541f70b60e9e"
],
[
"e",
"7ce7ab25048871e057743dbcd5221565c0d7a298f3deb5682db42ca1a92eeabd",
"",
"reply",
"55cb05361e8a0d096f2e0b52f16b407e7f7354d6d2dceab8a76c541f70b60e9e"
],
[
"proxy",
"https://aus.social/users/vk4msl/statuses/116388149901643939",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://aus.social/users/vk4msl/statuses/116388149901643939",
"pink.momostr"
],
[
"-"
]
],
"content": "As some might've guessed… that `fsck` is still grinding away.\n\n24+ hours. I thought large EXT2 volumes took a long time to check, but it seems BTRFS can be just as bad.\n\n```\nref mismatch on [77402689536 8192] extent item 1, found 0\ndata extent[77402689536, 8192] bytenr mimsmatch, extent item bytenr 77402689536 file item bytenr 0\ndata extent[77402689536, 8192] referencer count mismatch (root 256 owner 227855 offset 33595392) wanted 1 have 0\nbackpointer mismatch on [77402689536 8192]\nowner ref check failed [77402689536 8192]\nrepair deleting extent record: key [77402689536,168,8192]\nRepaired extent references for 77402689536\n\n```\n\nNot sure what number that's expected to climb to. Maybe with some luck I might be \"back home\" this afternoon, but at this rate, who knows?",
"sig": "380648465de8a6f1acf1a10848ca4316f98561d65647cc09ed58c5e7fc498f05c4ef14eb1c9b9066fe92b1bdcdd523c6c6c08994e4d7646a7a0ffee13b9e6a76"
}