Date: Fri, 15 Jan 2010 21:49:09 +0100 From: Oliver Lehmann <lehmann@ans-netz.de> To: Alexander Motin <mav@FreeBSD.org> Cc: stable@freebsd.org, pjd@FreeBSD.org Subject: Re: 8-STABLE: gmirror segfaulting Message-ID: <20100115214909.42d3ca21.lehmann@ans-netz.de> In-Reply-To: <4B50BFA2.10204@FreeBSD.org> References: <20100115163350.094a2e4c.lehmann@ans-netz.de> <4B50BFA2.10204@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Motin wrote: > Interesting story, but I've lost the track. I can't say for sure what > crashed gmirror without seeing any messages, but I suppose that after so > dirty deconstruction of mirror and journals Hm.. dirty? I used the standard tools ;) > you may left some > meta-information on devices. Restoring gmirror could make it accessible > again. I would try to explicitly clear last few sectors of every > disk/partition where something was living with dd to be sure that > nothing left there. Right now I've cleaned the whole ada1 disk, recreated the filesystems and dump+restoreing the filesystems from ada0 to ada1. Then I'll switch ada1 andada0 and continue cleaning up the remaining disk. Then I'll gmirror them again. I could try to reproduce the error with my testsystem (have around 10 2GB SCSI disks waiting for such a task) and log every command I typed. But - is someone interested in fixing this? I already opened a PR for glabel not working on top of gjournaled devices but it is open w/o any comment for 2 month. Before I try to find a way of reproducing it I would know that someone would work with the PR I'll create then. I don't like feeding black holes ;) -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100115214909.42d3ca21.lehmann>