Hello again,
I am still concerned if my points are being well taken.
> If you are concerned that a
> single 200TB pool would take a long
> time to scrub, then use more pools and scrub in
> parallel.
The main concern is not scrub time. Scrub time could be weeks if scrub just
would behave. You ma
I'm running a raidz1 with 3 Samsung 1.5TB drives. Every time I scrub the pool
I get multiple read errors, no write errors and no checksum errors on one drive
(always the same drive, and no data loss).
I've changed cables, changed the sata ports the drives are attached to, I
always get the same
Thanks Richard - I will look into the firmware versions...
On the Corrupt MetaData question, I ran a scrub, and the pool has come up
clean again... So at least the pool is operational, and I am happy not to
have to rebuild that data set. I'm still a little surprised that zpool
status would advis
On Mar 14, 2010, at 11:45 AM, Tonmaus wrote:
> Hi Richard,
>
> thanks for the answer. I think I am aware on the properties of my
> configuration and how it will scale. Let me please stress that this is not
> the point in the discussion.
> The target of this discussion should rather be if scrubbi
Can anyone say what the status of CR 6880994 (kernel/zfs Checksum failures on
mirrored drives) might be?
Setting copies=2 has mitigated the problem, which manifests itself consistently
at
boot by flagging libdlpi.so.1, but two recent power cycles in a row with no
normal
shutdown has resulted in
Hi Richard,
thanks for the answer. I think I am aware on the properties of my configuration
and how it will scale. Let me please stress that this is not the point in the
discussion.
The target of this discussion should rather be if scrubbing can co-exist with
payload or if we are thrown back to
On Mar 14, 2010, at 12:16 AM, Tonmaus wrote:
> Hi Richard,
>
> these are
> - 11x WD1002fbys (7200rpm SATA drives) in 1 raidz2 group
> - 4 GB RAM
> - 1 CPU L5410
> - snv_133 (where the current array was created as well)
These are slow drives and the configuration will have poor random
read perfo
I thought pointing out some of this information might come in handy for some
of the
folks who are new to the (Open)Solaris world.
The following section discusses differences between SMI labels (aka VTOC)
and EFI
GPT labels. It may not be everything one needs to know in order to
successfully
manag
On Sun, Mar 14, 2010 at 4:26 AM, Svein Skogen wrote:
> How does it fare, with regards to BUG ID 689477?
>
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6894775
>
> //Svein
>
>
It fairs identically, it's literally the exact same card OEM'd by Intel and
sold for less money. Same dr
How does it fare, with regards to BUG ID 689477?
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6894775
//Svein
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org
Hi Richard,
these are
- 11x WD1002fbys (7200rpm SATA drives) in 1 raidz2 group
- 4 GB RAM
- 1 CPU L5410
- snv_133 (where the current array was created as well)
Regards,
Tonmaus
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
11 matches
Mail list logo
