Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The renamed destination keys are different for ofs and o3fs.
# ozone fs -rm o3fs://xyz.abc.ozone1/o3fs 21/10/11 11:22:31 INFO Configuration.deprecation: io.bytes.per.checksum is deprecated. Instead, use dfs.bytes-per-checksum 21/10/11 11:22:31 INFO fs.TrashPolicyDefault: Moved: 'o3fs://xyz.abc.ozone1/o3fs' to trash at: /.Trash/om/Current/o3fs # ozone fs -rm ofs://ozone1/abc/xyz/ofs 21/10/11 11:22:00 INFO Configuration.deprecation: io.bytes.per.checksum is deprecated. Instead, use dfs.bytes-per-checksum 21/10/11 11:22:00 INFO fs.TrashPolicyDefault: Moved: 'ofs://ozone1/abc/xyz/ofs' to trash at: ofs://ozone1/abc/xyz/.Trash/om/Current/abc/xyz/ofs # ozone fs -ls -R ofs://ozone1/abc/xyz -rw-rw-rw- 3 om om 0 2021-10-11 11:22 ofs://ozone1/abc/xyz/.Trash/om/Current/abc/xyz/ofs -rw-rw-rw- 3 om om 0 2021-10-11 11:22 ofs://ozone1/abc/xyz/.Trash/om/Current/o3fs
Files lying at same level moves to different trash directory structure.
o3fs -> /<vol>/<buck>/.Trash/<user>/Current/..<dir if any>..
ofs -> /<vol>/<buck>/.Trash/<user>/Current/<vol>/<buck>/..<dir if any>..
Omitting the volume and bucket name from OFS trash key name since its redundant.