From: Oleg Drokin <green@namesys.com>
To: Zygo Blaxell <eazgwmir@umail.furryterror.org>
Cc: reiserfs-list@namesys.com
Subject: Re: About direntries pointing to nowhere on reiserfs problem in 2.4
Date: Fri, 28 Feb 2003 10:46:51 +0300 [thread overview]
Message-ID: <20030228104651.A1234@namesys.com> (raw)
In-Reply-To: <b3mnpd$1ho$1@satsuki.furryterror.org>
Hello!
On Thu, Feb 27, 2003 at 11:15:41PM -0500, Zygo Blaxell wrote:
> OK, I did the following:
> patch kernel
> install patched kernel
> umount filesystem
> reiserfsck 3.6.5-pre1 --fix-fixable the filesystem
> forgot to note the last few things reiserfsck said
Ideally, resiserfsck should have told you wwhenever there were any
unfixed corruptions left.
> reboot machine
> verify that patched kernel is running
> wait a few days
> read "unlink: Permission denied" in logs
> I'm wondering if I'm still seeing the bug, or just the lingering
> after-effects of the bug that might still be hiding in the filesystem.
Hard to tell. But it well might be a hiding bugs.
--fix-fixable does not correct link counts, so if you have
file with nlinks=3 and 4 hardlinks to it, you are in trouble after
three of the hardlinks are removed.
> Is fix-fixable able to correct link counts? If not, presumably I need
No. It may only delete entries pointing to nowhere, I think.
> to do a full rebuild-tree in order to correct any incorrect link counts
> that may still be present on the filesystem?
Probably yes.
Bye,
Oleg
prev parent reply other threads:[~2003-02-28 7:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 14:53 About direntries pointing to nowhere on reiserfs problem in 2.4 Oleg Drokin
2003-02-21 7:11 ` Manuel Krause
2003-02-21 7:14 ` Oleg Drokin
[not found] ` <20030220154924.7171cbd7.akpm@digeo.com>
2003-02-21 19:03 ` 2.4 iget5_locked port attempt to 2.4 Oleg Drokin
2003-02-21 20:04 ` Jan Harkes
2003-02-22 9:29 ` Oleg Drokin
2003-02-24 10:21 ` 2.4 iget5_locked port attempt to 2.4 (supposedly fixed NFS version this time) Oleg Drokin
2003-02-24 16:50 ` Trond Myklebust
2003-02-24 17:02 ` Trond Myklebust
2003-02-24 17:03 ` Oleg Drokin
2003-02-24 17:17 ` Trond Myklebust
2003-02-24 17:26 ` Oleg Drokin
2003-02-24 17:33 ` Trond Myklebust
2003-02-24 17:38 ` Oleg Drokin
2003-03-03 14:09 ` 2.4 iget5_locked port attempt to 2.4 Oleg Drokin
2003-03-03 16:25 ` Alan Cox
2003-03-03 15:35 ` Nikita Danilov
2003-03-03 15:38 ` Oleg Drokin
2003-03-03 15:57 ` Anton Altaparmakov
2003-03-03 16:04 ` Oleg Drokin
2003-03-03 16:27 ` Anton Altaparmakov
2003-03-03 16:45 ` Oleg Drokin
2003-03-03 16:50 ` Jan Harkes
2003-03-03 16:57 ` Oleg Drokin
2003-03-03 17:23 ` Jan Harkes
2003-02-24 17:49 ` About direntries pointing to nowhere on reiserfs problem in 2.4 Zygo Blaxell
2003-02-24 18:59 ` Vitaly Fertman
2003-02-25 3:45 ` Zygo Blaxell
2003-02-25 12:39 ` Vitaly Fertman
2003-02-25 18:11 ` Zygo Blaxell
2003-02-25 19:35 ` Vitaly Fertman
2003-02-25 7:04 ` Oleg Drokin
2003-02-25 12:01 ` Hans Reiser
2003-02-25 12:31 ` Oleg Drokin
2003-02-28 4:15 ` Zygo Blaxell
2003-02-28 7:46 ` Oleg Drokin [this message]
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=20030228104651.A1234@namesys.com \
--to=green@namesys.com \
--cc=eazgwmir@umail.furryterror.org \
--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.