HDDS-5677. When use s3g and goofys , mkdir a directory but file is cr…

[zhengchenyu]

What changes were proposed in this pull request?

First mount bucket1

goofys --endpoint http://localhost:9878 bucket1 /mount/bucket1

Reproduce case:
when I mkdir /mount/bucket1/dir1, but I found /mount/bucket1/dir1 is a file in actually.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-5677

How was this patch tested?

manual tests

[bharatviswa504]

@zhengchenyu is this with ozone.om.enable.filesystem.paths enabled
If so, I have also faced similar issue with S3AFileSystem and proposed similar fix.

That got closed out saying we donot support S3A FileSystem in FileSystem compat mode. When ozone.om.enable.filesystem.paths is enabled, we normalize the paths, that is causing this issue. For more info refer to the below PR discussion.

#1418

if possible for now you can try with config disabled and give a try, and let us know if you are still seeing the issue.

Once bucket type feature comes in, a single ozone cluster can support both FS and complete Object Store buckets.
https://issues.apache.org/jira/browse/HDDS-5672

[zhengchenyu]

@bharatviswa504 Yeah it works , after ozone.om.enable.filesystem.paths is set to false, ozone.om.metadata.layout is set to SIMPLE, and apply #2583. Thanks, I will close this issue.

BTW, Since HDDS-5672, maybe s3v volume should be a fixed assignment for BucketLayout: ObjectStore.

[bharatviswa504]

@bharatviswa504 Yeah it works , after ozone.om.enable.filesystem.paths is set to false, ozone.om.metadata.layout is set to SIMPLE, and apply #2583. Thanks, I will close this issue.

BTW, Since HDDS-5672, maybe s3v volume should be a fixed assignment for BucketLayout: ObjectStore.

Bucket layout need to be set at. bucket level, not at volume level.

[zhengchenyu]

@bharatviswa504 Yeah it works , after ozone.om.enable.filesystem.paths is set to false, ozone.om.metadata.layout is set to SIMPLE, and apply #2583. Thanks, I will close this issue.
BTW, Since HDDS-5672, maybe s3v volume should be a fixed assignment for BucketLayout: ObjectStore.

Bucket layout need to be set at. bucket level, not at volume level.

I mean that all bucket in s3v volume should be set to ObjectStore BucketLayout.