Erik Trimble writes:
[...]
> The Warning only applies to this circumstance: if you've upgraded
> from an older build, then upgrading the zpool /may/ mean that you will
> NOT be able to reboot to the OLDER build and still read the
> now-upgraded zpool.
Lots of good details snipped... thanks for
On 11 Mar 2010, at 04:17, Erik Trimble wrote:
> Matt Cowger wrote:
>> On Mar 10, 2010, at 6:30 PM, Ian Collins wrote:
>>
>>
>>> Yes, noting the warning.
>>
>> Is it safe to execute on a live, active pool?
>>
>> --m
>>
> Yes. No reboot necessary.
>
> The Warning only applies to this
Matt Cowger wrote:
On Mar 10, 2010, at 6:30 PM, Ian Collins wrote:
Yes, noting the warning.
Is it safe to execute on a live, active pool?
--m
Yes. No reboot necessary.
The Warning only applies to this circumstance: if you've upgraded from
an older build, then upgrading the z
On Mar 10, 2010, at 6:30 PM, Ian Collins wrote:
> Yes, noting the warning.
Is it safe to execute on a live, active pool?
--m
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On 03/11/10 03:21 PM, Harry Putnam wrote:
Running b133
When you see this line in a `zpool status' report:
status: The pool is formatted using an older on-disk format. The
pool can still be used, but some features are unavailable.
Is it safe and effective to heed the advice given i
Running b133
When you see this line in a `zpool status' report:
status: The pool is formatted using an older on-disk format. The
pool can still be used, but some features are unavailable.
Is it safe and effective to heed the advice given in next line:
action: Upgrade the pool using
