All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin <newsbox1026@web.de>
To: reiserfs-devel@vger.kernel.org
Subject: Reiser4 on 2.6.31.4 freezes process accessing file, fsck 1.0.7 finds no inconsistency
Date: Mon, 19 Oct 2009 00:10:10 +0200	[thread overview]
Message-ID: <4ADB9242.30808@web.de> (raw)

Hi!

I am running reiser4 for a few years now without problems. Yesterday I
had an undeletable directory which ls -a reported empty but rmdir
claimed not to be empty. There were no kernel messages about it. After
fsck-ing I had to run fsck.reiser4 --build-fs (reiser4progs 1.0.7) which
finished but printed an error at the very end like "application error"
(sorry, I didn't wrote it down). A second run of fsck.reiser4 told me to
fix some remaining corruptions using --fix. This worked without error
messages and a following fsck told me everything is OK.

But then accessing a file froze the process, consuming 100% CPU. I tried
cat and cp with same result. The processes could not be terminated nor
killed. Still no kernel messages. Only rebooting helped here and a
following fsck showed no corruptions. The file could be renamed and
deleted which kind of solved the problem. I haven't found (yet) another
file like this.

Before deleting the bad file I did a debugfs.reiser4 -P to store the
metadata so if anyone is interested in debugging this bug contact me to
give you the file (34MB bz2).

Konstantin


             reply	other threads:[~2009-10-18 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 22:10 Konstantin [this message]
2009-10-19 23:07 ` Reiser4 on 2.6.31.4 freezes process accessing file, fsck 1.0.7 finds no inconsistency Edward Shishkin

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=4ADB9242.30808@web.de \
    --to=newsbox1026@web.de \
    --cc=reiserfs-devel@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 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.