From: mross@rs-net.org
To: Edward Shishkin <edward@namesys.com>
Cc: reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>
Subject: Re: reiser4 corruption
Date: Fri, 17 Jun 2005 13:50:52 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0506171348350.6542@localhost> (raw)
In-Reply-To: <42B30380.90606@namesys.com>
> What patch set did you apply? If this is the last one (reiser4-for-2.6.11-5)
> there is some inconsistency due to format changes
> that will be fixed in the next release.
Yes, it was reiser4-for-2.6.11-5. Would this inconsistency cause fsck to
find problems that just didn't exist? Would fsck's attempt to "fix" this
problem be harmful?
Thanks,
-Ross
next prev parent reply other threads:[~2005-06-17 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 15:26 reiser4 corruption mross
2005-06-17 17:08 ` Edward Shishkin
2005-06-17 17:50 ` mross [this message]
2005-06-20 10:35 ` Vladimir Saveliev
-- strict thread matches above, loose matches on Subject: below --
2014-10-31 16:37 Reiser4 corruption dE
2014-10-31 17:26 ` Edward Shishkin
2014-11-01 11:16 ` dE
2014-11-01 12:47 ` Edward Shishkin
2014-11-01 16:05 ` dE
2005-05-18 22:12 Reiser4 Corruption Craig Shelley
2004-09-04 18:07 reiser4 corruption Grzegorz Jaśkiewicz
2004-09-04 18:08 ` Grzegorz Jaśkiewicz
2004-09-04 18:23 ` Vince
2004-09-04 18:34 ` Grzegorz Jaśkiewicz
2004-05-22 19:36 dave
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=Pine.LNX.4.60.0506171348350.6542@localhost \
--to=mross@rs-net.org \
--cc=edward@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).