This message was deleted.

The

strict-local

configuration shouldn't be involved in this issue ... If you copy another file and then delete it, what happen? Same behavior?

@little-kangaroo-65735 I am unable to read the actual files from the worker node's mount path. I understood from the size of the file present inside the mount path. I have copied a 1Gb file first and then deleted it and later copied it again and deleted it but I see 2 1Gb files inside the worker node's mount path

I am unable to read the actual files from the worker node's mount path

What error do you get?

I did not get any error. It should automatically delete the files from the worker node's longhorn mount path after deleting the files from the pod using longhorn volume, otherwise the mount path size grows indefinitely

Ok, now I understand, Try open a github issue or discussion

ok Thanks for your help

Do you have a RWX volume?

No it is RWO volume only

So, if you don't have RWX volume, share-manager pod is not running. The documentation is a bit confusing, you have to execute

fstrim <the mount point>

where

The mount point is either a pod of the workload or the node to which the volume was manually attached

can you please let me know if this is not automatically deleted? And we need to delete it manually using fstrim command?

Trimming will reclaim space wasted by the removed files of the filesystem

, and this operation is not automatic, you have to execute it manually

can you please let me know if this will be automated in the future releases?

I don't think so