Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Oct 2010 23:58:29 +0200
From:      Willem Jan Withagen <wjw@digiware.nl>
To:        Freddie Cash <fjwcash@gmail.com>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: ZFS 'read-only' device / pool scan / import?
Message-ID:  <4CBE1485.2070400@digiware.nl>
In-Reply-To: <AANLkTi=DikO4-N8BG4U0WBX-7ypbPkVCR8=vHSaeN3qV@mail.gmail.com>
References:  <AE519076FDEA1259C5DEA689@HexaDeca64.dmpriest.net.uk>	<20101019151602.GA61733@icarus.home.lan>	<7BEF90D9F4D4CB985F3573C3@HexaDeca64.dmpriest.net.uk>	<4CBDFFF6.5080701@digiware.nl> <AANLkTi=DikO4-N8BG4U0WBX-7ypbPkVCR8=vHSaeN3qV@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-10-19 23:03, Freddie Cash wrote:

> While using labelled devices (be it glabel, gpt label, or whatever)
> certainly helps keep things ordered and working.
>
> However, ZFS also labels the devices in the pool.  A simple "zpool
> export poolname" followed by a "zpool import poolname" will scan the
> metadata on the drives, find all the devices in the pool, re-order
> things internally, and carry on.
>
> Back when I started with ZFS, I used unlabelled drives (also on 3Ware
> controllers) and made the mistake once of booting with a failed drive
> removed.  Pool came up faulted saying all the drives after the missing
> one were also faulted.  Thought I lost the whole pool.  However, some
> digging online showed the export/import info, and I was able to
> continue on without losing any data.

At the moment I have two 10Tb systems available so I'm experimenting  a 
lot to get a feeling on how easy recovering is.

So your comments are well appreciated.

And your suggestion is that although things looked really messed up, 
just export/import fixed the lot....

The GPT trick is sort of selfdocumenting, because it is otherwise real 
easy to get lost with 10 disks and 4 flash-devices. :(
And just because I yanked a single log disk (the wrong one) I ended up 
with a corrupt zraid.

So the least lesson for me here (again) has been that disk handling 
requires the utmost care. Trouble is just around the corner.

--WjW




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CBE1485.2070400>