From: Vitaly Fertman <vitaly@namesys.com>
To: reiserfs-list@namesys.com
Subject: http://www.namesys.com/snapshots/2004.08.09-internal.testing/
Date: Mon, 9 Aug 2004 23:49:31 +0400 [thread overview]
Message-ID: <200408092349.31231.vitaly@namesys.com> (raw)
In-Reply-To: <411158A3.1060707@namesys.com>
Hello All,
This snapshot contains what was included into 2004.08.03-internal.testing
snapshot:
> updated reiser4progs-0.5.7 and the grub patch.
>
> It includes several bug fixes against the previous snapshot, and has a disk
> format change -- the layout of blocks that contain backuped fs metadata
> are changed.
>
> No kernel patch is needed for the disk format change, however fsck may
> report about some corruptions on an existent fs if a block was allocated
> for some data and has become a backup one. Fsck.reiser4 --build-fs is
> able to fix it of course, although the data in these blocks are lost then.
and it has a converter from the previous format to the new one -- if you
already created a reiser4 fs with the mkfs from some previous version
of reiser4progs, first of all run
$ debugfs.reiser4 -C device
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2004-08-09 19:49 UTC|newest]
Thread overview: 36+ 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 ` http://www.namesys.com/snapshots/2004.08.03-internal.testing/ Hans Reiser
2004-08-09 19:49 ` Vitaly Fertman [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 19:55 http://www.namesys.com/snapshots/2004.08.09-internal.testing/ Vitaly Fertman
[not found] ` <e796392204080913384ac39553@mail.gmail.com>
2004-08-09 21:01 ` http://www.namesys.com/snapshots/2004.08.09-internal.testing/ Stefan Schweizer
2004-08-09 21:21 ` http://www.namesys.com/snapshots/2004.08.09-internal.testing/ Vitaly Fertman
[not found] ` <200408100057.57087.vitaly@namesys.com>
2004-08-09 21:18 ` http://www.namesys.com/snapshots/2004.08.09-internal.testing/ Stefan Schweizer
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=200408092349.31231.vitaly@namesys.com \
--to=vitaly@namesys.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.