From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: "Markus Törnqvist" <mjt@nysv.org>,
"Thomas Graham" <lkthomas@sml.dyndns.org>,
"Chris Mason" <mason@suse.com>,
reiserfs-list@namesys.com
Subject: Re: http://www.namesys.com/snapshots/2004.08.03-internal.testing/
Date: Wed, 04 Aug 2004 14:44:03 -0700 [thread overview]
Message-ID: <411158A3.1060707@namesys.com> (raw)
In-Reply-To: <200408042251.41149.vitaly@namesys.com>
Vitaly Fertman wrote:
>On Wednesday 04 August 2004 21:47, Hans Reiser wrote:
>
>
>>Markus TЖrnqvist wrote:
>>
>>
>>>On Wed, Aug 04, 2004 at 10:16:26PM +0800, Thomas Graham wrote:
>>>
>>>
>>>>if a convertor are not done yet, I think we could wait until it's bundle
>>>>into the .tar.gz and we could use it, actually, do we HAVE TO do that
>>>>format changes ? or normal user could just ignore that except for some of
>>>>them who reach problem with that ?
>>>>
>>>>
>>>I don't think you HAVE to do it, if you would, there would be a
>>>compensation in the kernel, and Vitaly said there is not.
>>>
>>>So just avoid the reiser4progs like the plague, call the Namesys helpdesk,
>>>whatever and ask Vitaly to remove the file from the web, remove the
>>>code that changes the format, whatever.
>>>
>>>I just hope I won't hit a corruptive bug on my machine, it would be pretty
>>>anticlimactic if I did and I would lose data because it decides to
>>>change the format.
>>>
>>>
>>I don't understand why Vitaly cannot do one of the things suggested on
>>this thread: create an fsck option for people like Markus to use.
>>
>>If Vitaly does that, problem solved, yes?
>>
>>Chris is right that any disk format changes need to be made now.
>>Vitaly, send an email defining what you propose to do, and cc the list.
>>Do that now please.
>>
>>
>
>I have written a converter (an option to debugfs), testing it,
>it does well for the last half an hout already.
>
>I am going to release another internal snapshot with the explanation
>in README how to use it.
>
>
>
good answer.
next prev parent reply other threads:[~2004-08-04 21:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 20:22 http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-06-14 21:05 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ mjt
2004-06-14 21:27 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-06-16 11:58 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-06-16 15:44 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Sander Sweers
2004-06-16 16:08 ` http://www.namesys.com/snapshots/2004.06.14-internal.testing/ Vitaly Fertman
2004-07-13 10:27 ` http://www.namesys.com/snapshots/2004.07.13-internal.testing/ Vitaly Fertman
2004-07-13 10:54 ` [PATCH] http://www.namesys.com/snapshots/2004.07.13-internal.testing/ Philippe Gramoullé
2004-07-13 12:06 ` Vitaly Fertman
2004-08-03 13:50 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-03 13:58 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-03 14:19 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 8:51 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-04 9:55 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 10:34 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 10:52 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 12:49 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 12:56 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 12:41 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Philippe Gramoullé
2004-08-04 12:50 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 13:49 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Chris Mason
2004-08-04 14:16 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Thomas Graham
2004-08-04 14:22 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 17:47 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-04 18:21 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
2004-08-04 18:51 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 21:44 ` Hans Reiser [this message]
2004-08-09 19:49 ` http://www.namesys.com/snapshots/2004.08.09-internal.testing/ Vitaly Fertman
2004-08-04 3:33 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Thomas Graham
2004-08-04 8:44 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-04 10:16 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Vitaly Fertman
2004-08-04 10:28 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ mjt
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=411158A3.1060707@namesys.com \
--to=reiser@namesys.com \
--cc=lkthomas@sml.dyndns.org \
--cc=mason@suse.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.