Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Jul 2010 20:45:25 -0400
From:      jhell <jhell@dataix.net>
To:        "Jason J. W. Williams" <jasonjwwilliams@gmail.com>
Cc:        freebsd-current@freebsd.org, grarpamp <grarpamp@gmail.com>
Subject:   Re: [CFT] ZFS v15 patch (version 3)
Message-ID:  <4C3D08A5.2090109@dataix.net>
In-Reply-To: <AANLkTil6vRybs5MQ4jP1Acx3C8VYowwHrG9-EpEH-NxR@mail.gmail.com>
References:  <AANLkTin7I5TKcaEL5bVUXZhjHDXhJIOo4Qv1tVgGhcqa@mail.gmail.com> <AANLkTil6vRybs5MQ4jP1Acx3C8VYowwHrG9-EpEH-NxR@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 07/13/2010 12:30, Jason J. W. Williams wrote:
> If there's any way to backport ZFS log device removal that would be
> very helpful. That's the primary hold up for ops folks moving our
> OpenSolaris servers to FreeBSD.

I second this.

In explanation I have one machine that needs to be rearranged for a
upgrade/update for a different purpose than what it is currently doing
that is holding up some of the other tasks that are planned. I already
made the mistake once in a test situation by removing a log device that
was da0 during a reboot & popped in another device, something happened,
rebooted the machine, plugged in original and the situation was
irreparable causing the pool to be corrupt.

Needless to say it was only a test environment but this has stopped me
cold from using further log devices because of this. ;(

This is not really top priority right now but would be a great Christmas
present ;)

If someone points me in the right direction I guess I could always start
reviewing the changes for inclusion on a patch against head & stable/8.


Regards, Thanks & Good Luck,

-- 

 +-+-+-+-+-+
 |j|h|e|l|l|
 +-+-+-+-+-+



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