From: Roman I Khimov <rik@osrc.info>
To: reiserfs-list@namesys.com
Cc: Jake Maciejewski <maciejej@msoe.edu>
Subject: Re: Reiser4 corruption (fsck.reiser4 broken?)
Date: Wed, 25 Jan 2006 00:28:10 +0300 [thread overview]
Message-ID: <200601250028.13857.rik@osrc.info> (raw)
In-Reply-To: <1138135840.29441.124.camel@gentoo>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
24 января 2006 23:50 | Jake Maciejewski:
> Someone correct me if I'm wrong, but kernels since 2.6.11-5 have the new
> plugin set which isn't supported by reiser4progs 1.0.4, so fscking with
> 1.0.4 was probably a big mistake.
I'm looking at Reiser4progs Changelog, this line:
Handle new (crc related) fields in plugin set correctly.
from 2005-06-28 (post 1.0.4 changes) looks interesting. Seems that I'm not
so good at following reiserfs-list, because I knew about changes, but
somehow forgot to upgrade to 1.0.5 (and I can even remember why - at the
time it was released I wasn't using Reiser4, only looking at it from safe
Reiser3 /home, that was converted to Reiser4 in November). Cool... When
will I finally learn to be careful? ;-)
Sorry for the noise...
--
Roman
,---------------------------. ,--------------------------.
/ http://www.3os.ru/ V http://www.osrc.info/ \ .o.
\ mailto: rik@3os.ru ^ mailto: rik@osrc.info / ..o
`---------------------------' `--------------------------' ooo
gpg --recv-keys 0xE5E055C3 --keyserver hkp://subkeys.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-24 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 19:57 Reiser4 corruption (fsck.reiser4 broken?) Roman I Khimov
2006-01-24 20:23 ` Hans Reiser
2006-01-24 20:48 ` Roman I Khimov
2006-01-24 20:50 ` Jake Maciejewski
2006-01-24 21:08 ` Hans Reiser
2006-01-24 21:28 ` Roman I Khimov [this message]
2006-01-24 21:42 ` Boyd Waters
2006-01-25 0:25 ` Barry K. Nathan
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=200601250028.13857.rik@osrc.info \
--to=rik@osrc.info \
--cc=maciejej@msoe.edu \
--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.