On Wed 30 Sep 2009 at 02:02AM, Niall Power wrote:
>
> This one bit me pretty badly not so long ago when it filled up the
> partition I had installed upon. Freeing up the space used is in
> /var/pkg/download is painfully slow when it's grown quite big because
> the content is split into a zillion fragments using what appears to be
> some kind of hashing mechanism.
The way files are hashed in the download cache causes pathologically
bad filesystem performance (oops). Brock is working on fixing this.
> I guess I'm missing part of the bigger picture but.................
> What I don't really understand is what purpose this serves: Even when
> flush-content-cache-on-success is enabled, the cache doesn't get
> flushed in the even of a failed installation, only on success. What's
> the purpose of keeping the content around after a successful
> installation?
For the average desktop system, probably not too much, although if you
want it cleaned up right away, you'll always have to spend some time
waiting for the cleanup. We could of course background the cleanup
somehow. As for keeping it, there are a couple of potential reasons:
- Useful for installing zones.
- Useful for 'pkg fix'.
- In the future (pending several other RFEs being finished),
the download cache could be reshared out to other peers.
The other issue is that we really need to make sure the download cache
is its own filesystem so that contents don't get "trapped" inside of
zfs snapshots.
-dp
--
Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
