mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Beneath <ishikodzume@beneath.plus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: EXT3: linux-2.4.21-pre5
Date: Mon, 3 Mar 2003 21:09:56 -0700	[thread overview]
Message-ID: <20030303210956.M1373@schatzie.adilger.int> (raw)
In-Reply-To: <20030304024714.647cc75d.ishikodzume@beneath.plus.com>; from ishikodzume@beneath.plus.com on Tue, Mar 04, 2003 at 02:47:14AM +0000

On Mar 04, 2003  02:47 +0000, Beneath wrote:
> All of a sudden, and not during any heavy disk writing sessions or
> anything, things seem to stop loading up. I.e. the system is still very
> much alive, just anything that requires disk access will hang. It's
> happened both times in X, and i was able to switch back to VT1, where
> the following error messages awaited me:
> (this is as much as i could write down)
> 
> Several of these two messages:
> EXT3-FS error (device ide0(3,2)) in ext3 reserve_inode_write: IO failure
> EXT3-FS error (device ide0(3,2)) in ext3_get_inode ... (this then
> scrolled off the screen before i could transcribe it)

So, could you check in /var/log/messages (or whatever) to see if you
have the original error?  It might not have been written to disk if the
error is on the /var filesystem.  If that is the case, is it possible
for you to set up a serial console or network syslog to capture the
full errors?

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2003-03-04  4:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04  2:47 Beneath
2003-03-04  4:09 ` Andreas Dilger [this message]
2003-03-04 23:32   ` Beneath

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=20030303210956.M1373@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=ishikodzume@beneath.plus.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®