Hi all,
I have created a zpool with 2 LUNs from a same raid-disk(3+1 raid5) of
ST2540.
#zpool create mypool2 c1t1d0 c2t2d0(c1t1d0 stand for LUN1 and c2t2d0
stand for LUN2 for explaining simply).
Just because the 2 LUNs is come from the same RAID-group, I wanna create
the zpool in concatenation
OK, my bad. I was looking at the WRONG bootserver, on another network.
Shared out the U8 DVD, boot net -s, and can import the zpool.
On Tue, Oct 27, 2009 at 6:01 PM, Tim Cook t...@cook.ms wrote:
On Tue, Oct 27, 2009 at 4:59 PM, dick hoogendijk d...@nagual.nl wrote:
Tim Cook wrote:
Increasing is not that problem. ZFS does it automatically. Change the
size of a partition or replace a disk with a bigger one and it will
use the newly available space.
--
Ted Turner - Sports is like a war without the killing. -
http://www.brainyquote.com/quotes/authors/t/ted_turner.html
Hi there,
While receiving incremental streams, zfs recv ignores the existing
snapshots and stops without processing rest of the streams.
Here is the scenario.
# zfs snapshot sp...@s1
# zfs send sp...@s1 | zfs recv dpath
# zfs snapshot sp...@s2
# zfs snapshot sp...@s3
# zfs send -I sp...@s1
On Tue, 27 Oct 2009 18:42:08 +0100, Bruno Sousa
bso...@epinfante.com wrote:
I often find alot of customers that say that it's
far more easy to convince the Board of Directors
to buy software rather than hardware or a appliance.
My observation is a trend towards (fully supported)
appliances /
Raghav Ilavarasu wrote:
Hi there,
While receiving incremental streams, zfs recv ignores the existing
snapshots and stops without processing rest of the streams.
Here is the scenario.
# zfs snapshot sp...@s1
# zfs send sp...@s1 | zfs recv dpath
# zfs snapshot sp...@s2
# zfs snapshot
Hi,
I've got an OpenSolaris 2009.06 box that will reliably panic whenever
I try to import one of my pools. What's the best practice for
recovering (before I resort to nuking the pool and restoring from
backup)?
There are two pools on the system: rpool and tank. The rpool seems to
be fine, since
Donald Murray, P.Eng. wrote:
Hi,
I've got an OpenSolaris 2009.06 box that will reliably panic whenever
I try to import one of my pools. What's the best practice for
recovering (before I resort to nuking the pool and restoring from
backup)?
Could you please post panic stack backtrace?
There
I am also running 2 of the Supermicro cards. I just upgraded to b126 and it
seems improved. I am running a large file copy locally. I get these warnings in
the dmesg log. When I do, I/O seems to stall for about 60sec. It comes back up
fine, but it's very annoying. Any hints? I have 4 disks per
