Another data corruption, fortunately not fatal, with btrfs.
Uncategorized
11
Posts
5
Posters
10
Views
-
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.
-
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.
Don't forget to connect the employee to the UPS, too.
-
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 honestly can't believe how these sorts of issues can keep cropping up with btrfs even today. A hard system shutdown or reboot is an undesirable but certainly by no means uncommon event. And btrfs certainly has all the elements that would *enable* it to handle them gracefully in as close to a guaranteed fashion as one can reasonably get. To say nothing of *one* disk in a redundant array having bad data requiring physical intervention to get to a working state... yikes!
-
Don't forget to connect the employee to the UPS, too.
@GustavinoBevilacqua the fun fact is that nobody is admitting it. But the heater is still connected, even if it is off.
-
@GustavinoBevilacqua the fun fact is that nobody is admitting it. But the heater is still connected, even if it is off.
The UPS was trying to commit suicide
-
@stefano I honestly can't believe how these sorts of issues can keep cropping up with btrfs even today. A hard system shutdown or reboot is an undesirable but certainly by no means uncommon event. And btrfs certainly has all the elements that would *enable* it to handle them gracefully in as close to a guaranteed fashion as one can reasonably get. To say nothing of *one* disk in a redundant array having bad data requiring physical intervention to get to a working state... yikes!
@mkj I agree. Btrfs has its good points but I don't rely on it.
-
The UPS was trying to commit suicide
@GustavinoBevilacqua I think they're ready to swear they saw the UPS trying to commit suicide 🤣
-
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.
-
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 🫣
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@dmoonfire my current SGT puzzles' obsession is Towers, FWIW.
-
@evan 40% of respondents are undernourished
-
@bigzaphod only one thing for it... THUMB WAR WITH THE IDEAS! 👍🏻
-
So, I see that brilliant @cubicgarden person was a guest on @firesidefedi ... I need to catch up!
-
Thanksgiving and Christmas should be six months apart. It's very difficult to have to deal with those people again that soon.
(Due to events in my personal life, this week's #HootinTootinTuesday will be on a Wednesday. My apologies for the delay.)
#Humor #Humour #FunnyMeme #Turkey #TurkeyDay #DadJokes #Thanksgiving #ThanksgivingDinner #Holidays #Dogs
#Dogstodon ##DogsOfMastodon #Dog #Dachshunds #WienerDogs #DogMemes
-
@symbolics I've see records of a purchase of a Xerox Interlisp D-machine by an Italian research institution in the late 1980s. The price tag, which included WAN connectivity and support, was eye watering.
-
Had some pretty extensive implementation ideas in my head for a Tapestry feature for months now. Was excited to finally get started on it.
Woke up feeling like all the ideas are sus and will be a disaster.
My brain isn't playing fair here.
-
@amoroso They were also not widely available. They were very very expensive and I doubt that more than 10k of these machines were ever sold. The hardware was expensive, but the software was also very expensive. The early competition were UNIX Lisp systems like Allegro CL, Lucid CL and then LispWorks. But they and the hardware for them was also expensive (memory). Government money feeded the bubble. Later, after the AI crash a lot of the remaining applications were ported to C++.
