Izak Burger added the comment: It turns out the issue is a bit more complex than that. /dev/sda has been removed from the array. Normally just re-adding it causes the bad block to be swapped out, but /dev/sdb has sectors itself that might be suspect, so it cannot rebuild. It appears all these are in the area where the logical volumes live, so the plan is to copy everything to a new logical volume, thereby effectively writing fresh copies to a new area of the disk. I will then overwrite the old area with zeroes, effectively forcing the hardware to swap the sector, hopefully allowing us to reover the raid array. At the very least, we'll have a copy of everything if it doesn't work.
On Sat, Jan 19, 2013 at 8:57 AM, Izak Burger <metatrac...@psf.upfronthosting.co.za> wrote: > > New submission from Izak Burger: > > Hi all, > > I got an notification during the night that something is amiss on the > psf virtual server hosting bugs.python.org. I've checked the > filesystem, repaired it, and restarted the virtual server. The ground > reason appears to be that we lost a disk in the RAID1. This means > we'll need to replace it on Monday. I'll let you know as soon as that > has been scheduled. > > regards, > Izak > > ---------- > messages: 2688 > nosy: izak > status: unread > title: Server error > > _______________________________________________________ > PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> > <http://psf.upfronthosting.co.za/roundup/meta/issue504> > _______________________________________________________ ---------- status: unread -> chatting _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue504> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org http://mail.python.org/mailman/listinfo/tracker-discuss
