On Sat, Nov 10, 2012 at 5:00 PM, Tim Cook wrote:
> On Sat, Nov 10, 2012 at 9:48 AM, Jan Owoc wrote:
>> On Sat, Nov 10, 2012 at 8:14 AM, Trond Michelsen
>> wrote:
>>> How can I replace the drive without migrating all the data to a
>>> different pool? It is possible, I hope?
>> I had the same prob
On Sat, Nov 10, 2012 at 5:04 PM, Tim Cook wrote:
> On Sat, Nov 10, 2012 at 9:59 AM, Jan Owoc wrote:
>> Apparently the currently-suggested way (at least in OpenIndiana) is to:
>> 1) create a zpool on the 4k-native drive
>> 2) zfs send | zfs receive the data
>> 3) mirror back onto the non-4k drive
tron...@gmail.com said:
> That said, I've already migrated far too many times already. I really, really
> don't want to migrate the pool again, if it can be avoided. I've already
> migrated from raidz1 to raidz2 and then from raidz2 to mirror vdevs. Then,
> even though I already had a mix of 512b a
On Sat, Nov 10, 2012 at 6:19 PM, Jim Klimov wrote:
> On 2012-11-10 17:16, Jan Owoc wrote:
>> Any other ideas short of block pointer rewrite?
> A few... one is an idea of what could be the cause: AFAIK the
> ashift value is not so much per-pool as per-toplevel-vdev.
> If the pool started as a set o
On Mon, Nov 12, 2012 at 10:39 AM, Trond Michelsen wrote:
> On Sat, Nov 10, 2012 at 5:00 PM, Tim Cook wrote:
> > On Sat, Nov 10, 2012 at 9:48 AM, Jan Owoc wrote:
> >> On Sat, Nov 10, 2012 at 8:14 AM, Trond Michelsen
> >> wrote:
> >>> How can I replace the drive without migrating all the data to
In general, you can force the unmount with the "-f" flag.
As to your specific question of changing the mountpoint to somewhere that
it can't currently be mounted, it should set the mountpoint property but
not remount it. E.g.:
# zfs set mountpoint=/ rpool/test
cannot mount '/': directory is not
