zpool status error <0xc245>:<0x8b09>

[Bostjan]

How to find these files and take required actions?

Code:

root@freenas:~ # zpool status -v
  pool: nas2
 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://illumos.org/msg/ZFS-8000-8A

config:

        NAME                                            STATE     READ WRITE CKSUM
        nas2                                             ONLINE       0     0 1
          mirror-0                                      ONLINE       0     0 0
            gptid/72c347a2-69f4-11e9-af93-d05099c2bdbf  ONLINE       0     0 0
            gptid/737027446-69f4-11e9-af93-d05099c2bdbf  ONLINE       0     0 0
          mirror-1                                      ONLINE       0     0 2
            gptid/74882668-69f4-11e9-af93-d05099c2bdbf  ONLINE       0     0 2
            gptid/77b830d6-69f4-11e9-af93-d05099c2bdbf  ONLINE       0     0 2

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

        <0xc245>:<0x8b09>

I don’t want to use # zpool clear nas2 command. I’d like to solve the problem first, but I don’t know how.
I’ve googled for this error and also search on this forum, but no results for this error.

How to solve this problem?

 

[Jailer]

That's metadata corruption and that's not good. I hope you have good backups.

The bigger issue is how it got that way in the first place. Complete hardware specs, per the forum rules, are needed to help any further.

 

[WW1 Flying Ace]

It looks like ZFS can only give you the location for the file(s), like it doesn't "know" the file names. Did you get this after scrubbing the pool?

 

[Bostjan]

@Jailer yes, I also wanted to know how it got that way. I still do.

I ran scrub one more time. The errors are gonne.

Now I get

Code:

# zpool status
...
scan: scrub repaired 128K in 0 days 04:05:04 with o errors on Wed Oct 23 10:52:31 2019
...

Thank you all for replying.