reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John <geearf@free.fr>
To: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 resize
Date: Mon, 3 Mar 2008 21:59:59 +0100	[thread overview]
Message-ID: <0f5c92f3901a9fee53965e43e4bca960@free.fr> (raw)
In-Reply-To: <b8d16a880803021439m58cb9251uabe3b57c1c57f971@mail.gmail.com>


Edward Shishkin wrote:
>Oleg Osovitskiy wrote:

>>Hello!
>>  
>>

>Hi

>>  Does Reiser4 fs support resize as reiserfs ?
>>  
>>

>nop, sorry..

>>If yes which tool I have to use to enlarge my reiser4 fs ?
>>
>>---
>>Best regards, Oleg O. Osovitskiy
>>mailto:o.osovitskiy@rambler.ru, icq# 33366588


Hi there,

While playing with LVM today I was wondering about that too.
How hard would that be?
(What will follow are just assumptions from my memories of writing FS, so sorry if I'm way off with R4)

- Growing should not be too hard as only the main table would need to be changed no?
- As for shrinking I see 2 cases:
   a- There is no data beyond my desired new end, it looks like I only need to modify the table
   b- There is some data bothering us, now we need to pull it the same way as a repacker would do I believe.


The first 2 cases look easy. For the last it would need something close to a defrag.

So again, how hard would it be to write a dirty resizer? I have no Linux or R4 dev knowledge, but I have a lot spare time and I'm willing to put some of my data at risk. C is not an issue either. Do you think I can try something if you give me some pointers or am I just day-dreaming?

Thanks,

John


  reply	other threads:[~2008-03-03 20:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 16:45 No space left on rfs4 John
2008-03-01 21:27 ` Edward Shishkin
2008-03-01 21:50   ` John
2008-03-01 22:54     ` Edward Shishkin
2008-03-01 23:05       ` John
2008-03-02 10:17         ` Edward Shishkin
2008-03-02 21:53           ` John
2008-03-02 22:39             ` Christopher Sawtell
2008-03-03 20:59               ` John [this message]
2008-03-08 19:24             ` Edward Shishkin
2008-03-11 21:39               ` Edward Shishkin
2008-03-11 22:19                 ` John
2008-03-12  0:06                   ` Edward Shishkin
  -- 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
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
     [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

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=0f5c92f3901a9fee53965e43e4bca960@free.fr \
    --to=geearf@free.fr \
    --cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).