Closed immanuelfodor closed 2 years ago
Yes, the WARN stems from the systemd
integration in LINSTOR detecting no running systemd (because it's running in container). Nothing to worry about in this case.
The SpaceTracking messages are a bug that we are currently investigating. It's only used in error reports and other statistics, so it can safely be ignored.
Okay, thanks! Should we keep this issue open for the bug?
Regarding the statistics, I'm not aware of any kind of anonymous data collection or such. Is there something ongoing in any of the Piraeus/Linstor/DRBD services or one that can be opt-in or opt-out?
Should we keep this issue open for the bug?
Yes, you can keep it open as a reminder.
Regarding the statistics, I'm not aware of any kind of anonymous data collection or such.
There is non. That was badly worded on my part. Some commercial users of LINSTOR need to report their used storage space from time to time. This "statistic" never leaves your systems unless you send it.
Bug in question (regarding space tracking) was closed some time ago.
I suspect the below WARN is thrown because we run Linstor dockerized, and not on the host, is it right?
However, why are all satellite pods outputting capacity as 0 when they have 8G disks from which approx 7G is still free? Shouldn't they say something other than 0? This log is there from the first time I started experimenting with Piraeus, it's not new but I was always curious what does it mean and why 0 capacity is logged.