I have a test Linux MA using a local filesystem directory as a library.
All is working so I can complete my tests however I do not understand the library consumption figures.
Linux lv_root -> size = 55g, available = 34G
(library is /backup which is not a separate lv)
Local library reports -> capacity = 54.5GB, free space = 33.17GB
This matches Linux well
The mount path within the library reports -> same free space and capacity plus ....
total app size = 14.26GB. This is right. Cross-check by ...
- add job sizes, incl metadata
- view contents of media
- du -sh /backup
- these are all consistent
size on disk = 36.77. Whence comes this? This is my question.
If my library was a cloud library it could be possible that the size on disk number does not get updated
( Media Management Configuration -> Service Configuration -> Process volume size updates for cloud mount paths)
but that does not apply here.