Thanks for all the suggestions. Now for a strange tail...
I tried upgrading to dev 130 and, as expected, things did not go well. All
sorts of permission errors flew by during the upgrade stage and it would not
start X-windows. I've heard that things installed from the contrib and extras
rep
Hi Gary,
You might consider running OSOL on a later build, like build 130.
Have you reviewed the fmdump -eV output to determine on which devices
the ereports below have been generated? This might give you more clues
as to what the issues are. I would also be curious if you have any
driver-level
I've just made a couple of consecutive scrubs, each time it found a couple of
checksum errors but on different drives. No indication of any other errors.
That a disk scrubs cleanly on a quiescent pool in one run but fails in the next
is puzzling. It reminds me of the snv_120 odd number of dis
Mattias Pantzare wrote:
On Sun, Jan 10, 2010 at 16:40, Gary Gendel wrote:
I've been using a 5-disk raidZ for years on SXCE machine which I converted to
OSOL. The only time I ever had zfs problems in SXCE was with snv_120, which
was fixed.
So, now I'm at OSOL snv_111b and I'm finding that
On Sun, Jan 10, 2010 at 16:40, Gary Gendel wrote:
> I've been using a 5-disk raidZ for years on SXCE machine which I converted to
> OSOL. The only time I ever had zfs problems in SXCE was with snv_120, which
> was fixed.
>
> So, now I'm at OSOL snv_111b and I'm finding that scrub repairs errors
I've been using a 5-disk raidZ for years on SXCE machine which I converted to
OSOL. The only time I ever had zfs problems in SXCE was with snv_120, which
was fixed.
So, now I'm at OSOL snv_111b and I'm finding that scrub repairs errors on
random disks. If I repeat the scrub, it will fix error
