public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Goller <morfic@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] digest-* files in portage tree
Date: Fri, 25 Mar 2005 00:04:41 -0600	[thread overview]
Message-ID: <4243A9F9.805@gentoo.org> (raw)
In-Reply-To: <4242BF20.2000100@pnpitalia.it>

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

Francesco Riosa wrote:
> In addition to "Manifest" files in portage tree there are 19000
> "digest-${P}" files in the portage tree each of this uses 4k on ext{2,3}
> filesystem and has to be scanned each time rsync is run on the tree.
> Is possible to avoid the use of theese files?
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
while not technically what you asked for, keeping the tree on a
partition with a smaller than default block and inode size would allow
you to decrease wasted space significantly, ext3 does 1024 in linux
iirc, docs suggest 512 should be possible, but i have not found a fs on
linux that did indeed allow actual use of 512byte blocks/inodes (yes you
want to make sure to adjust both, not just one)

hope this helps while people consider integrating them elsewhere to safe
the most space possible



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2005-03-25  6:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 13:22 [gentoo-dev] digest-* files in portage tree Francesco Riosa
2005-03-24 13:36 ` Chris Gianelloni
2005-03-24 14:16   ` Francesco Riosa
2005-03-24 14:37     ` Mike Frysinger
2005-03-24 15:45       ` Francesco Riosa
2005-03-24 15:42 ` Aron Griffis
2005-03-25  1:46   ` Marius Mauch
2005-03-25  4:28     ` Daniel
2005-03-27  3:31       ` Daniel
2005-03-26  7:43     ` Peter Cech
2005-03-25  6:04 ` Daniel Goller [this message]
2005-03-25  7:12   ` Robin H. Johnson
2005-03-25 23:55     ` [gentoo-dev] " Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4243A9F9.805@gentoo.org \
    --to=morfic@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox