From: "Diaz Rodriguez, Eduardo" <ediaz@pk25.com>
To: reiserfs-list@namesys.com
Subject: Conversion from v3.6 to v4 of Reiserfs...
Date: Tue, 24 Feb 2004 18:30:22 +0100 [thread overview]
Message-ID: <20040224172153.M90659@pk25.com> (raw)
Sorry for the question from a newbie but I can'f find the answer and I find in
google maillist and may sites...
I recently upgrade from 2.4.20 kernel to 2.6.3 kernel my debian testing.
I see in logs that my lvm system are using version 3.6 of resiser fs.
Feb 23 21:57:12 servidor1 kernel: found reiserfs format "3.6" with standard
journal
Feb 23 21:57:12 servidor1 kernel: Reiserfs journal params: device dm-0, size
8192, journal first block 18, max trans len 1024, max batch 900, max commit
age 30, max trans age 30
Feb 23 21:57:12 servidor1 kernel: reiserfs: checking transaction log (dm-0)
for (dm-0)
Feb 23 21:57:12 servidor1 kernel: reiserfs: replayed 23 transactions in 1 seconds
Feb 23 21:57:12 servidor1 kernel: Using r5 hash to sort names
I want use new version v4 but I don't want to lost my data. are there any form
to convert my fs to a new version v4??? This files are not critical for the
system, only data..
Thanks for the time and for reiserfs...
=======================================================================================
Una partícula que vuela ... buscará el ojo mas próximo ...
=======================================================================================
next reply other threads:[~2004-02-24 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 17:30 Diaz Rodriguez, Eduardo [this message]
2004-02-24 17:50 ` Conversion from v3.6 to v4 of Reiserfs Dr. Giovanni A. Orlando
2004-02-25 2:25 ` Asheesh Laroia
2004-02-25 8:33 ` Christian Mayrhuber
2004-02-25 9:37 ` Hans Reiser
[not found] <no.id>
2004-02-25 1:54 ` The Amazing Dragon
2004-02-25 9:17 ` Nikita Danilov
2004-02-25 9:27 ` Dr. Giovanni A. Orlando
2004-02-25 9:36 ` Nikita Danilov
2004-02-25 10:02 ` Nikita Danilov
2004-02-25 11:14 ` 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=20040224172153.M90659@pk25.com \
--to=ediaz@pk25.com \
--cc=reiserfs-list@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.