From: Jeffrey Mahoney <jeffm@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Mike Benoit" <ipso@snappymail.ca>, "Jan Kara" <jack@suse.cz>,
"Jure Pečar" <pegasus@nerv.eu.org>,
reiserfs-list@namesys.com
Subject: Re: ReiserFS v3 choking when free space falls below 10%?
Date: Wed, 12 Jul 2006 01:52:50 -0400 [thread overview]
Message-ID: <44B48E32.5080307@suse.com> (raw)
In-Reply-To: <44B48BC0.2000608@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans Reiser wrote:
> You make this way too complicated because you are trying to be way too
> perfect. If you scan 3 bitmap blocks and find nothing, stop trying to
> size match.
Agreed on the trying too hard. I think we can find a better, less
"perfect" solution. I wrote that email on Friday on my notebook and it
couldn't connect. It managed to do so this evening. I spent the weekend
experimenting with the idea, and while I came up with something that
worked, it wasn't really usable. The memory footprint was much too large
to be worthwhile. For some fragmentation patterns, it would work. The
worst case scenario was totally intolerable.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEtI4xLPWxlyuTD7IRAh0uAJ4xqU2JFRUqgyQYDDQBr0oGBJBCXgCcCXD7
et36eQ8yUt3CD7e6+thPZvU=
=iFAe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-12 5:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:41 ReiserFS v3 choking when free space falls below 10%? Mike Benoit
2006-06-29 19:12 ` Vladimir V. Saveliev
2006-06-29 20:15 ` Mike Benoit
2006-06-29 20:22 ` Vladimir V. Saveliev
2006-06-29 21:01 ` Mike Benoit
2006-06-29 20:36 ` Nate Diller
2006-06-30 16:33 ` Hans Reiser
2006-06-30 16:47 ` Jeff Mahoney
2006-06-30 17:04 ` Hans Reiser
2006-06-30 17:46 ` Mike Benoit
2006-06-30 18:18 ` Hans Reiser
2006-07-05 0:37 ` Mike Benoit
2006-07-05 2:37 ` Hans Reiser
2006-07-05 14:42 ` Tom Vier
2006-07-05 19:12 ` Jeff Mahoney
[not found] ` <20060706125856.fdac1d16.pegasus@nerv.eu.org>
2006-07-06 15:43 ` Mike Benoit
2006-07-06 16:01 ` Jonathan Briggs
2006-07-06 17:26 ` Toby Thain
2006-07-06 17:26 ` Toby Thain
2006-07-06 18:02 ` Jeff Mahoney
2006-07-06 18:12 ` Hans Reiser
2006-07-06 18:19 ` Jeff Mahoney
2006-07-06 18:47 ` Mike Benoit
2006-07-06 19:17 ` Hans Reiser
2006-07-06 18:27 ` Mike Benoit
2006-07-06 18:39 ` Jeff Mahoney
2006-07-07 7:29 ` Mike Benoit
2006-07-07 17:49 ` Jan Kara
2006-07-07 17:50 ` Jeff Mahoney
2006-07-07 18:07 ` Jan Kara
2006-07-07 18:08 ` Jeff Mahoney
2006-07-07 19:05 ` Hans Reiser
2006-07-07 19:18 ` Jan Kara
2006-07-07 19:38 ` Hans Reiser
2006-07-07 20:18 ` Mike Benoit
2006-07-07 21:04 ` Mike Benoit
2006-07-07 21:20 ` Hans Reiser
2006-07-08 18:45 ` Jeff Mahoney
2006-07-09 0:01 ` Hans Reiser
2006-07-09 0:02 ` Hans Reiser
2006-07-12 0:54 ` Jeffrey Mahoney
2006-07-12 5:42 ` Hans Reiser
2006-07-12 5:52 ` Jeffrey Mahoney [this message]
2006-07-12 8:18 ` Hans Reiser
2006-07-12 16:06 ` Jeff Mahoney
2006-07-24 22:26 ` ReiserFS v3 choking when free space falls below 10% - FIXED Mike Benoit
2006-07-24 22:32 ` Jeff Mahoney
2006-07-26 0:10 ` David Masover
2006-07-26 2:25 ` Mike Benoit
2006-07-26 14:29 ` Hans Reiser
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=44B48E32.5080307@suse.com \
--to=jeffm@suse.com \
--cc=ipso@snappymail.ca \
--cc=jack@suse.cz \
--cc=pegasus@nerv.eu.org \
--cc=reiser@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.