dullbananas (Joseph Silva)@lemmy.ca to Linux@lemmy.mlEnglish · edit-22 months agoCan corruption happen by powering off the computer (not properly shutting it down) during balance or scrub of a btrfs volume?message-squaremessage-square33fedilinkarrow-up10arrow-down10file-text
arrow-up10arrow-down1message-squareCan corruption happen by powering off the computer (not properly shutting it down) during balance or scrub of a btrfs volume?dullbananas (Joseph Silva)@lemmy.ca to Linux@lemmy.mlEnglish · edit-22 months agomessage-square33fedilinkfile-text
minus-squareAtemu@lemmy.mllinkfedilinkarrow-up0·2 months agoAs long as the hardware functions as it should (e.g. respects barriers) and there is no software bug in the stack, no. That’s a highly unlikely scenario though. Make backups.
minus-squareReakDuck@lemmy.mllinkfedilinkarrow-up0·2 months agoI had some kernel panics here and there… but the last one panic was fatal. Suddenly a lot of /usr/lib/lib<name>.so files were empty and also X11 stopped working…
minus-squareblackstrat@lemmy.fwgx.uklinkfedilinkarrow-up0·2 months agoAs long as there are no problems with the btrfs code? Hahahahaha!! There are.
minus-squareAtemu@lemmy.mllinkfedilinkarrow-up0·2 months agoAnd also in any other filesystem’s code or the block layers below the filesystem. As I said, unlikely scenario.
As long as the hardware functions as it should (e.g. respects barriers) and there is no software bug in the stack, no.
That’s a highly unlikely scenario though. Make backups.
I had some kernel panics here and there… but the last one panic was fatal. Suddenly a lot of /usr/lib/lib<name>.so files were empty and also X11 stopped working…
As long as there are no problems with the btrfs code? Hahahahaha!! There are.
And also in any other filesystem’s code or the block layers below the filesystem. As I said, unlikely scenario.