Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
which will clear the old entries out of the zpool.cache and look for
the new devices.
More below...
Brian Leonard wrote:
I had a machine die the other day and
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
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
Above, I used slice 0 as an example, your system may use a
different slice. But you can run zdb -l on all of
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 reasonably
Brian Leonard wrote:
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
Above, I used slice 0 as an example, your system may use a
different slice. But you
I've been playing around with zfs root pool mirroring and came across some
problems.
I have no problems mirroring the root pool if I have both disks attached during
OpenSolaris installation (installer sees 2 disks).
The problem occurs when I only have one disk attached to the system during
h... export the pool again. Then try simply zpool import
and it should show the way it sees vault. Reply with that output.
zpool export vault
cannot open 'vault': no such pool
zpool import
pool: vault
id: 196786381623412270
state: UNAVAIL
action: The pool cannot be imported due
Hi Noz,
This problem was reported recently and this bug was filed:
6844090 zfs should be able to mirror to a smaller disk
I believe slice 9 (alternates) is an older method for providing
alternate disk blocks on x86 systems. Apparently, it can be removed by
using the format -e command. I
Brian Leonard wrote:
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
Above, I used slice 0 as an example, your system may use a
different slice. But you can run
noz wrote:
I've been playing around with zfs root pool mirroring and came across some
problems.
I have no problems mirroring the root pool if I have both disks attached during
OpenSolaris installation (installer sees 2 disks).
The problem occurs when I only have one disk attached to the
Victor took the words right out of my fingers :-) more below...
Victor Latushkin wrote:
Brian Leonard wrote:
Since you did not export the pool, it may be looking for the wrong
devices. Try this:
zpool export vault
zpool import vault
That was the first thing I tried, with no luck.
I believe slice 9 (alternates) is an older method for
providing
alternate disk blocks on x86 systems. Apparently, it
can be removed by
using the format -e command. I haven't tried this
though.
format -e worked!! It is resilvering as I type this message. Thanks!!
I don't think removing
On 06/04/09 06:44 PM, cindy.swearin...@sun.com wrote:
Hi Noz,
This problem was reported recently and this bug was filed:
6844090 zfs should be able to mirror to a smaller disk
Is this filed on bugs or defects? I had the exact same problem,
and it turned out to be a rounding error in Solaris
Check contents of /dev/dsk and /dev/rdsk to see if
there are some
missing links there for devices in question. You may
want to run
devfsadm -c disk -sv
devfsadm -c disk -Csv
and see if it reports anything.
There were quite a few links it removed, all on c0.
Try to move c6d1p0 and
14 matches
Mail list logo
