Brandon,
Thanks for replying to the message.
I believe that this is more related to the variable stripe size of RAIDZ
than the fdisk MBR. I say this because the disk works without any issues in
a mirror configuration or as standalone reaching 80 MB/s burst transfer
rates.
In RAIDZ, however, the
On Sat, Apr 24, 2010 at 5:02 PM, Leandro Vanden Bosch
l.vbo...@gmail.com wrote:
Confirmed then that the issue was with the WD10EARS.
I swapped it out with the old one and things look a lot better:
The problem with the EARS drive is that it was not 4k aligned.
The solaris partition table was,
Just in case someone of you want to jump in, I created the case
#100426-001820 to WD to ask for a firmware update to the WD??EARS drives
without any 512-byte emulation, just the 4K sectors directly exposed.
The WD forum thread:
Hello everyone,
As one of the steps of improving my ZFS home fileserver (snv_134) I wanted
to replace a 1TB disk with a newer one of the same vendor/model/size because
this new one has 64MB cache vs. 16MB in the previous one.
The removed disk will be use for backups, so I thought it's better off
ZFS first does a scan of indicies and such, which requires lots of seeks. After
that, the resilvering starts. I guess if you give it an hour, it'll be done
roy
- Leandro Vanden Bosch l.vbo...@gmail.com skrev:
Hello everyone,
As one of the steps of improving my ZFS home fileserver
Thanks Roy for your reply.
I actually waited a little more than an hour, but I'm still going to wait a
little longer following your suggestion and a little hunch of mine. I just
found out that this new WD10EARS is one of the new 4k disks. I believed that
only the 2TB models where 4k.
See:
BEFORE
Confirmed then that the issue was with the WD10EARS.
I swapped it out with the old one and things look a lot better:
pool: datos
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait
