Errors on a file on a zpool: How to remove?

[Rich]

On Sun, Jan 24, 2010 at 12:15 AM, jhell <jhell at dataix.net> wrote:
> From what I see and what was already mentioned earlier in this thread is
> meta data corruption but the checksum errors do not span across the whole
> pool of vdevs. These are, correct me if I am wrong USB mass storage devices
> ? SSD ?

1.5T Seagate 7200RPM drives.

> In the arrangement of the devices on the system are da2,4,5 on the same hub
> and da6,7 on another ? If this is the case you may have consolidated your
> errors down to being a USB problem and narrowed down to where they are
> connected to.

...no.

All five are on the same SATA controller. These behaviors persist
independent of which SATA controller they are plugged into, and I've
tried all seven in the machine.

> What happened to da1,3 ? Were these once connected to the system ? and if so
> did you start noticing this problem occur roughly about the same period they
> were removed ?

da1,3 are being used in another disk pool, and were never a part of this pool.

This is not an issue of a faulty SATA controller or SATA drives.

This is an issue of "there was a single faulty stick of RAM in the machine".

I have sixteen disks in this machine. These three are having issues
only on these particular files, and only on these files, not on random
portions of the disk. The disks never report read errors - the ZFS
layer is what reports them. SMART is not reporting any difficulties in
reading any sectors of these disks.


I could be mistaken, but I do not believe there to be a faulty
controller in play at this time. I've rotated the drives among the
spares of the 24 ports on the SATA controller in question, as well as
the on-motherboard controller, and this behavior has persisted.

- Rich