Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Suggestions for handling errors after resilver

nasjazz

Newbie
Joined
Nov 6, 2019
Messages
2
I replaced one drive in a 2 drive mirror and resilvered the mirror. The system is now reporting there are permanent errors
in one specific file. The file isn't too important, but I restored it from another copy anyway. But zpool status is still reporting
permanent errors on that file. The help at http://illumos.org/msg/ZFS-8000-8A indicates it may or may not be possible to
clear the status of this error depending on whether the error is in in file data, or metadata.

I'd like to have some confidence everything is ok(even if the one files is lost) and that there isn't some other problem waiting to go south
when the wrong thing happens down the road.

Any suggestions for cleaning up and confirming that health of the zpool in question?
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
4,078
It's possible (but you haven't shared the path of the file, so can't know for sure) that the file that's corrupt is part of a snapshot rather than the live filesystem...

Replacing the file in the live filesystem won't remove the bad copy from the snapshot until the snapshot is removed or expires (and is automatically removed).

Just one possible answer.

You should review the file itself if you can to see if the live copy seems right.
 

nasjazz

Newbie
Joined
Nov 6, 2019
Messages
2
Thanks for the reply. I read back the file that i copied in and it matches, so freenas is serving the file back without problems.

The error message from zpool status is:


errors: Permanent errors have been detected in the following files:

/mnt/Primary/Backup/nov/backup.tar


where the following are configured in freenas
pool = "Primary"
dataset = "Backup"

and the rest of the path is what I created on the share from a remote machine.

So that doesn't appear to be a snapshot, right?
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
4,078
So that doesn't appear to be a snapshot, right?
Seems not based on that path, although I've not had a file corruption on a snapshot to compare to see if it reports as being in the live location or in the snapshot area of the live location.

Do you have snapshots on that dataset? (can you enable the snapshot visibility and browse to previous versions of that file?)
 

sretalla

Wizened Sage
Joined
Jan 1, 2016
Messages
4,078
If your file seems good to you... assuming your other copy that you put back isn't a copy of the file from when it was already corrupt... it may be that you can just do a zpool clear on that pool and keep an eye on it.
 
Top