From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} rdiff-backup: push or pull?
Date: Thu, 18 Aug 2011 00:03:32 +0200 [thread overview]
Message-ID: <5798822.HQTIkZ2nyT@nazgul> (raw)
In-Reply-To: <2962306.tz4O8xtn7d@weird>
On Wed 17 August 2011 23:49:16 Alex Schuster did opine thusly:
> Grant writes:
> > >> > Can I reserve 0% for root on my USB hard drive which
> > >> > is only
> > >> > used for backups and does not contain an OS?
> > >>
> > >> Yes:
> > >>
> > >> mke2fs -m 0 /dev/usb-drive
> > >
> > > Although a value > 0 helps against fragmentation. And when
> > > rdiff-backup has failed because it ran out of space,
> > > regressing to the previous sane state will need a little
> > > free space.>
> > Good points. Should 10GB (1% of 1TB) do it?
>
> This I don't know. I use this value for large partitions of
> multimedia data, because I do not want to waste space (no matter
> how big the drives are, mine are always quite full), and
> performance should not be a big issue here. I keep the 5% default
> other partitions, like /home. BTW, you can also specify fractions
> like 0.5% if you like.
I prefer to keep reminding myself where 5% comes from. Way back when
ext2 was being developed, 500M drives were big. 5% reserved is 12.5M
or about 12,500 blocks.
Why that amount? Is it really 5% or is it the number of blocks and 5%
just happens to round that out nicely?
Median file sizes haven't changed much in 15 years. The number of
files on an average machine has increased hugely, and the upper size
limit is orders of magnitude bigger, but that doesn't affect the
median size much.
I take the view that 5% is excessive these days and usually reserve
only a tiny amount - something like 10 x the biggest file I expect to
have to deal with when the disk is full.
And besides, as Murphy would have it, it's usually a root process that
fills drives anyway (syslog cough cough) rendering the reserved amount
useless :-)
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-08-17 22:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 4:58 [gentoo-user] {OT} rdiff-backup: push or pull? Grant
2011-08-16 6:35 ` Joost Roeleveld
2011-08-16 23:50 ` Grant
2011-08-17 6:07 ` Joost Roeleveld
2011-08-17 17:18 ` Grant
2011-08-18 6:13 ` Joost Roeleveld
2011-08-19 1:01 ` Grant
2011-08-19 6:07 ` Joost Roeleveld
2011-08-19 17:13 ` Grant
2011-08-17 6:14 ` Joost Roeleveld
2011-08-17 17:35 ` Grant
2011-08-19 17:14 ` Michael Orlitzky
2011-08-19 18:00 ` Grant
2011-08-19 19:06 ` Michael Orlitzky
2011-08-19 19:58 ` Grant
2011-08-20 8:12 ` Alan McKinnon
2011-08-17 6:15 ` Joost Roeleveld
2011-08-17 17:37 ` Grant
2011-08-17 18:54 ` Alex Schuster
2011-08-17 20:47 ` Grant
2011-08-17 21:49 ` Alex Schuster
2011-08-17 22:03 ` Alan McKinnon [this message]
2011-08-18 0:35 ` Peter Humphrey
2011-08-18 6:30 ` Joost Roeleveld
2011-08-19 1:51 ` Grant
2011-08-19 6:13 ` Joost Roeleveld
2011-08-19 17:35 ` Grant
2011-08-21 19:10 ` Joost Roeleveld
2011-08-16 13:39 ` Bill Longman
2011-08-16 14:04 ` Alan McKinnon
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=5798822.HQTIkZ2nyT@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.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