slight zfs problem after playing with WDIDLE3 and WDTLER

[Tommi Lätti]

2010/1/26 Steven Schlansker <stevenschlansker at gmail.com>:
>
> On Jan 25, 2010, at 10:43 AM, Tommi Lätti wrote:
>> After checking the logs carefully, it seems that the ada1 device
>> permanently lost some sectors. Before twiddling with the parameters,
>> it was 1953525168 sectors (953869MB), now it reports 1953523055
>> (953868MB). So, would removing it and maybe export/import get me back
>> to degraded state and then I could just replace the now
>> suddenly-lost-some-sectors drive?
>
> That will probably work.  I had a similar problem a bit
> ago where suddenly my drives were too small, causing the UNAVAIL
> corrupted-data problem.  I managed to fix it by using gconcat to stitch
> an extra MB of space from the boot drive onto it.  Not a very good solution,
> but the best I found until FreeBSD gets shrink support (which sadly seems
> like it may be a long while)
>
> Failing that, you could use OpenSolaris to import it (as it does have minimal
> support for opening mismatched sized vdevs), copy the data off, destroy, and restore.

Forgot to reply-all...

--clip--
I just tried just to boot up the system without the 'reduced' drive to
see if would automatically go to reduced state. What I got after
booting up was that one of the labels had vanished and now it had
mixed up the drives it seems. GRR.

I guess that's an easy one to recover from, although now I suspect
that the zfs is writing to the disks while it scans for the pools and
making my life harder at the same time.

Maybe I'll just go to the opensol way and try it from there. Copying
data locally is quite fast.
--clip--

After thinking overnight I'm a bit curious why the whole filesystem
failed on that single vdev causing the whole pool loss. Shouldn't the
zfs just disregard the disk and just go to degraded state? I've had
normal catastrophic disk failures on this setup before and normal
replace drive+resilver has worked just fine.

Maybe a bug?

-- 
br,
Tommi