Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 May 2009 00:04:03 +0400 (MSD)
From:      Dmitry Morozovsky <marck@rinet.ru>
To:        Dimitry Andric <dimitry@andric.com>
Cc:        freebsd-stable@freebsd.org, Pete French <petefrench@ticketswitch.com>
Subject:   Re: RFT: ZFS MFC
Message-ID:  <alpine.BSF.2.00.0905192358080.44708@woozle.rinet.ru>
In-Reply-To: <4A130E66.9070903@andric.com>
References:  <E1M6TK0-0007v2-F8@dilbert.ticketswitch.com> <4A130E66.9070903@andric.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 May 2009, Dimitry Andric wrote:

DA> >> http://www.andric.com/freebsd/zfs13/r192269/zfs_mfc-r192269.diff.bz2
DA> > 
DA> > Thanks - am going to gve this a try later. Preseumably if I leave the
DA> > pool at the revision it is currently on then I can revert back easily ?
DA> 
DA> I'll just repeat what Kip told us, "The standard disclaimers apply.
DA> This has only been lightly tested in a VM. Please do not use it with
DA> data you care about at this time."
DA> 
DA> That said, zpool(1M) tells:
DA> 
DA>        zpool upgrade [-V version] -a | pool ...
DA> 
DA>            Upgrades the given pool to the latest on-disk version. Once this is
DA>            done, the pool will no longer  be  accessible  on  systems  running
DA>            older versions of the software.
DA> 
DA> and later on:
DA> 
DA>            -V version    Upgrade  to  the specified version. If the -V flag is
DA>                          not specified, the  pool  is  upgraded  to  the  most
DA>                          recent  version.  This  option  can  only  be used to
DA>                          increase the version number, and only up to the  most
DA>                          recent version supported by this software.
DA> 
DA> E.g. you can upgrade pools to ZFS v13, but there's no way back.  If you
DA> don't upgrade your pool, it should not destroy anything (but don't count
DA> on it!), but you won't be able to test any new features either...

Well, I know this well, but for my particular case I should at least test one 
case where previous ZFS implementation panics on *read* access to one 
particular inode; then I hope to convince Kip to dig into the case deep enough 
to fix it ;-)

FWIW, I use ZFS on FreeBSD from the moment it hits RELENG_7, though not too 
high load patterns, and have no major isues so far, modulo this one and obvious 
kmem exhastion.  Even more is my intention to fix this ;-)

-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0905192358080.44708>