On Tue, Nov 13, 2012 at 6:16 PM, Karl Wagner wrote:
> On 2012-11-13 17:42, Peter Tribble wrote:
>
> > Given storage provisioned off a SAN (I know, but sometimes that's
> > what you have to work with), what's the best way to expand a pool?
> >
> > Specifically, I can either grow existing LUNs, a]o
On Wed, Nov 14, 2012 at 1:35 AM, Brian Wilson
wrote:
> So it depends on your setup. In your case if it's at all painful to grow the
> LUNs, what I'd probably do is allocate new 4TB LUNs - and replace your 2TB
> LUNs with them one at a time with zpool replace, and wait for the resliver to
> fini
Not sure if this will make it to the list, but I'll try...
On 11/13/12, Peter Tribble
wrote:
> Given storage provisioned off a SAN (I know, but sometimes that's
> what you have to work with), what's the best way to expand a pool?
>
> Specifically, I can either grow existing LUNs, a]or add new L
On 2012-11-13 17:42, Peter Tribble wrote:
> Given storage
provisioned off a SAN (I know, but sometimes that's
> what you have to
work with), what's the best way to expand a pool?
>
> Specifically, I
can either grow existing LUNs, a]or add new LUNs.
>
> As an example, If
I have 24x 2TB LUNs,
> What you could do is to write a program which calls
> efi_use_whole_disk(3EXT) to re-write the label for you. Once you have a
> new label you will be able to export/import the pool
Awesome..
Worked for me, anyways. .C file attached
Although I did a "zpool export" before opening the device
On Sun, Jun 07, 2009 at 10:38:29AM -0700, Leonid Zamdborg wrote:
> Out of curiosity, would destroying the zpool and then importing the
> destroyed pool have the effect of recognizing the size change? Or
> does 'destroying' a pool simply label a pool as 'destroyed' and make
> no other changes...
I
Leonid Zamdborg wrote:
George,
Is there a reasonably straightforward way of doing this partition table edit
with existing tools that won't clobber my data? I'm very new to ZFS, and
didn't want to start experimenting with a live machine.
Leonid,
What you could do is to write a program whi
Out of curiosity, would destroying the zpool and then importing the destroyed
pool have the effect of recognizing the size change? Or does 'destroying' a
pool simply label a pool as 'destroyed' and make no other changes...
--
This message posted from opensolaris.org
> The problem you're facing is that the partition table
> needs to be
> expanded to use the newly created space. This all
> happens automatically
> with my code changes but if you want to do this
> you'll have to change
> the partition table and export/import the pool.
George,
Is there a reaso
Leonid,
I will be integrating this functionality within the next week:
PSARC 2008/353 zpool autoexpand property
6475340 when lun expands, zfs should expand too
Unfortunately, the won't help you until they get pushed to Opensolaris.
The problem you're facing is that the partition table needs to
I'm running 2008.11.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Jun 3, 2009, at 19:37, Leonid Zamdborg wrote:
The new capacity, unfortunately, shows up as inaccessible. I've
tried exporting and importing the zpool, but the capacity is still
not recognized. I kept seeing things online about "Dynamic LUN
Expansion", but how do I do this?
What OS ve
12 matches
Mail list logo
