All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Fertman <vitaly@namesys.com>
To: Fionn Behrens <fionn@unix-ag.org>, reiserfs-list@namesys.com
Subject: Re: Re: Strange Syslog messages - this is NOT an isolated case!
Date: Mon, 30 Sep 2002 15:23:16 +0400	[thread overview]
Message-ID: <200209301523.16500.vitaly@namesys.com> (raw)
In-Reply-To: <20020930125753.5d05d7ea.fionn@unix-ag.org>

> Having gotten curious, I did a ls -lR on the drive and uncovered about a
> dozen similar problems outside /lost+found. I have not yet changed anything
> on the drive and hope you can give me some advice as I consider this a
> SERIOUS problem (wheter my data is in danger or not, problems should be
> found by an fsck). As a satiric sidenote, there are messages appearing in
> the syslog, suggesting an fsck. But fsck wont find a problem.
>
> So, bottom line:
> * The drive is pretty new. badblocks does NOT find anything. In fact it ran
>   flawlessly until I rebuilt the tree.
> * reiserfsck --fix-fixable claims there are NO errors.
> * I have 2.4.19, too
> * I am using reiserfsprogs 3.6.3 from the Debian
>   reiserfsprogs 3.6.3-1 package.

It looks like a known bug which was fixed in last pre releases. Would you try
reiserfsprogs-3.6.4-pre2 and tell us about the result?

-- 

Thanks,
Vitaly Fertman

      parent reply	other threads:[~2002-09-30 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 10:57 Strange Syslog messages - this is NOT an isolated case! Fionn Behrens
2002-09-30 11:09 ` Oleg Drokin
2002-09-30 13:56   ` Fionn Behrens
2002-09-30 14:22     ` Oleg Drokin
2002-09-30 11:23 ` Vitaly Fertman [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=200209301523.16500.vitaly@namesys.com \
    --to=vitaly@namesys.com \
    --cc=fionn@unix-ag.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.