Hi,
I think you are saying that you copied the data on this system from a
previous system with hardware problems. It looks like the data that was
copied was corrupt, which is causing the permanent errors on the new
system (?)
The manual removal of the corrupt files, zpool scrub and zpool clear
might work, but I don't have experience with this many errors on a
non-redundant config.
If you have a clean backup of this data, you might consider destroying
the green/home dataset, clearing the pool errors, recreating green/home,
and restoring the known, good data.
Maybe someone else can suggest a better approach...
Cindy
On 01/12/10 15:27, epiq wrote:
Cindys, thank you for answer, but i need explain some details. This pool is new hardware for my system - 2x1Tb WD Green hard drives, but data on this pool was copied from old 9x300 Gb hard drives pool with hw problem. while i copied it data where was many errors, but at the end i see this picture :
j...@opensolaris:~# fmdump -eV
fmdump: failed to open /var/fm/fmd/errlog: No such file or directory
and where no READ or WRITE errors on new pool - only CKSUM. As i understand it
closely to transfer errors, then problem with new HW. And now i need only to
clear this permanent errors on new pool, for probably restoring this files from
backups.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
