reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: Jack Byer <ojbyer@usa.net>, reiserfs-list@namesys.com
Subject: Re: reiser4 resize
Date: Tue, 19 Sep 2006 12:54:30 -0500	[thread overview]
Message-ID: <45102ED6.6080209@slaphack.com> (raw)
In-Reply-To: <200609191723.01936.vs@namesys.com>

Vladimir V. Saveliev wrote:
> Hello
> 
> On Tuesday 19 September 2006 05:12, Jack Byer wrote:
>> Short summary: Will a resize program for reiser4 be available within the
>> next six months?
>>
> 
> Currently nobody works on that. So, I guess it is not very likely that reiser4.resize will be created within next six months.

Not even an expand?  I know a shrink depends on a working repacker (even 
an offline one), but I'd think expanding it would be simple enough, so 
long as there's a big warning of "You cannot undo this (can't shrink)!"

>> When I first created the filesystem, there was a reiser4 resize program.
>> This is no longer the case.
> 
> that was not a working program.

Yes, I remember that, it was a stub.

> I think you should change to a filesystem which has resize.

Alternately, how much would it cost to implement basic resizefs.reiser4?

There are other reasons that make me wish I'd stayed away from reiser4 
for awhile.  Mainly, right now, I need a repacker, and the system seems 
to have become absurdly slow when it's fragmented.  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.

I believe there was a patch to address the thrashing, so I'm eagerly 
awaiting 2.6.18, but the lack of a repacker bothers me.

  reply	other threads:[~2006-09-19 17:54 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 [this message]
2006-09-20  7:39     ` Alexey Polyakov
     [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=45102ED6.6080209@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=ojbyer@usa.net \
    --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).