Ticket #98 (new bugs)

Opened 12 years ago

Last modified 12 years ago

Cost calculation might be wrong after precious -> cached/sticky (Doris #2612: PoolManager accounting)

Reported by: patrick Owned by: tigran
Priority: major Milestone: 1.8.0-16
Component: core Keywords: PoolManager, cost module, space accounting
Cc: Sub Version:


Dear *, It would be good, if you could add something in the output of "cm ls" about the sticky files in dCache. Before 1.8 files in disk-only pools where marked as precious and as such the output of "cm ls" p= could give an impression of how much space has been used on these pools. Now the files are marked as cached and sticky and are not accounted for anymore. It would be good to have an extra entry in the PoolManager command and in the webpage (usageInfo).

Cheers, Doris

Change History

comment:1 Changed 12 years ago by tigran

  • Milestone changed from 1.8.0-14 to 1.8.0-15

comment:2 Changed 12 years ago by patrick

  • Milestone changed from 1.8.0-15 to 1.8.0-16
Note: See TracTickets for help on using tickets.