All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <yury@clusterfs.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: Alex Zarochentsev <zam@namesys.com>,
	"Dr. Giovanni A. Orlando" <gorlando@futuretg.com>,
	David Masover <ninja@slaphack.com>,
	reiserfs-list@namesys.com
Subject: Re: Reiser4 support on parted program ...
Date: Wed, 15 Sep 2004 16:31:53 +0300	[thread overview]
Message-ID: <41484449.8060301@clusterfs.com> (raw)
In-Reply-To: <20040915132013.GG26192@nysv.org>

Markus Törnqvist wrote:

>On Wed, Sep 15, 2004 at 04:17:48PM +0300, Yury Umanets wrote:
>  
>
>>Alex is right in both. To add such a support one should write resizing 
>>stuff in libreiser4 first. Then write glue code in parted. IMHO both are 
>>not so difficult. Probably Vitaly or Alex self could do that in week 
>>(may be few days).
>>    
>>
>
>How long for Dr. Orlando and his crew in cooperation with Namesys?-)
>  
>
Have no idea :) I do not know anything about Dr. Orlando and his crew.
Suff itself is not difficult, as there is not tree modifications, etc.

Rough sequence is like this:

(1) make sure, that there is no not replied transactions.

(2) tree traverse and move all nodes and unformatted blocks which do not 
fit to new range (new_start - new_end) one by one to new area. Block 
allocator info should be updated on this stage too.

(3) update some fields in super block. Probably one more update of block 
allocator.

The framework for all these actions exists in libreiser4.

Parted's part is trivial -- just follow the API.

>  
>
>>The only problem Hans seems does not want such a support or does not 
>>count it as somethinf serious attention should be paid to :(
>>    
>>
>
>I think his followers would disagree ;)
>
>  
>


-- 
umka


  reply	other threads:[~2004-09-15 13:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 17:49 Reiser4 support on parted program Dr. Giovanni A. Orlando
2004-09-14 22:52 ` David Masover
2004-09-15  7:03   ` Dr. Giovanni A. Orlando
2004-09-15  9:49     ` Alex Zarochentsev
2004-09-15 13:17       ` Yury Umanets
2004-09-15 13:20         ` mjt
2004-09-15 13:31           ` Yury Umanets [this message]
2004-09-15 15:34             ` Dr. Giovanni A. Orlando
2004-09-15 15:42               ` Hans Reiser
2004-09-15 15:45                 ` Dr. Giovanni A. Orlando
2004-09-15 17:47                 ` Yury Umanets
2004-09-15 17:54                   ` Dr. Giovanni A. Orlando
2004-09-16  5:40                     ` Yury Umanets
2004-09-15 15:42           ` Sami Samhuri
2004-09-15 15:44             ` mjt
2004-09-15 15:19         ` Dr. Giovanni A. Orlando
2004-09-15 15:17       ` Dr. Giovanni A. Orlando
2004-09-16 12:36         ` Andrew Clausen
2004-09-16 13:31           ` Yury Umanets
2004-09-16 17:57             ` Dr. Giovanni A. Orlando
2004-09-17  6:11               ` Yury Umanets
2004-09-17  6:42           ` Dr. Giovanni A. Orlando

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=41484449.8060301@clusterfs.com \
    --to=yury@clusterfs.com \
    --cc=gorlando@futuretg.com \
    --cc=mjt@nysv.org \
    --cc=ninja@slaphack.com \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@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.