From: Oleg Drokin <green@namesys.com>
To: Jussi Vainionp?? <jjvainio@cc.hut.fi>
Cc: reiserfs-list@namesys.com
Subject: Re: Journal-601 error on Redhat 7.3 / reiserfs / ext3 / raid 5
Date: Thu, 3 Jul 2003 10:53:48 +0400 [thread overview]
Message-ID: <20030703065348.GD8358@namesys.com> (raw)
In-Reply-To: <3F035930.9050701@cc.hut.fi>
Hello!
On Thu, Jul 03, 2003 at 01:14:08AM +0300, Jussi Vainionp?? wrote:
> >>Apr 27 20:18:06 un kernel: journal-601, buffer write failed
> >I do not know who to blame here. Try to heavily write to loop device
> >itself (without using
> >reiserfs) to see if something will break? Or bettr yet - upgrade to newer
> >kernel and see if that's
> >cures your problem?
> I tried the same operation using ext2 instead of reiserfs and at least that
> worked without any problems.
ext2 does not wait on buffers unless you operate in sync mode, so it won't notice.
Try the ext2 with -o sync then?
Bye,
Oleg
next prev parent reply other threads:[~2003-07-03 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 21:52 Journal-601 error on Redhat 7.3 / reiserfs / ext3 / raid 5 Jussi Vainionpää
2003-07-01 5:43 ` Oleg Drokin
2003-07-02 22:14 ` Jussi Vainionpää
2003-07-03 6:53 ` Oleg Drokin [this message]
2003-07-09 19:31 ` Jussi Vainionpää
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=20030703065348.GD8358@namesys.com \
--to=green@namesys.com \
--cc=jjvainio@cc.hut.fi \
--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.