From: "Samium Gromoff" <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: ReiserFS report
Date: Sun, 22 Jul 2001 17:01:14 +0400 [thread overview]
Message-ID: <E15OIrC-000HTk-00@f5.mail.ru> (raw)
Hello there,
Reporting about linux-2.4.4/3.x.0k-pre8
1. Wow! Actually 1st time i hadnt tail corruption
when again revived my partition with --rebuild-tree.
Good work!
2. Erm, --fix-non-critical says:
bla-bla-bla
there are 6 corruptions what can be fixed with
fix-fixable
bla-bla-bla...
i`m trying to be clever, and run --fix-fixable
AND: _it finds nothing offensive_!!!
ofcourse --fix-non-critical finds these
stale 6 errors..... quite disappointing :(
---
cheers,
Samium Gromoff
reply other threads:[~2001-07-22 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E15OIrC-000HTk-00@f5.mail.ru \
--to=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®