From: "Alexey Polyakov" <alexey.polyakov@gmail.com>
To: David Masover <ninja@slaphack.com>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>, reiserfs-list@namesys.com
Subject: Re: reiser4 resize
Date: Wed, 20 Sep 2006 11:39:08 +0400 [thread overview]
Message-ID: <b5d90b2a0609200039g70c40f5bvb374b5f15b42988d@mail.gmail.com> (raw)
In-Reply-To: <45102ED6.6080209@slaphack.com>
On 9/19/06, David Masover <ninja@slaphack.com> wrote:
> When I have over a
> gig of RAM free (not even buffer/cache, but _free_), and am trying to
> download anything over BitTorrent, even if it's less than 200 megs, the
> disk thrashes so badly that the system is really only usable for web and
> email. Even movies will occasionally stall when this is happening, and
> by "occasionally", I mean every minute or so.
Do you have this problem on plain vanilla + reiser4? I think some
out-of-tree patches (like adaptive readahead?) may result in such
behaviour, independent of file system.
With a free gig of RAM reiser4 shouldn't access disk a lot, only during flushes.
--
Alexey Polyakov
next prev parent reply other threads:[~2006-09-20 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 1:12 reiser4 resize Jack Byer
2006-09-19 13:23 ` Vladimir V. Saveliev
2006-09-19 17:54 ` David Masover
2006-09-20 7:39 ` Alexey Polyakov [this message]
[not found] ` <op.tf52pansd4os1z@localhost>
2006-09-20 9:00 ` Alexey Polyakov
2006-09-21 7:30 ` David Masover
2006-09-21 7:49 ` Łukasz Mierzwa
2006-09-21 7:52 ` Łukasz Mierzwa
2006-09-21 7:48 ` David Masover
2006-09-20 1:09 ` Jack Byer
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 14:38 Reiser4 resize Oleg Osovitskiy
2008-01-30 20:40 ` Edward Shishkin
2008-03-02 22:39 No space left on rfs4 Christopher Sawtell
2008-03-03 20:59 ` Reiser4 resize John
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=b5d90b2a0609200039g70c40f5bvb374b5f15b42988d@mail.gmail.com \
--to=alexey.polyakov@gmail.com \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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;
as well as URLs for NNTP newsgroup(s).