All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Clausen <clausen@gnu.org>
To: David Masover <ninja@slaphack.com>
Cc: Jonathan Briggs <jbriggs@esoft.com>,
	"Dr. Giovanni A. Orlando" <gorlando@futuretg.com>,
	Hans Reiser <reiser@namesys.com>,
	Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: Reiser4 repackers
Date: Sat, 7 May 2005 20:25:14 +1000	[thread overview]
Message-ID: <20050507102514.GH8179@gnu.org> (raw)
In-Reply-To: <427C46EC.6080009@slaphack.com>

On Fri, May 06, 2005 at 11:41:16PM -0500, David Masover wrote:
> > Are you familiar with convertfs?
> >
> > 	http://members.optusnet.com.au/clausen/ideas/convertfs.txt
> 
> How easy is it to get the blocklist needed?  It seems like Reiser4's
> packing doesn't help here...

The blocklist is only needed to find the blocks in the nested file,
which is huge.  (I don't know anything about reiser packing, but
things like tail-merging aren't a serious problem.)

> In both of these situations, convertfs seems workable, but overkill.  I
> mean, a proper resizer would leave the FS in a useable state no matter
> which way it went or when power was cut.  Convertfs means that if I lose
> power at any point during the process, I'm very likely hosed, especially
> with something doing lazy writes like Reiser4 as the original FS.  And
> this is all assuming it would work at all.

You could do journalling in this process.  (This would slow it down
considerablly, however!)  If you've got some nice gui like qtparted
on a knoppix live cd, it could be quite convenient.

> These are not situations where enterprise users would pay thousands of
> dollars to be able to do this -- they can afford to do a full
> backup/restore, just throw hardware at a problem and make it go away.
> These are the scenario where small users like me tend to give up, back
> up, reformat, and never touch such an inflexible FS again.

Small users are happy to leave their computer overnight.

Cheers,
Andrew


  reply	other threads:[~2005-05-07 10:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 11:49 Reiser4 support on parted Dr. Giovanni A. Orlando
2005-05-05 15:11 ` Hans Reiser
2005-05-05 17:41 ` Jander
2005-05-05 21:01   ` Dr. Giovanni A. Orlando
2005-05-05 22:10 ` David Masover
2005-05-05 22:12   ` Andrew Clausen
2005-05-05 23:05     ` David Masover
2005-05-06  0:02       ` Andrew Clausen
2005-05-06  2:29         ` David Masover
2005-05-06  6:19       ` Alex Zarochentsev
2005-05-05 23:31   ` Reiser4 repackers Jonathan Briggs
2005-05-06  2:47     ` David Masover
2005-05-06  3:59       ` Andrew Clausen
2005-05-07  4:41         ` David Masover
2005-05-07 10:25           ` Andrew Clausen [this message]
2005-05-08  1:10             ` David Masover
2005-05-08  1:05               ` Andrew Clausen
2005-05-08 13:37                 ` Dr. Giovanni A. Orlando
2005-05-06  5:06       ` Hans Reiser
2005-05-06  9:31         ` Reiser4 support on parted Dr. Giovanni A. Orlando
2005-05-06 12:26           ` Hans Reiser
2005-05-06 19:19           ` Vitaly Fertman

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=20050507102514.GH8179@gnu.org \
    --to=clausen@gnu.org \
    --cc=Reiserfs-List@namesys.com \
    --cc=gorlando@futuretg.com \
    --cc=jbriggs@esoft.com \
    --cc=ninja@slaphack.com \
    --cc=reiser@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.