Another data corruption, fortunately not fatal, with btrfs.
-
Another data corruption, fortunately not fatal, with btrfs. Two mirrored disks that have little activity. On the same server, Proxmox 9, there is also a ZFS pool (mirrored, more active). Same type of disks.
An employee mistakenly connected an electric heater to a socket protected by the UPS, and the server rebooted brutally.
Upon reboot, one of the two btrfs disks reported:
[ 167.015266] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.017007] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.052517] BTRFS error (device sdd): open_ctree failed mount: /btrfs: can't read superblock on /dev/sdd.Result: unable to mount, even in degraded mode. The only way was to disconnect sdd and mount the other disk in degraded mode.
No issues with the ZFS pool.
Needless to say, I'm now copying the data to ZFS, and before tomorrow, these two disks will be a new ZFS pool.
@stefano These incidents always point to a poorly designed electrical installation where servers are not isolated from other electrical devices to prevent interference, particularly issues caused by harmonics 🤷🏻
-
@stefano These incidents always point to a poorly designed electrical installation where servers are not isolated from other electrical devices to prevent interference, particularly issues caused by harmonics 🤷🏻
@ricardo it is. The server is not in a proper room, and isn't protected in the proper way
-
undefined oblomov@sociale.network shared this topic
-
@ricardo it is. The server is not in a proper room, and isn't protected in the proper way
@stefano Aye, the wise move is, before even checking the computers in an office, to take a look at the electrical panel and see whether there's a super immune RCD ... then you can brace yourself 🫣
-
Another data corruption, fortunately not fatal, with btrfs. Two mirrored disks that have little activity. On the same server, Proxmox 9, there is also a ZFS pool (mirrored, more active). Same type of disks.
An employee mistakenly connected an electric heater to a socket protected by the UPS, and the server rebooted brutally.
Upon reboot, one of the two btrfs disks reported:
[ 167.015266] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.017007] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.052517] BTRFS error (device sdd): open_ctree failed mount: /btrfs: can't read superblock on /dev/sdd.Result: unable to mount, even in degraded mode. The only way was to disconnect sdd and mount the other disk in degraded mode.
No issues with the ZFS pool.
Needless to say, I'm now copying the data to ZFS, and before tomorrow, these two disks will be a new ZFS pool.
@stefano what would explain that a low activity fs would get wrecked this way… sounds weird; unless btrfs keeps things in memory and never go sync.
-
@stefano what would explain that a low activity fs would get wrecked this way… sounds weird; unless btrfs keeps things in memory and never go sync.
@joel I don't know. The disk isn't broken and the other disk (they're in mirror mode) is fine.
This has already happened to me a couple of times. Unpredictable but, at this point, not unexpected. -
Another data corruption, fortunately not fatal, with btrfs. Two mirrored disks that have little activity. On the same server, Proxmox 9, there is also a ZFS pool (mirrored, more active). Same type of disks.
An employee mistakenly connected an electric heater to a socket protected by the UPS, and the server rebooted brutally.
Upon reboot, one of the two btrfs disks reported:
[ 167.015266] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.017007] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.052517] BTRFS error (device sdd): open_ctree failed mount: /btrfs: can't read superblock on /dev/sdd.Result: unable to mount, even in degraded mode. The only way was to disconnect sdd and mount the other disk in degraded mode.
No issues with the ZFS pool.
Needless to say, I'm now copying the data to ZFS, and before tomorrow, these two disks will be a new ZFS pool.
@stefano ZFS 2 BTRFS 0
-
Another data corruption, fortunately not fatal, with btrfs. Two mirrored disks that have little activity. On the same server, Proxmox 9, there is also a ZFS pool (mirrored, more active). Same type of disks.
An employee mistakenly connected an electric heater to a socket protected by the UPS, and the server rebooted brutally.
Upon reboot, one of the two btrfs disks reported:
[ 167.015266] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.017007] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.052517] BTRFS error (device sdd): open_ctree failed mount: /btrfs: can't read superblock on /dev/sdd.Result: unable to mount, even in degraded mode. The only way was to disconnect sdd and mount the other disk in degraded mode.
No issues with the ZFS pool.
Needless to say, I'm now copying the data to ZFS, and before tomorrow, these two disks will be a new ZFS pool.
Btrfs - the name says it all. "BetterFS" but misspelled by serverside Javascript hipsters. It needs to effin burn.
I'd take FAT32 over that monstrosity any day.
It is way, way worse than the tiramisu pizza abomination.
Sorry not sorry.
-
Another data corruption, fortunately not fatal, with btrfs. Two mirrored disks that have little activity. On the same server, Proxmox 9, there is also a ZFS pool (mirrored, more active). Same type of disks.
An employee mistakenly connected an electric heater to a socket protected by the UPS, and the server rebooted brutally.
Upon reboot, one of the two btrfs disks reported:
[ 167.015266] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.017007] BTRFS error (device sdd): parent transid verify failed on 873906176 wanted 998679 found 998677
[ 167.052517] BTRFS error (device sdd): open_ctree failed mount: /btrfs: can't read superblock on /dev/sdd.Result: unable to mount, even in degraded mode. The only way was to disconnect sdd and mount the other disk in degraded mode.
No issues with the ZFS pool.
Needless to say, I'm now copying the data to ZFS, and before tomorrow, these two disks will be a new ZFS pool.
@stefano I have never used btrfs. But I always read horror stories about it.
All I understand about btrfs is it's eternally in beta testing phase.
-
Btrfs - the name says it all. "BetterFS" but misspelled by serverside Javascript hipsters. It needs to effin burn.
I'd take FAT32 over that monstrosity any day.
It is way, way worse than the tiramisu pizza abomination.
Sorry not sorry.
@h3artbl33d @stefano Butter Fuss. I hope it becomes reliable someday, but I won't use it until it's been stable for some years. Same reason I won't use native ZFS encryption. People swear by both, and they keep losing data.
-
@h3artbl33d @stefano Butter Fuss. I hope it becomes reliable someday, but I won't use it until it's been stable for some years. Same reason I won't use native ZFS encryption. People swear by both, and they keep losing data.
@mason @h3artbl33d I've been waiting fot it to be stable for something like...15 years. I'm starting to believe it will never be totally stable.
-
Btrfs - the name says it all. "BetterFS" but misspelled by serverside Javascript hipsters. It needs to effin burn.
I'd take FAT32 over that monstrosity any day.
It is way, way worse than the tiramisu pizza abomination.
Sorry not sorry.
@h3artbl33d The tiramisu pizza is a perfect example 😆
I've used btrfs - but never for critical data. Maybe for backup servers, etc, thanks to its possibility to mix and match drives and still have redundancy.
But the price is that - more than once - it ate my data.