Srikumar Venugopal

@starpit I was unable to replicate the issue either on `kind` or in an OpenShift cluster with small files (10s of KB) or comparatively larger files (approx 6 MBs). I...

@rrehman-hbk there seems to be no error in the logs above. There is one `csi-s3` pod per K8s node. Please check all the other ones and please paste the lines...

@elgalu @joebowbeer thanks, will look into how we can surface this at the dataset level (happy to take suggestions on-board)

@nikitok It might be that you had datasets that were still present when you reinstalled datashim. Because of this, the CRD associated with your previous installation has not been deleted....

@Venkatesh7591 have you set `read-only: true` in the dataset

@Venkatesh7591 for your first issue, if it appears again, please paste the logs of csi-s3 daemons here

@vabburi Hi, can you paste the logs for the csi-s3 daemons here ?

@nikitok Could you provide more details on when this is happening ? Infrastructure (i.e. K8s version, provider), type of workload, etc. ?

@Trainbow check if the namespace in which you are creating the datasets is being watched by Datashim. See [this link](https://github.com/datashim-io/datashim/issues/167#issuecomment-1112357851) for an explanation

@Trainbow Could you verify that you have the correct endpoint for the object storage service ? Protocol (`http://` vs 'https://'), Port, etc. Since this error appears in the mounter rather...