Warning message confusing when physical file data location not available about fclones

[jvirkki]

Since you're doing comparisons, if you have a chance to try out https://github.com/jvirkki/dupd on your particular data set, would be interesting to see (dupd scan -p xxx).

[pkolaczk]

This is generally harmless. It means your file system doesn't support getting physical locations of files through the sysctl fiemap API, hence performance is probably much slower than it could be. Anyway glad it is fast despite that optimisation not kicking in.

I'm leaving this open to improve logging.

[dsully]

This is happening for me with ZFS on Ubuntu 20.10 FWIW. Let me know if I can get any more information for you.

[pkolaczk]

I have everything I need. I need to change the message.

[paony]

Issue is clear for fclones then.

Might be an openZFS bug ...

Thanks for the quick reaction