On 2018-11-15 11:53, Gene Heskett wrote:
On Thursday 15 November 2018 07:36:37 Austin S. Hemmelgarn wrote:
On 2018-11-15 06:16, Gene Heskett wrote:
I ask because after last nights run it showed one huge and 3 teeny
level 0's for the 4 new dle's. So I just re-adjusted the locations
of some categories and broke the big one up into 2 pieces.
"./[A-P]*" and ./[Q-Z]*", so the next run will have 5 new dle's.
But an estimate does not show the new names that results in. I've
even took the estimate assignment calcsize back out of the global
dumptype, which ack the manpage, forces the estimates to be derived
from a dummy run of tar, didn't help.
Clues? Having this info from an estimate query might take a couple
hours, but it sure would be helpfull when redesigning ones dle's.I'm
fairly certain you can't, because it specifically shows server-side
estimates, which have no data to work from if there has never been a
dump run for the DLE.
Even if you told it to user tar for the estimate phase? That has enough
legs to be called a bug. IMO anyway.
As mentioned in one of my other responses, I can kind of see the value
in this not bothering the client systems. Keep in mind that server
estimates cost nothing on the client, while calcsize or client estimates
may use a significant amount of resources.
In this case, I do think the documentation should be a bit clearer, and
it would be useful to be able to get regular (calcsize and/or client)
estimates on-demand, but I do think that the default is reasonably sane.
