 |
what information exactly are you missing? Running "status storage" gives runtime information from the SD. In contrast "list volumes" provides information from the catalog. |
|
|
Whoops, I forgot to mention... The status storage lists AAF274L9 as being pool 'Unknown', whereas 'list volumes' knows that it's in pool Incremental. Shouldn't 'status storage' know this as well? |
|
|
Not neccessarily. The SD doesn't really "know" about pools (unless the director told it something). If - for example - the SD is started with a volume mounted it will determine the volume name (by simply reading its volume label), but it won't be able to determine the pool, as that information is in the catalog on the director only. Thus the SD will show the pool as "unknown". |
|
|
Hmm, ok. But then why show 'Pool: *unknown*' in the first place if the SD never knows the pool anyway? Isn't it less confusing to simply omit the line? |
|
|
I think there are situations where the SD knows the pool, but tbh I'm not sure about that. Feel free to open a pull request for that change. Should be rather trivial. |
|
|
That would be a bit outside my skill set, so I think I'll pass � Thanks for the swift and enlightening replies. |
|
|
I'll close the issue, feel free to reopen it if something related comes up. |
- Anonymous
