Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Workaround
-
None
-
None
Description
In ozone, it shows "0" used.
ozone fs -df -h ofs://ozone1/
Filesystem Size Used Available Use%
ofs://ozone1 8.0 E 0 8.0 E 0%
In hdfs
ozone fs -df -h hdfs://ns1/
Filesystem Size Used Available Use%
hdfs://ns1 1.7 T 39.7 G 1.0 T 2%
du command on ozone :
ozone fs -du -h ofs://ozone1/ 6.4 K 6.4 K ofs://ozone1/test-40242 0 0 ofs://ozone1/linkvol 0 0 ofs://ozone1/linkvol1655280938 0 0 ofs://ozone1/test 0 0 ofs://ozone1/vol-04098 7.4 G 7.4 G ofs://ozone1/vol-05896 17.9 G 17.9 G ofs://ozone1/vol-07390 0 0 ofs://ozone1/vol-09790 0 0 ofs://ozone1/vol-09847 29.6 G 29.6 G ofs://ozone1/vol-10185 100 M 100 M ofs://ozone1/vol-test-kill-datanode-1654699785 100 M 100 M ofs://ozone1/vol-test-kill-datanode-1654700250 100 M 100 M ofs://ozone1/vol-test-kill-datanode-1655281572 100 M 100 M ofs://ozone1/vol-test-no-enough-dn-for-replication-1654700762 100 M 100 M ofs://ozone1/vol-test-replicate-all-replicas-1654703211 1.5 G 1.5 G ofs://ozone1/vol-test-replication-multi-containers-same-pipeline-1654701994 200 M 200 M ofs://ozone1/vol-test-replication-with-scm-restart-1654701314 2 G 2 G ofs://ozone1/vol2