Slow Archive Progress
06:26am UTC - 8/09/2010
Hey all, quick update. Sorry about the glacial pace of the restoration; I'm trying not to fuck it up when I move it, and I've been having trouble properly getting these threads to compress (and then extract with full paths to the right location, which is, you know, kinda important
, what the fuck 7z why is that the common command).
I've also been fucking with server things in general, such as the brand new Minecraft server; let's just say that Notch really needs to hop in a time machine and write the game in anything other than fucking Java
. Goddamned memory leaks cause Java to die, and all content in memory is lost, which seems to be all changes since the last restart
. ffs. It now reboots every 4 hours starting at midnight UTC so that should fix it.
Anyway, as we speak, the first batch of threads are decompressing on the server (in the right directories, with the right file permissions); I've been just going by thread number and moving newest-oldest. I'm restoring back through thread 10011240, which is around May 24, 2010. (Edit:
It worked! Huzzah!)
Once this proves to have worked just fine and I can stop worrying, I'll do another batch tonight, and so on. I've got a few days of vacation coming up this weekend, so I'm going to focus and get this shit done. I apologize for all the delays, but it's not like the content's going anywhere. Besides, the extra delay has given people way, way more than enough time to salvage whatever fapfics they'd like to save before I decommission the old server; I'll make a formal announcement this weekend when it's going dark (and even then I'll probably still leave it up for a while. I'm nice like that).Update:
Been pluggin' along. Somewhere in the 7zillions now. Uploading ~2GB a night or so, should be done within the coming week.Update 2:
I've lost a couple days due to Comcast asshattery, since I couldn't upload a 2.xGB file during constant spikes/drops and huge lag. See, before, when the internet would drop or slow to a crawl, I'd assume it was due to load on sup/tg/; now I'm finding it's just as likely Comcast's fault.
Also I decided I'm probably never taking down the old server. The bandwidth consumption dropped to nearly nothing (I figured it'd still get a bit hammered now and then) and I'm way, way under my bandwidth cap, so the graveyard on the old server will remain online indefinitely.
(The new graveyard, e.g. from July 2010 on, will be deleted regularly.)