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/ _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
