Yes, it is helpful in that it reviews all the steps needed to get the
replacement disk labeled properly for a root pool and is identical
to what we provide in the ZFS docs.
The part that is not quite accurate is the reasons for having to relabel
the replacement disk with the format utility.
If
It's a litle while ago, but i've found a http://www.youtube.com/watch?v=tpzsSptzmyA";>pretty helpful video on
YT how to completely "migrate" from one harddrive to another.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-disc
On Wed, 2010-03-03 at 06:59 -0800, Vladimir Leitenberger wrote:
> Hmm is it pissoble to upgrade my current zfs version to the new one, without
> updating whole system (pkg image-update)?
>
> The Problem is, i've made 5.1 Gb free space and tried to make a normal
> update, but upgrading from 111b
Hmm is it pissoble to upgrade my current zfs version to the new one, without
updating whole system (pkg image-update)?
The Problem is, i've made 5.1 Gb free space and tried to make a normal update,
but upgrading from 111b to current 133 is a huge jump. 1050 Mb must be
downloaded and the instal
Daniel Carosone wrote:
On Tue, Mar 02, 2010 at 02:04:52PM -0800, Erik Trimble wrote:
I don't believe that is true for VM installations like Vladimir's,
though I certainly could be wrong.
I think you are :-)
And you would be correct. No booting from EFI labeled disks for now,
an
On Tue, Mar 02, 2010 at 02:04:52PM -0800, Erik Trimble wrote:
> I don't believe that is true for VM installations like Vladimir's,
> though I certainly could be wrong.
I think you are :-)
> Vladimir - I would say your best option is to simply back up your data
> from the OpenSolaris VM, and
Daniel Carosone wrote:
For rpool, which has SMI labels and fdisk partitions, you need to
expand the size of those, and then ZFS will notice (with or withhout
autoexpand, depending on version).
--
Dan.
I don't believe that is true for VM installations like Vladimir's,
though I certainly could be
How can I do that ?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
For rpool, which has SMI labels and fdisk partitions, you need to
expand the size of those, and then ZFS will notice (with or withhout
autoexpand, depending on version).
--
Dan.
pgpHNYyaslcOA.pgp
Description: PGP signature
___
zfs-discuss mailing list
z
Hello Erik, first of all, thanks for quick replay.
About using later builds: Right now I'm using a snv_111b bild (osol2009.06 -
5.11 snv_111b i86pc i386 i86pc Solaris). As i already said, I tried to upgrade
to a newest dev-release but I wasn't lucky with that (panic at the boot,
crushes, etc),
Vladimir Leitenberger wrote:
Hello, Experts.
I've got a problem. I'm trying to expand my main zpool (rpool), but don't know
how to do that. (i'm 100% newbie in non-windows world)
I use Osol under Vmware on Windows.
I had a pretty small vhdd -> only 12gb. Yesterday i decided to expand my virtua
Hello, Experts.
I've got a problem. I'm trying to expand my main zpool (rpool), but don't know
how to do that. (i'm 100% newbie in non-windows world)
I use Osol under Vmware on Windows.
I had a pretty small vhdd -> only 12gb. Yesterday i decided to expand my
virtual drive to 20gb. (After severa
12 matches
Mail list logo
