From: Oleg Drokin <green@namesys.com>
To: reiserfs-list@namesys.com
Cc: phoner.reiserfs@blah.pl
Subject: Re: kernel BUG at prints.c:334
Date: Mon, 6 Jan 2003 10:11:49 +0300 [thread overview]
Message-ID: <20030106101149.B1881@namesys.com> (raw)
In-Reply-To: <hhr8bv7cm6.fsf@blah.pl>
Hello!
On Thu, Jan 02, 2003 at 05:14:25PM +0100, Maciej Matysiak wrote:
> reiserfs went mad on one of my machines. it's debian woody, with 2.4.20 kernel.
> in system logs i can see:
Logs you just provided show that your harddrive cannot remember what it was
supposed to store anymore.
> Jan 1 11:00:29 brzydal kernel: I/O error: dev 08:21, sector 65704
> Jan 1 11:00:29 brzydal kernel: zam-7001: io error in reiserfs_find_entry
> Jan 1 11:00:29 brzydal kernel: I/O error: dev 08:21, sector 65704
> Jan 1 11:00:29 brzydal kernel: zam-7001: io error in reiserfs_find_entry
See these IO errors? It cannot read the data off the HDD (/dev/sdc1).
> i've just tried to unmount the device. umount segfaulted, but the device is
> no longer mounted. in logs i can see:
Yes, reiserfs is not very well prepared to I/O errors while writing to journal,
hence it panicked.
> reiserfsck can't do anything:
No wonder, it cannot read anything off the disk either.
May be if you reboot or just keep the box off for some time and drive will
return to somewhat normal state, you will be able to
read something off it, but may be not. You will not know
for sure until you try.
> it's brand new, just 3 weeks ago installed. it's attached to:
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
> <Adaptec 2940B Ultra2 SCSI adapter>
> aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
> what's wrong (disk or kernel?) and what can with this problem?
Try to reboot (halt, switch the box off, then turn it back on to be sure),
if everything will appear normal, then the problem is with
controller or aic7xxx driver most probably.
If the drive is still inaccessible, then the drive is bad.
> i'm a bit afraid to reboot the machine at the moment.
Since the disk cannot be read anymore, you have no much other choices I afraid.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-06 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 16:14 kernel BUG at prints.c:334 Maciej Matysiak
2003-01-06 7:11 ` Oleg Drokin [this message]
2003-01-06 7:36 ` Maciej Matysiak
2003-01-06 7:44 ` Oleg Drokin
2003-01-06 9:23 ` Maciej Matysiak
2003-01-06 8:42 ` Hans Reiser
2003-01-06 17:02 ` Valdis.Kletnieks
2003-01-10 17:07 ` Any paper on Journaling algorithm? bmoon
2003-01-13 15:53 ` Hans Reiser
[not found] ` <3E22ECF0.9050605@emageon.com>
2003-01-13 18:57 ` Hans Reiser
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=20030106101149.B1881@namesys.com \
--to=green@namesys.com \
--cc=phoner.reiserfs@blah.pl \
--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.