Gooberpatrol66 has quit [Ping timeout: 260 seconds]
edr has quit [Quit: Leaving]
Gooberpatrol66 has joined #osdev
antranigv has quit [Ping timeout: 252 seconds]
antranigv has joined #osdev
koolazer has joined #osdev
[Kalisto] has quit [Quit: Ping timeout (120 seconds)]
[Kalisto] has joined #osdev
_whitelogger has joined #osdev
<MarchHare>
Any of you guys somewhat familiar with mdadm on linux? Google's answers aren't very satisfying for what I'm asking.
<Mutabah>
Somewhat, but it's not really on-topic here
<MarchHare>
I'
<MarchHare>
I'm aware. Fortunately, it's just an informational type of question and I don't see a lot of other traffic right now
<MarchHare>
You can /msg me if you'd prefer.
da5id has quit [Quit: WeeChat 4.7.0]
<Mutabah>
Eh, go for it here
Celelibi has quit [Ping timeout: 240 seconds]
<geist>
sure yeah
<MarchHare>
So I had some hardware go on the fritz. I had all four drives synced and in good shape, so the data was known to be good. However, one of the drives got out of sync before I realised what was actually happening, so it would've been wanting to resync. Anyway, I think I have the hardware issue resolved. I went to re-add the dropped drive and it's adding it as a spare. So right now it's saying raid device 3 is "removed" but that the one that I added is
<MarchHare>
the spare. I'm trying to figure out if I should let the drives sync and it'll just go back to being part of set B, or if I should just recreate the array and restore from backup.
<MarchHare>
Data itself still seems intact.
<geist>
how long is it gonna take to sync?
<MarchHare>
5500 min.
<MarchHare>
It's 4x 22TB disks.
<geist>
well, depends on if you wanna wait that long
<MarchHare>
Well, that's what I'm trying to decide.
<geist>
but i thought it was adding it as a spare?
<MarchHare>
If it's not going to promote it back to a full member of the array at the end of the resync, I'm just going to blow the disks away
<geist>
i suspect you have to tell it that you're reinserting it and to resync
<MarchHare>
I guess the question is "does it just call it a spare until it's a full member"
<geist>
dunno
<MarchHare>
Oh, it's already resyncing
<geist>
oh yay
<geist>
maybe it took a whiel to figure it out
Celelibi has joined #osdev
<MarchHare>
Like I said, I could always just blow it away and restore the 4.4TB from backup.
<MarchHare>
But them I really only do have one copy.
<MarchHare>
At least while the restore is happening
<geist>
yeah i'd just wait
<geist>
and funny right as you said this i have some sort of failure on my root disk of my workstation
<MarchHare>
That's what I was thinking, too. But I was hoping someone else might know what it was going to do with the spare status.
<MarchHare>
oof. Root failure is no fun. Disk or just filesystem damage?
<geist>
seems to be okay now but i need to roll back some recent overclocking i was futzing with it seems
<MarchHare>
My issue was related to a failing HDD cage backplane, and it turns out that also the SATA cable. I think it took out the SATA expansion card, too.
<geist>
before it trashes my disk
<geist>
got a large spew of BTRFS node corruption in dmesg and a RO locked down FS (good) right after messing around pushing the AMD 'curve optimizer' a bit in windows
<MarchHare>
Honestly, I sort of wonder if that do some damage to the PCI-E bus, too. I know when the new sata card boots, its option rom shows disk 1, 2, & 3, but no 0. But disk 0 seems to be visible to linux.
<geist>
soooo i'm sure not a coincidence
<MarchHare>
geist: Wow. I didn't know anyone used BTRFS.
* geist
rolls eyes
<MarchHare>
geist: I've seriously never used it. Wasn't sure why I would want to. Ext4 always worked pretty well for me. Beat Ext2 hands-down
<geist>
because of a pile of additional features it has that i find useful
<MarchHare>
You've got my attention...
<geist>
anyway, trying to fix things hang on
<geist>
actually the fact that it immediately caught an internal consistency and locked down the FS is a pretty good example
<MarchHare>
Okay, that's a fair argument
<geist>
anyway i use subvolumes and snapshtos and whatnot a lot
<geist>
as well as reflinks and other goodies
<geist>
works great for backing up things, etc
<geist>
reason i virtually rolled my eyes is it seems like 50% of the people i mention btrfs do respond similarly
<geist>
i think it got a bad rap early on and like 10 years later folks are saying it's super unstable, etc
<geist>
and AFAICT it's quite stable, and having lots of internal checksums and whatnot has helped me catch hardware failures much quickier
<MarchHare>
I believe it.
<MarchHare>
Maybe they haven't done a very good job selling it?
<MarchHare>
I'm sure a lot of people remember the thing with ReiserFS
<geist>
yah. lots of NASes and whatnot use it, synology comes to mind
<MarchHare>
I remember I was starting to experiment with ReiserFS in 07, and then all that shit went down, and I noped right the fuck back to ext4. I have 25 years of shit backed up on that raid and I don't wanna lose it.
<geist>
heh i remember it was a pretty solid fs for a while there. faaast
<geist>
back in that window where ext4 hadn't come out yet i think, so compared to ext3 it was pretty quick
<MarchHare>
I think ext4 was just becoming considered stable
<MarchHare>
Maybe I noped right the fuck back to ext3
<geist>
yah ext4 may have been around longer than i'd like to admit :)
<geist>
i do remember it being a fairly large speed increase compared to ext3
<geist>
at least on spinny disks since SSDs weren't really a thing then
<geist>
now i think in general your fs can be slow and no one cares because SSD
<MarchHare>
SSD are lightning fast. Wish they held a candle to the $/bit of spinning platter
agent314 has joined #osdev
TkTech1 has joined #osdev
TkTech has quit [Ping timeout: 252 seconds]
TkTech1 is now known as TkTech
<AmyMalik>
Stop holding candles to things.
<MarchHare>
You're right. I should hold a 2M candlepower spotlight to stuff!
<MarchHare>
lol
<AmyMalik>
I used to know someone who said that.
<MarchHare>
Okay, time for bed. The damn array is rebuilding. If the spare doesn't drop in like a normal device in a few days, I'll blow it away and restore from backup.
vai has joined #osdev
<vai>
morning from Finland
vai is now known as Jari--
<MarchHare>
Morning.
fgarcia has quit [Ping timeout: 248 seconds]
agent314 has quit [Ping timeout: 244 seconds]
fgarcia has joined #osdev
fgarcia has quit [Max SendQ exceeded]
agent314 has joined #osdev
MarchHare has quit [Quit: Leaving]
fgarcia has joined #osdev
fgarcia has quit [Max SendQ exceeded]
fgarcia has joined #osdev
Fingel has quit [Remote host closed the connection]
Fingel has joined #osdev
goliath has joined #osdev
agent314 has quit [Quit: WeeChat 4.5.2]
Jari-- has quit [Ping timeout: 248 seconds]
netbsduser has joined #osdev
Lucretia has joined #osdev
nitrix has quit [Ping timeout: 252 seconds]
nitrix has joined #osdev
netbsduser has quit [Ping timeout: 252 seconds]
msv has quit [Quit: Leaving]
msv has joined #osdev
xvmt has quit [Remote host closed the connection]
HumanG331 has joined #osdev
Teukka has quit [Read error: Connection reset by peer]
Teukka has joined #osdev
xvmt has joined #osdev
[Kalisto] has quit [Quit: Ping timeout (120 seconds)]