From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Zygo Blaxell <eazgwmir@umail.furryterror.org>, reiserfs-list@namesys.com
Subject: Re: How to break a reiserfs on Linux 2.4.20
Date: 16 Jan 2003 10:29:03 -0500 [thread overview]
Message-ID: <1042730943.31095.2188.camel@tiny.suse.com> (raw)
In-Reply-To: <20030116182201.A28414@namesys.com>
On Thu, 2003-01-16 at 10:22, Oleg Drokin wrote:
> Hello!
>
> On Thu, Jan 16, 2003 at 09:16:11AM -0500, Zygo Blaxell wrote:
> > Oleg Drokin <green@namesys.com> wrote:
> > >Yes, we were able to reproduce the problem and now we are trying to fix it.
> > >Thanks a lot for your help and for the script.
> > Excellent! :-)
> > Just on a whim, I ran the tests on a different kernel image yesterday
> > and got some different results in the syslog:
> > Jan 15 18:26:00 berkelium kernel: journal-569: flush_commit_list, block already dirty!
>
> Hm, these are something new for me.
>
These aren't good at all, either the locking on the commit lists is
broken or the buffer head management is going wrong.
Oleg, do you have any leads or do you want me to try reproducing?
-chris
next prev parent reply other threads:[~2003-01-16 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 19:30 2.4.20, reiserfs, md linear, and "Permission denied" Zygo Blaxell
2003-01-14 0:37 ` Zygo Blaxell
2003-01-14 16:56 ` How to break a reiserfs on Linux 2.4.20 Zygo Blaxell
2003-01-14 17:05 ` Nikita Danilov
2003-01-14 19:04 ` Zygo Blaxell
2003-01-14 19:15 ` Nikita Danilov
2003-01-14 22:39 ` Zygo Blaxell
2003-01-15 22:44 ` Zygo Blaxell
2003-01-16 7:49 ` Oleg Drokin
2003-01-16 14:16 ` Zygo Blaxell
2003-01-16 15:22 ` Oleg Drokin
2003-01-16 15:29 ` Chris Mason [this message]
2003-01-16 15:32 ` Oleg Drokin
2003-01-17 20:13 ` Zygo Blaxell
2003-01-14 17:53 ` Oleg Drokin
2003-01-14 19:02 ` Zygo Blaxell
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=1042730943.31095.2188.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=eazgwmir@umail.furryterror.org \
--cc=green@namesys.com \
--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.