ZFS Extra files created when resilvering

A

antperval

Hi everyone,

Some months ago, we experienced some issues with one of our enclosures (One of the pools was affected and we had errros like resilvering not finishing, lot of disk removed from the same pool...) We solved it by replacing backplane and worked like charm.

Some weeks ago, we had to replace a disk in the same pool. It was more or less an expected issue as disk to be replaced was the disk that had been working in the deffective bay of the old backplane. No problem, disk replaced and working. This enclosure is storing old data. No access to the disks to write information (only reading)

In our normal workday, we perform scheduled auditories of our storage to verify there are no changes. In the last auditory, we have realized that there are new files that shouldn't be there (they are hidden files)

Perhaps it's a strange question, and I bet answer is no but...Have you ever seen that a resilver creates temporary files?

We are pretty sure there has not been external access to the enclosure and we are getting crazy to try to fix the issue.

Thank you very much in advance,
 
Hi Martin,

Thank you very much for your answer and sorry for the late response. We have excuted the command proposed. Problem is that we have detected the issue now but file creation was 7 months ago, so we are not sure if we had a resilver on that date or issue could come from other cause.

It sounds strange that resilver creates extra files, but we preferred to ask community just in case some other experienced this fact in the past.

Thanks!
 
It’s highly unlikely (I would suggest impossible) that a resilver created files. It is rebuilding blocks at the zpool level and doesn’t have anything to do with the actual ZFS file system, which is basically an addition software layer that implements a posix file system and stores its data/metadata in a zpool.

Maybe we could have a better guess if we knew what the server runs, and what these files are called / path on the server.
 
Aren't these just similar to the (partial) files that can appear in lost+found after an fsck(8)? The scrub (or resilvering) may have found some "orphaned" metadata and various blocks of data and simply tried to restore it to a consistent state.
 
You must log in or register to reply here.
Back
Top