![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
i think we're back online
Dec. 22nd, 2005 01:17 pmIf you receive any bounced e-mail from me or Kim, please try again. More later, after lunch with ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif){kind=small}
matrushkaka and Mom of matrushkaka.
Dec. 22nd, 2005
i think we're back online
Dec. 22nd, 2005 01:17 pmIf you receive any bounced e-mail from me or Kim, please try again. More later, after lunch with matrushkaka and Mom of matrushkaka.
root cause analysis
Dec. 22nd, 2005 11:55 pmAfter removing the suspect drive and suffering more crashes, all while i was trying to transfer files to and from drives, i determined that the culprit was the goddamned primary 80-wire UDMA cable.
I ended up moving some files instead of copying them from drive to drive, so in returning to my original drive, i was missing some stuff, most importantly some log files; syslogd (the program that writes system logs) is still stupid in that if it tries to log to a file and realizes that it's not there, it will fail with a whine instead of creating the file. This is indisputably broken behavior and i don't know why we put up with it this way.
The worst of all this was that i blew away my mail server configuration. Not a big deal, though, just a moment of panic. There's also some brokenness in my news spool, but i think that'll sort itself out after tonight's expiration run.
root cause analysis
Dec. 22nd, 2005 11:55 pmAfter removing the suspect drive and suffering more crashes, all while i was trying to transfer files to and from drives, i determined that the culprit was the goddamned primary 80-wire UDMA cable.
I ended up moving some files instead of copying them from drive to drive, so in returning to my original drive, i was missing some stuff, most importantly some log files; syslogd (the program that writes system logs) is still stupid in that if it tries to log to a file and realizes that it's not there, it will fail with a whine instead of creating the file. This is indisputably broken behavior and i don't know why we put up with it this way.
The worst of all this was that i blew away my mail server configuration. Not a big deal, though, just a moment of panic. There's also some brokenness in my news spool, but i think that'll sort itself out after tonight's expiration run.