Re: [osol-help] repair pool - Permanent errors
> From: opensolaris-help-boun...@opensolaris.org [mailto:opensolaris-help- > boun...@opensolaris.org] On Behalf Of Andre Lue > > Try a zpool scrub. Be prepared to be real patient. It could take a while for the > scrub to complete. Do not power cycle the machine to break the sequence > once started. It will most likely lead to more complicated issues. The only thing a scrub can do in this situation, is to possibly find more errors. It can't correct the existing known error. When you scrub, it's going to examine every used block on every disk, and verify its checksum. If there is a cksum mismatch on any device, it will attempt to correct it using good data from a redundant copy (the other side of the mirror.) If there is no good copy of the data found, then it results in a permanent error. The only thing you can do is to rm the file, and hope you can find a good copy somewhere in backups. In fact, anytime you use the filesystem for normal day-to-day reads and so on, it is always checking the cksum for any block it reads. And if a cksum mismatch is detected, the behavior is as described. When you scrub, all it does, is to systematically read every block on every device, thus finding all corruption and correcting all correctable corruption. ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] repair pool - Permanent errors
The problem is that I'm not administrator solaris/opensolaris. But I try solved problems more small. -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] repair pool - Permanent errors
Yes, for me too. -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] repair pool - Permanent errors
Try a zpool scrub. Be prepared to be real patient. It could take a while for the scrub to complete. Do not power cycle the machine to break the sequence once started. It will most likely lead to more complicated issues. -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] repair pool - Permanent errors
> From: opensolaris-help-boun...@opensolaris.org [mailto:opensolaris-help- > boun...@opensolaris.org] On Behalf Of Luana de Freitas > > hi everybody > how i can repair this problem with my pool? > > zpool status -v pool > pool: pool > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. >see: http://www.sun.com/msg/ZFS-8000-8A > scrub: none requested > config: > > NAMESTATE READ WRITE CKSUM > poolONLINE 0 0 0 > c1t0d0s7 ONLINE 0 0 0 > c1t5d0ONLINE 0 0 0 > > errors: Permanent errors have been detected in the following files: > > pool/home2:<0x19f0aa> > /export/xxx/Tools_LCU_sol86_1of1.tar A permanent error is a permanent error. You have a mirrored device, with no checksum errors on either side of the device (I'm guessing you reset the counter.) If there was a checksum error on only one side of the mirror, then the other side of the mirror would have been used automatically to reconstruct the correct data. But a permanent error means there was a checksum failure on both sides of the mirror, for the same data. So there is no good copy of the data anywhere. Most commonly, this type of error occurs if you had a fault in the HBA, or in RAM (and you have non-ECC ram)... Most likely there's nothing wrong with your disks, but some corruption happened in the channel that delivers data to the disks. So most likely the same corrupt data was written to both sides of the mirror, or not at all. Long story short: There is no way to recover that data. Fall back and try to find a good copy in backups. ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] repair pool - Permanent errors
Does it give you the 503 service unavailable screen after log-in? I think this documentation is locked into service contract but I'm not sure, have same type of problem. -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
