Chris Williams
2009-Dec-23 17:04 UTC
[zfs-discuss] ZFS pool is in a degraded state and I need some suggestions
I have a system that took a RAID6 hardware array and created a ZFS pool on top of it (pool only has one device in it which is the entire RAID6 HW array). A few weeks ago, the Sun v440 somehow got completely wrapped around the axle and the operating system had to be rebuilt. Once the system was rebuilt, I did a zfs import on the pool. (BTW, I didn''t build the system....just a engineer trying to help out....) Doing a zpool status -v, I saw some files that were damaged. The issue I am seeing now is that when I delete the damaged files in question, this is how it shows up in the output from zpool status -v pool1/data1:<0xba2c7> So my zpool status -v is still showing 1958 errors but instead of showing the paths to the files, I am seeing similar messages to the one above for the files that I deleted. Other that rebuilding the pool from scratch (which might happen), is there any way to get rid of the this error? It doesn''t look like any new errors are occurring, just the original damaged files from when the system died. I thought about running a scrub but I don''t know if that will do much since it isn''t a mirror or raidz. Any ideas would be great Thanks! Chris PS: I know this array probably should of been built treating the disks as a JBOD and have ZFS do the raiding. Unfortunately, nobody asked me when it was built :) -- This message posted from opensolaris.org
Len Zaifman
2009-Dec-23 17:12 UTC
[zfs-discuss] ZFS pool is in a degraded state and I need some suggestions
Chris: This happened to us recently due to some hardware failures. zpool scrub poolname cleared this up for us. We did not try rm damaged file at all. Len Zaifman Systems Manager, High Performance Systems The Centre for Computational Biology The Hospital for Sick Children 555 University Ave. Toronto, Ont M5G 1X8 tel: 416-813-5513 email: leonardz at sickkids.ca ________________________________________ From: zfs-discuss-bounces at opensolaris.org [zfs-discuss-bounces at opensolaris.org] On Behalf Of Chris Williams [chris.d.williams at gmail.com] Sent: December 23, 2009 12:04 PM To: zfs-discuss at opensolaris.org Subject: [zfs-discuss] ZFS pool is in a degraded state and I need some suggestions I have a system that took a RAID6 hardware array and created a ZFS pool on top of it (pool only has one device in it which is the entire RAID6 HW array). A few weeks ago, the Sun v440 somehow got completely wrapped around the axle and the operating system had to be rebuilt. Once the system was rebuilt, I did a zfs import on the pool. (BTW, I didn''t build the system....just a engineer trying to help out....) Doing a zpool status -v, I saw some files that were damaged. The issue I am seeing now is that when I delete the damaged files in question, this is how it shows up in the output from zpool status -v pool1/data1:<0xba2c7> So my zpool status -v is still showing 1958 errors but instead of showing the paths to the files, I am seeing similar messages to the one above for the files that I deleted. Other that rebuilding the pool from scratch (which might happen), is there any way to get rid of the this error? It doesn''t look like any new errors are occurring, just the original damaged files from when the system died. I thought about running a scrub but I don''t know if that will do much since it isn''t a mirror or raidz. Any ideas would be great Thanks! Chris PS: I know this array probably should of been built treating the disks as a JBOD and have ZFS do the raiding. Unfortunately, nobody asked me when it was built :) -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss This e-mail may contain confidential, personal and/or health information(information which may be subject to legal restrictions on use, retention and/or disclosure) for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.
Len Zaifman
2009-Dec-23 17:24 UTC
[zfs-discuss] ZFS pool is in a degraded state and I need some suggestions
from zpool history zpool create -f zfs_hpf c6t600A0B8000495A510000081F492C644Dd0 c6t600A0B8000495B1C0000053148B41F54d0 c6t600A0B8000495B1C0000053248B42036d0 c6t600A0B8000495B1C000005B948CA87A2d0 these are raid5 devices from a 2540 disk controller : we did not us raidz on top we cleaned as follows: 2009-12-17.20:47:41 zpool scrub zfs_hpf and our errors went away the fc connection the above array failed 2x and each time we needed a scrub to clean up the corrupt file error. Len Zaifman Systems Manager, High Performance Systems The Centre for Computational Biology The Hospital for Sick Children 555 University Ave. Toronto, Ont M5G 1X8 tel: 416-813-5513 email: leonardz at sickkids.ca ________________________________________ From: Chris Williams [chris.d.williams at gmail.com] Sent: December 23, 2009 12:22 PM To: Len Zaifman Subject: Re: [zfs-discuss] ZFS pool is in a degraded state and I need some suggestions Was your ZFS pool a mirror or raidz? I didn''t think doing a scrub would help much since it is neither. Thanks Chris On Wed, Dec 23, 2009 at 12:12 PM, Len Zaifman <leonardz at sickkids.ca> wrote:> Chris: > > This happened to us recently due to some hardware failures. > > zpool scrub poolname > > cleared this up for us. We did not try rm damaged file at all. > Len Zaifman > Systems Manager, High Performance Systems > The Centre for Computational Biology > The Hospital for Sick Children > 555 University Ave. > Toronto, Ont M5G 1X8 > > tel: 416-813-5513 > email: leonardz at sickkids.ca > ________________________________________ > From: zfs-discuss-bounces at opensolaris.org [zfs-discuss-bounces at opensolaris.org] On Behalf Of Chris Williams [chris.d.williams at gmail.com] > Sent: December 23, 2009 12:04 PM > To: zfs-discuss at opensolaris.org > Subject: [zfs-discuss] ZFS pool is in a degraded state and I need some suggestions > > I have a system that took a RAID6 hardware array and created a ZFS pool on top of it (pool only has one device in it which is the entire RAID6 HW array). A few weeks ago, the Sun v440 somehow got completely wrapped around the axle and the operating system had to be rebuilt. Once the system was rebuilt, I did a zfs import on the pool. (BTW, I didn''t build the system....just a engineer trying to help out....) > > Doing a zpool status -v, I saw some files that were damaged. The issue I am seeing now is that when I delete the damaged files in question, this is how it shows up in the output from zpool status -v > > pool1/data1:<0xba2c7> > > So my zpool status -v is still showing 1958 errors but instead of showing the paths to the files, I am seeing similar messages to the one above for the files that I deleted. > > Other that rebuilding the pool from scratch (which might happen), is there any way to get rid of the this error? It doesn''t look like any new errors are occurring, just the original damaged files from when the system died. I thought about running a scrub but I don''t know if that will do much since it isn''t a mirror or raidz. > > Any ideas would be great > Thanks! > Chris > > PS: I know this array probably should of been built treating the disks as a JBOD and have ZFS do the raiding. Unfortunately, nobody asked me when it was built :) > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > This e-mail may contain confidential, personal and/or health information(information which may be subject to legal restrictions on use, retention and/or disclosure) for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. >This e-mail may contain confidential, personal and/or health information(information which may be subject to legal restrictions on use, retention and/or disclosure) for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.