From: mdew <mdew@mdew.dyndns.org>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Oleg Drokin <green@namesys.com>, Ivan Gyurdiev <ivg2@cornell.edu>,
Andreas Dilger <adilger@clusterfs.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs4
Date: 08 Aug 2003 03:01:19 +1200 [thread overview]
Message-ID: <1060268478.30293.14.camel@mdew> (raw)
In-Reply-To: <20030807132111.GB7094@louise.pinerecords.com>
On Fri, 2003-08-08 at 01:21, Tomas Szepe wrote:
> > This is no longer true.
> > There is sort of "universal" fs convertor for linux that can convert almost
> > any fs to almost any other fs.
> > The only requirement seems to be that both fs types should have read/write support in Linux.
> > http://tzukanov.narod.ru/convertfs/
>
> I'm afraid I cannot recommend using this tool.
>
> A test conversion from reiserfs to ext3 (inside a vmware machine)
> screwed up the data real horrorshow: directory structure seems
> ok but file contents are apparently shifted.
I'm looking at converting (sometime soon) a JFS system to XFS using
convertfs, I'm hoping this "converting" process will come out bug-free.
Other than backing up all the data, and re-formating to XFS, would any
one have suggestings?
convertfs /dev/hde1 jfs xfs
--
mdew <mdew@mdew.dyndns.org>
next prev parent reply other threads:[~2003-08-07 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 1:05 reiserfs4 Vladimir Lazarenko
2003-08-07 5:02 ` reiserfs4 Andreas Dilger
2003-08-07 5:12 ` reiserfs4 Ivan Gyurdiev
2003-08-07 7:27 ` reiserfs4 Oleg Drokin
2003-08-07 13:21 ` reiserfs4 Tomas Szepe
2003-08-07 14:23 ` reiserfs4 Matthias Schniedermeyer
2003-08-07 14:25 ` reiserfs4 Oleg Drokin
2003-08-07 16:31 ` reiserfs4 Matthias Schniedermeyer
2003-08-07 14:34 ` reiserfs4 Nikita Danilov
2003-08-07 15:01 ` mdew [this message]
2003-08-08 13:05 ` reiserfs4 Hans Reiser
2003-08-08 16:23 ` reiserfs4 Tomas Szepe
2003-08-07 15:20 ` reiserfs4 Ivan Gyurdiev
2003-08-07 10:00 ` reiserfs4 Michael Buesch
2003-08-07 14:00 ` reiserfs4 Hans Reiser
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=1060268478.30293.14.camel@mdew \
--to=mdew@mdew.dyndns.org \
--cc=adilger@clusterfs.com \
--cc=green@namesys.com \
--cc=ivg2@cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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