Open jeroenmaelbrancke opened 7 years ago
After restarting the maintenance agents the used space is now correct. Checked the propagate osd updates in the maintenance agent (default is every 20 sec)
One maintenance agent before the restart the propagate appears every minute instead of every 20 sec.
Jan 05 09:28:32 pocwim-ovs03 alba[52551]: 2017-01-05 09:28:32 190161 +0100 - pocwim-ovs03 - 52551/0 - alba/maintenance - 9453673 - info - propagate 14 osd updates
Jan 05 09:29:31 pocwim-ovs03 alba[52551]: 2017-01-05 09:29:31 739959 +0100 - pocwim-ovs03 - 52551/0 - alba/maintenance - 9461376 - info - propagate 14 osd updates
Trying to verify if the delete-readd asd trigger this issue.
looks like it could be related to / the same issue as #312 & #441
disk_usage
is a value that's maintained inside the ASD.
It's the sum of the sizes of the values that are stored inside that ASD.
As an example, this is an excerpt of the statistics of an ASD that was completely filled and then completely emptied again.
...
"disk_usage": 0.0,
"capacity": 2365308928.0
}
If you look at the state of the file system, you see the following:
[shell 16:48:03.226926] du -h /home/romain/workspace/tmp/alba/asd_mnt
16K /home/romain/workspace/tmp/alba/asd_mnt/lost+found
4.0K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/09
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/08
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/06
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/07
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/02
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/00
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/03
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/05
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/01
12K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00/04
116K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00/00
120K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00/00
124K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00/00
128K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00/00
132K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00/00
136K /home/romain/workspace/tmp/alba/asd_mnt/blobs/00
140K /home/romain/workspace/tmp/alba/asd_mnt/blobs
75M /home/romain/workspace/tmp/alba/asd_mnt/db
79M /home/romain/workspace/tmp/alba/asd_mnt
There are some residual directories, and there's about 75MB
of stuff in the rocksb dir.
most notably:
71M -rw-r--r-- 1 romain romain 247K Jan 18 16:47 000006.log
the transaction log file uses a preallocated slab.
This explains the difference between list-osds
and ls -lRhs
.
I'm absolutely clueless why a restart of a maintenance agent would change this.
@toolslive the size of the content of the rocksdb directory can indeed explain a small difference between list-osds
and ls -lRhs
, however that's not what this ticket is about, because it can't explain:
This ticket is about disk usage information not being properly propagated towards the albamgr. Restart of the maintenance process (which should do this propagation) made the problem go away. See also the other linked issues.
@toolslive is this one fixed by the above PR? please close if so.
No. above PR fixes something else ( #696 ).
The output from list-osds (used size) is not the same as the space the OS is reported.
Configuration: 1 asd per disk removed one asd yesterday and added the same asd back to the backend.
output from list-osds: long_id, used space, total space and percentage
list asd ids on one server:
diskspace usage on OS:
for example:
used space with list_osds = 0.0 used space OS = 25G
Can you please have a look why the used space from list-osds is not correct (for all the osds)?