From: Ignatich <ignatich@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: reiser4: reserved disk space
Date: Wed, 28 Mar 2007 19:13:37 +0400 [thread overview]
Message-ID: <460A8621.4030709@gmail.com> (raw)
In-Reply-To: <460A74E1.9000703@namesys.com>
Hello Edward,
Thank you for explanation. I'm still not convinced though. Cryptcompress
is indeed awesome, but that doesn't change the fact that reserved block
calculation can be improved. 5% of modern 500GB drive is 25GB and I
can't see how that space will ever be used even if I will delete
thousands of files. There is no point in reserving disk space if it will
never be used. There are many ways to improve this situation: a upper
and lower limit for reserved block count can be used, ability to
manually set reserve can be added to mkfs or perhaps reserve usage
patterns for various workloads can be analyzed and smarter algorithm can
be developed.
Can you suggest how to simulate workload that will expose reserve block
starvation?
Looking forward to your reply,
Max Yudin
prev parent reply other threads:[~2007-03-28 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 12:29 reiser4: reserved disk space Ignatich
2007-03-28 14:00 ` Edward Shishkin
2007-03-28 15:13 ` Ignatich [this message]
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=460A8621.4030709@gmail.com \
--to=ignatich@gmail.com \
--cc=reiserfs-list@namesys.com \
/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