From: Chris Mason <mason@suse.com>
To: Arnaud Installe <a.installe@ieee.org>, linux-kernel@vger.kernel.org
Subject: Re: reiserfs probs on 2.2.17
Date: Tue, 20 Feb 2001 19:53:01 -0500 [thread overview]
Message-ID: <1940350000.982716781@tiny> (raw)
In-Reply-To: <20010221014410.A2559@bach.iverlek.kotnet.org>
On Wednesday, February 21, 2001 01:44:10 AM +0100 Arnaud Installe
<arnaud@bach.kotnet.org> wrote:
> Hello,
>
> I've had a problem with a reiserfs partition on a 2.2.17 kernel the other
> day. Everything I did on it just waited forever. (Since shutdown tries
> to umount all partitions the only way to reboot the machine was to kill
> the watchdog process.)
>
> The problem persisted after the reboot, so the partition must've contained
> errors. Running `reiserfsck --replay-by-journal' fixed the problem. (I
> think: before that I also ran `reiserfsck --check 'on it.)
>
Which reiserfs version are you running? From the ps output, it looks like
you've got a bunch of processes waiting on the log, and one process waiting
on a semaphore, so everyone is probably waiting for that process to close
the transaction. These kinds of deadlocks should have been long since
fixed, so there is probably a larger problem.
Running reiserfsck --replay-journal will replay the journal. This happens
on every mount, so I'm really not sure how it could have fixed things ;-)
The --check option is readonly, and if there was a metadata problem it
probably would have reported it.
-chris
prev parent reply other threads:[~2001-02-21 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 0:44 reiserfs probs on 2.2.17 Arnaud Installe
2001-02-21 0:53 ` Chris Mason [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=1940350000.982716781@tiny \
--to=mason@suse.com \
--cc=a.installe@ieee.org \
--cc=linux-kernel@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.