From: Sean Plaice <splaice@gmail.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfs errors in dmesg output
Date: Wed, 14 Jul 2004 03:45:40 -0700 [thread overview]
Message-ID: <ae9bd76a04071403452dbe056b@mail.gmail.com> (raw)
In-Reply-To: <40E7C2BA.8050003@namesys.com>
On Sun, 04 Jul 2004 12:41:30 +0400, Vladimir V. Saveliev <vs@namesys.com> wrote:
> Sean Plaice wrote:
> >>>sd(8,6):journal-1777: buffer 109798 bad state !PREPARED !LOCKED !DIRTY
> >>> JDIRTY_WAIT
> >>>sd(8,6):journal-1777: buffer 185659 bad state !PREPARED !LOCKED !DIRTY
> >>> JDIRTY_WAIT
> >>>sd(8,6):journal-1777: buffer 208840 bad state !PREPARED !LOCKED !DIRTY
> >>> JDIRTY_WAIT
> >>>sd(8,6):journal-1777: buffer 300870 bad state !PREPARED !LOCKED !DIRTY
> >>> JDIRTY_WAIT
> >>>
> >>
> >>IIRC, sometime ago, there were some fixes for race conditions which
> >>might cause this. Chris, would you please confirm that?
> >
> >
> > If this is a race condition that is specific to the kernel I am
> > running could this lead to corruption or system instability?
> >
> Still waiting for Chris reply
>
>
I notived this thread sort of died, but the possible race condition is
still occuring. I have scheduled an outage window to upgrade the
kernel to the lastest Fedora Core distributed kernel release.
If the problem persists I will just build my own kernel from the
lastest 2.4.x vanilla tree. If the problem persists there I will
update this thread once again.
--
Sean
prev parent reply other threads:[~2004-07-14 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 12:22 reiserfs errors in dmesg output Sean Plaice
2004-07-03 12:53 ` Vladimir V. Saveliev
2004-07-03 23:10 ` Sean Plaice
2004-07-04 8:41 ` Vladimir V. Saveliev
2004-07-14 10:45 ` Sean Plaice [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=ae9bd76a04071403452dbe056b@mail.gmail.com \
--to=splaice@gmail.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.