From: mjt@nysv.org
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com, sikkh@wp.pl
Subject: Re: Tree issues, fsck output
Date: Wed, 30 Jun 2004 12:42:25 +0300 [thread overview]
Message-ID: <20040630094225.GN4990@nysv.org> (raw)
In-Reply-To: <200406301324.34713.vitaly@namesys.com>
On Wed, Jun 30, 2004 at 01:24:34PM +0400, Vitaly Fertman wrote:
>it prints all found corruptions. could you send them ?
The thing is, now that 2.6.7-mm4, latest auto-snapshot, failed,
I didn't get any errors with fsck... So it seems my filesystem
is all alright, at least for the time being.
>btw, I hvae already added gauge to the semantic pass. Hopefully will
>release another progs snapshot or internal-snapshot on days.
That would be great!
Any hints on what else to expect beyond the gauge?-)
>if I recall correctly the only corruption was wrong directory entry, right?
>or it fould some more while you were sleeping?
Nope, nada, the last I pasted to you, libmp4, was also the last failure.
Then I think I posted here that xmms wouldn't reinstall and there were
bad ELF headers.
>could you run fsck.reiser4 in check mode again after rebuilding to be sure
>that evth has been fixed. If you have matadata packed before rebuilding,
>not after, and you can provide them for downloading, it would be useful.
I'm taking a debugfs.reiser4 -P /dev/hda1 now.
Then I will run additional stuff, but it still seems like the FS is ok....
>> If the semantic tree pass goes cleanly and the fs is consistent, I will
>> try older auto-snapshots, despite the fact that the earlier mm's are
>> not highly recommended.
>to reproduce this we need to know which steps lead to such corruptions.
Yeah, but it ain't easy.
I'd like to hear what changes were made when porting the snapshot
to mainline. If that could possibly induce corruption.
Anyway, I think this part of the discussion is redundant, as the big
problem now remaining is that the 2004.06.29 auto-snapshot doesn't
boot. If it presents these problems, with sibling check and all that
enabled, I will have more details for you.
--
mjt
next prev parent reply other threads:[~2004-06-30 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 20:19 Tree issues, fsck output mjt
2004-06-30 6:45 ` mjt
2004-06-30 9:03 ` mjt
2004-06-30 9:24 ` Vitaly Fertman
2004-06-30 9:42 ` mjt [this message]
2004-06-30 10:43 ` 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=20040630094225.GN4990@nysv.org \
--to=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=sikkh@wp.pl \
--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.