Well, I tried to clear the errors, but zpool clear didn't clear them.
I think the errors are in the metadata in such a way that they can't
be cleared. I'm actually a bit scared to scrub it before I grab a
backup, so I'm going to do that first. After the backup, I need to
break the mirror to pull the x4540 out, and I just hope that can
succeed. If not, we'll be loosing some data between the time the
backup is taken and I roll out the new storage.
Let this be a double warning to all you zfs-ers out there: Make sure
you have redundancy at the zfs layer, and also do backups.
Unfortunately for me, penny pinching has precluded both for us until
now.
Jon
On Jun 1, 2009, at 4:19 PM, A Darren Dunham wrote:
On Mon, Jun 01, 2009 at 03:19:59PM -0700, Jonathan Loran wrote:
Kinda scary then. Better make sure we delete all the bad files
before
I back it up.
That shouldn't be necessary. Clearing the error count doesn't disable
checksums. Every read is going to verify checksums on the file data
blocks. If it can't find at least one copy with a valid checksum,
you should just get an I/O error trying to read the file, not invalid
data.
What's odd is we've checked a few hundred files, and most of them
don't seem to have any corruption. I'm thinking what's wrong is the
metadata for these files is corrupted somehow, yet we can read them
just fine.
Are you still getting errors?
--
Darren
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
- _____/ _____/ / - Jonathan Loran - -
- / / / IT Manager -
- _____ / _____ / / Space Sciences Laboratory, UC Berkeley
- / / / (510) 643-5146 jlo...@ssl.berkeley.edu
- ______/ ______/ ______/ AST:7731^29u18e3
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
