Hello.
3 month old pool hosted across two SAS JBODs w/ SATA disks on an x4170m2
running Solaris 11 SRU6.6, ran a scrub and I got this:
pool: zdata
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Res
On 2012-11-10 17:16, Jan Owoc wrote:
Any other ideas short of block pointer rewrite?
A few... one is an idea of what could be the cause: AFAIK the
ashift value is not so much per-pool as per-toplevel-vdev.
If the pool started as a set of the 512b drives and was then
expanded to include sets of
On Sat, Nov 10, 2012 at 9:04 AM, Tim Cook wrote:
> On Sat, Nov 10, 2012 at 9:59 AM, Jan Owoc wrote:
>> Sorry... my question was partly answered by Jim Klimov on this list:
>> http://openindiana.org/pipermail/openindiana-discuss/2012-June/008546.html
>>
>> Apparently the currently-suggested way (a
On Sat, Nov 10, 2012 at 9:59 AM, Jan Owoc wrote:
> On Sat, Nov 10, 2012 at 8:48 AM, Jan Owoc wrote:
> > On Sat, Nov 10, 2012 at 8:14 AM, Trond Michelsen
> wrote:
> >> When I try to replace the old drive, I get this error:
> >>
> >> # zpool replace tank c4t5000C5002AA2F8D6d0 c4t5000C5004DE863F2d
On Sat, Nov 10, 2012 at 9:48 AM, Jan Owoc wrote:
> On Sat, Nov 10, 2012 at 8:14 AM, Trond Michelsen
> wrote:
> > When I try to replace the old drive, I get this error:
> >
> > # zpool replace tank c4t5000C5002AA2F8D6d0 c4t5000C5004DE863F2d0
> > cannot replace c4t5000C5002AA2F8D6d0 with c4t5000C5
On Sat, Nov 10, 2012 at 8:48 AM, Jan Owoc wrote:
> On Sat, Nov 10, 2012 at 8:14 AM, Trond Michelsen wrote:
>> When I try to replace the old drive, I get this error:
>>
>> # zpool replace tank c4t5000C5002AA2F8D6d0 c4t5000C5004DE863F2d0
>> cannot replace c4t5000C5002AA2F8D6d0 with c4t5000C5004DE86
On Sat, Nov 10, 2012 at 8:14 AM, Trond Michelsen wrote:
> When I try to replace the old drive, I get this error:
>
> # zpool replace tank c4t5000C5002AA2F8D6d0 c4t5000C5004DE863F2d0
> cannot replace c4t5000C5002AA2F8D6d0 with c4t5000C5004DE863F2d0:
> devices have different sector alignment
>
>
> H
On Tue, Sep 25, 2012 at 6:42 PM, LIC mesh wrote:
> The new drive I bought correctly identifies as 4096 byte blocksize!
> So...OI doesn't like it merging with the existing pool.
So... Any solution to this yet?
I've got a 42 drive zpool (21 mirror vdevs) with 12 2TB drives that
has 512byte blocksi
