All of lore.kernel.org
 help / color / mirror / Atom feed
From: frbiscani@jumpy.it
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Michael Weissenbacher <webmaster@dermichi.com>,
	ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser4 - Non-removable files in lost+found
Date: Mon, 18 Oct 2004 15:50:33 +0200	[thread overview]
Message-ID: <40FC740900080188@mail13.jumpyint.it> (raw)

Sorry for the mail-mess... I hate webmail :/

On Friday 15 October 2004 14:29, Vitaly Fertman wrote:
> On Friday 15 October 2004 12:07, Michael Weissenbacher wrote:
> >
> > had the same problem, it is related to fsck which computes hashes the
> > wrong way if filenames are too long (and/or contain non-ascii
> > characters). vladimir sent a patch to the mailing list that corrected
> > this bug for me. not sure if this is already available in the
> > pre-version of reiser4progs.
>
> yes, the fix is included into reiser4progs-1.0.2-pre1.

Thank you all for the feedback. I installed reiser4progs-1.0.2-pre1 and
it
found the same number of corruptions as the number of undeletable files

in /lost+found. Should I run fsck with --build-fs then? Also, can this be

done when the partition is mounted read-only? I'm asking this because I
have to run reiser4progs from a chrooted environment where my / partition
is mounted read-only.

Thanks again,

  Francesco

________________________________________
Crea la tshirt con il tuo nick! http://www.mediasetshop.it/JumpyChat/



             reply	other threads:[~2004-10-18 13:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18 13:50 frbiscani [this message]
2004-10-18 16:30 ` reiser4 - Non-removable files in lost+found Michael Weissenbacher
2004-10-18 16:41 ` Adrian Ulrich
2004-10-18 16:33   ` E.Gryaznova
  -- strict thread matches above, loose matches on Subject: below --
2004-10-14 17:08 frbiscani
2004-10-14 18:42 ` Vitaly Fertman
2004-10-15  8:07 ` Michael Weissenbacher
2004-10-15  8:11   ` Michael Weissenbacher
2004-10-15 12:29   ` Vitaly Fertman

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=40FC740900080188@mail13.jumpyint.it \
    --to=frbiscani@jumpy.it \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@namesys.com \
    --cc=webmaster@dermichi.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.