[00:00] heh.... i had 4 drive raid10, unfortunetly 2 dropped off at the same time [00:00] so i'm going to setup a 4 drive raid 1 and restore from backup.... [00:00] mdadm just won't let me get rid of the old array... [00:01] and it's keeping the disc's busy so i can't create a new array [00:01] grrr [00:04] how the hell does 2 fail at once? [00:04] a great question... [00:05] one of them dissappeared and reappeared last month, now two just did it [00:05] not sure if they're just dying or what.... the connectors seem fine... so i'm just going to run it in raid1 to try and figure out what's going on... [00:06] thank god for nightly backups [00:06] once, out of the blue, 1 of my 3 failed. checked the other 2 drives, all fine. checked the drive on another computer, fine. what the hell is the chance the cable was failing? [00:07] it's a sas splitter cable, so.... i duno.... [00:07] mine were sata at that point [00:08] have u ever used xmonad? [00:09] no? [00:09] it's a tiling window manager. i just got it today, love it. [00:10] lol [00:10] people think i'm crazy when i need a tiling wm on a setup with 4 monitors [00:12] anyone good with mdadm & software raid???? [00:12] this thing just won't let me work on the md2 [00:14] omg...... apparantly third time is a charm.... lol [00:37] SpamapS: yeah, cool... wasn't sure of the best way to submit/surface the ganglia fix [00:39] I needed one working so I just put it in a ppa [02:02] adam_g: pong [02:09] is there a way to configure ubuntu server to go to sleep after a set period? [02:19] sleepd [02:19] Or if you just mean at specific times, atd or cron [02:20] hmm, i don't know much about atd or cron [02:20] buess i'll have to learn. [02:21] sleepd is more likely what you want [02:21] ok. [02:21] is there some instructions on configuring it? [02:22] RTFM [02:22] well, i didn't see a man page for it. [02:23] Try /usr/share/doc/sleepd then [02:23] My sleepd has a manpage, maybe your system is busted [02:24] i'll look at it. === kentb is now known as kentb-out [02:39] zul: hey, was just wondering what the flow is for packaging changes in the nova packages. do we merge to lp:~ubuntu-server-dev branches, and then push to the openstack ubuntu packagers, or the other way? im talking about general packaging fixes, not patches to the tree [02:55] twb: if I try to access a samba share, will that wake up my server? [02:56] No [02:56] You only asked about putting it to sleep, not waking it up [02:56] hmm [02:56] well, they would seem to go hand in hand [02:57] Waking it up by talking samba to it requires you to be running OS X on specialist Apple hardware; I'm not aware of anything else that can do anything layer-7 like that [02:57] You can do WOL but that will require your client to send a WOL packet [02:57] yeah, that wouldn't be bad, but my board doesn't suppor tWOL [02:57] And WOL also requires hardware support- right [02:58] If your goal is to reduce power consumption, but still have it respond to samba without having to walk over and push its power button or keyboard to wake it up, you're probably only going to be able to spin down disks and throttle the CPU, not put it into suspend-to-RAM or suspend-to-disk state [02:59] thats basically my goal [02:59] where could i learn to do that?.. what do i man or google? [03:00] it doesn't necessarily have to respond to samba, i mean, anyway i could wake it up, w/o physically being at the machine, would be fine [03:01] WOL is the only way I know [03:01] Or a monkey, of course [03:01] lol [03:01] Call the office, say "hey monkey, go push