No, but that's a great idea! I'm on a UFS root at the moment, will have a look
at using ZFS next time I re-install.
> Date: Tue, 5 Aug 2008 07:59:35 -0700> From: [EMAIL PROTECTED]> Subject: Re:
> [zfs-discuss] Zpool import not working - I broke my pool...> To: [EMAIL
> PROTECTED]> CC: [EMAIL PROTECTED]; zfs-discuss@opensolaris.org> > Ross Smith
> wrote:> > Just a thought, before I go and wipe this zpool, is there any way
> to > > manually recreate the /etc/zfs/zpool.cache file?> > Do you have a copy
> in a snapshot? ZFS for root is awesome!> -- richard> > > > > Ross> >> > >
> Date: Mon, 4 Aug 2008 10:42:43 -0600> > > From: [EMAIL PROTECTED]> > >
> Subject: Re: [zfs-discuss] Zpool import not working - I broke my pool...> > >
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]> > > CC:
> zfs-discuss@opensolaris.org> > >> > >> > >> > > Richard Elling wrote:> > > >
> Ross wrote:> > > >> I'm trying to import a pool I just exported but I can't,
> even -f > > doesn't help. Every time I try I'm getting an error:> > > >>
> "cannot import 'rc-pool': one or more devices is currently > > unavailable">
> > > >>> > > >> Now I suspect the reason it's not happy is that the pool used
> to > > have a ZIL :)> > > >>> > > >> > > > Correct. What you want is CR
> 6707530, log device failure needs > > some work> > > >
> http://bugs.opensolaris.org/view_bug.do?bug_id=6707530> > > > which Neil has
> been working on, scheduled for b96.> > >> > > Actually no. That CR mentioned
> the problem and talks about splitting out> > > the bug, as it's really a
> separate problem. I've just done that and > > here's> > > the new CR which
> probably won't be visible immediately to you:> > >> > > 6733267 Allow a pool
> to be imported with a missing slog> > >> > > Here's the Description:> > >> >
> > -------------------> > > This CR is being broken out from 6707530 "log
> device failure needs > > some work"> > >> > > When Separate Intent logs
> (slogs) were designed they were given > > equal status in the pool device
> tree.> > > This was because they can contain committed changes to the pool.>
> > > So if one is missing it is assumed to be important to the integrity > >
> of the> > > application(s) that wanted the data committed synchronously, and
> thus> > > a pool cannot be imported with a missing slog.> > > However, we do
> allow a pool to be missing a slog on boot up if> > > it's in the
> /etc/zfs/zpool.cache file. So this sends a mixed message.> > >> > > We should
> allow a pool to be imported without a slog if -f is used> > > and to not
> import without "-f" but perhaps with a better error message.> > >> > > It's
> the guidsum check that actually rejects imports with missing > > devices.> >
> > We could have a separate guidsum for the main pool devices (non > >
> slog/cache).> > > -----------------------> > >> >> >> >
> ------------------------------------------------------------------------> >
> Get Hotmail on your mobile from Vodafone Try it Now! > >
> <http://clk.atdmt.com/UKM/go/107571435/direct/01/>>
_________________________________________________________________
Get Hotmail on your mobile from Vodafone
http://clk.atdmt.com/UKM/go/107571435/direct/01/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
