2009/1/30 Ewan MacMahon <[log in to unmask]>:
>> -----Original Message-----
>> From: GRIDPP2: Deployment and support of SRM and local storage
>> Hi Ewan, (and others)
>>
>> Can you try running this query?
>>
> Hi,
>
> I'm just getting back onto this after a few local distractions; running
> that
> query gives us:
>
> +--------------------------------------+---------------------+---------+
> -----------------+
> | Space Token | Token Desc. | # Files |
> Total Size (GB) |
> +--------------------------------------+---------------------+---------+
> -----------------+
> | | NULL | 74769 |
> 4704.223786 |
> | NULL | NULL | 10 |
> 0.000000 |
> | f1171e3a-a112-4069-b6b8-7f54a4a9c3c4 | ATLASDATADISK | 1797 |
> 504.630595 |
> | adfd9d4a-ac99-4c14-8a43-0365e0d6b1e8 | ATLASGROUPDISK | 1 |
> 0.000002 |
> | e957b434-b61c-48eb-9aa0-01dc58cd5b97 | ATLASLOCALGROUPDISK | 26139 |
> 784.871504 |
> | 00522908-91fb-4c5b-8816-b036d3b56a3d | ATLASMCDISK | 296222 |
> 8937.174374 |
> | 574944c4-0ddf-4eb4-b66c-0ffba12a28dc | ATLASPRODDISK | 3106 |
> 167.958198 |
> | 2be8239e-01e7-4197-9c9a-9e15fa403223 | ATLASUSERDISK | 25541 |
> 1106.292630 |
> +--------------------------------------+---------------------+---------+
> -----------------+
> 8 rows in set (5.04 sec)
>
> Which I think looks relatively sane (with the possible exception of the
> first row).
The first row is sane, it simply refers to the existence of files
without space-tokens in DPM, which we expect.
I'm more surprised by the second row - I'm not sure where you're
getting files with NULL as a setname from... since there's only 10 of
them, though, it's probably not important(?)
> dpm-listspaces, however, shows:
>
>
> So it seems to have the correct space token descriptions, the correct
> 'actual' space
> tokens, but not be reporting the usage.
Right, that seems to match a conversation Greig and I were having
about precisely how DPM implements space tokens internally.
I asked the DPM developers for some details of how this works this
morning so we can understand better precisely what's broken and how to
properly fix it.
>Also; if the 'Total Size (GB)'
> column in the
> mysql output is total amount /used/ then is appears to add up to ~16Tb,
> whereas
> dpm-listspaces thinks the total usage is 8.24Tb. The 25Tb shown as
> 'unavailable' is,
> I think, correct - we've got some pools marked as readonly, and their
> free space
> adds to about that amount.
>
The total size disparity is something I noticed too, and have
mentioned to Greig. dpm-listspaces appears to do the "right thing" in
adding up the total usage, though, so it is a puzzle.
> Ewan
>
|