From: Nikita Danilov <Nikita@Namesys.COM>
To: "Weiping He" <laser@zhengmai.com.cn>
Cc: "Oleg Drokin" <green@Namesys.COM>, <linux-kernel@vger.kernel.org>,
<reiserfs-list@Namesys.COM>
Subject: Re: anybody know about "journal-615" and/or "journal-601" log error?(may be SCSI problem?)
Date: Thu, 10 Jan 2002 13:21:42 +0300 [thread overview]
Message-ID: <15421.27446.227873.475829@laputa.namesys.com> (raw)
In-Reply-To: <003b01c1997c$4a86fec0$d20101c0@T21laser>
In-Reply-To: <005401c18dc6$f3e3fb10$d20101c0@T21laser> <20011226094209.B871@namesys.com> <003b01c1997c$4a86fec0$d20101c0@T21laser>
journal-601 means that writing of the block into the journal area failed.
journal-615 means that writing of the commit record into the journal area failed.
Reiserfs cannot work reliably if there are io errors on access to
journal area. So, if this is turns out to be hardware problem (as it
looks to be, judging by scsi error messages), you will have to resort to
changing drive. There is also not well tested support for relocating
journal to another device or different place on a device.
Weiping He writes:
> Hi,
>
> I've experienced another crash this morning.
> I'v recorded the message displayed on the screen:
>
> -------------------------------------8<------------------------------------------------
> journal-601, buffer write failed
Nikita.
prev parent reply other threads:[~2002-01-10 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 4:36 anybody know about "journal-615" and/or "journal-601" log error? Weiping He
2001-12-26 6:42 ` Oleg Drokin
2001-12-26 8:38 ` Weiping He
2002-01-10 2:11 ` anybody know about "journal-615" and/or "journal-601" log error?(may be SCSI problem?) Weiping He
2002-01-10 10:21 ` Nikita Danilov [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=15421.27446.227873.475829@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=green@Namesys.COM \
--cc=laser@zhengmai.com.cn \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®