All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: penney@msu.edu
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	jfs-discussion@lists.sourceforge.net
Subject: Re: [Jfs-discussion] Re: Question about file system failure
Date: Mon, 27 Jun 2005 09:45:51 -0500	[thread overview]
Message-ID: <1119883552.9296.32.camel@localhost> (raw)
In-Reply-To: <1119883314.9271.29.camel@localhost>

On Mon, 2005-06-27 at 09:41 -0500, Dave Kleikamp wrote:
> On Mon, 2005-06-27 at 10:10 -0400, Chris Penney wrote:
> > I had an NFS file server using JFS fail this weekend.  A reboot, which
> > made fsck do a full check, seems to have cleared everything up.  The
> > initial errors I got were:
> > 
> > Jun 25 09:27:04 nicfs2 kernel: Incorrect number of segments after building list
> > Jun 25 09:27:04 nicfs2 kernel: counted 16, received 15
> > Jun 25 09:27:04 nicfs2 kernel: req nr_sec 320, cur_nr_sec 8
> 
> These are coming from scsi_init_io() in drivers/scsi/scsi_lib.c.  I
> don't know what it means, but I'm inclined to think that it indicates a
> software bug rather than a hardware error.
> 
> > Jun 25 09:27:04 nicfs2 kernel: device-mapper: dm-multipath: Failing path 8:96.
> > Jun 25 09:27:04 nicfs2 kernel: cfq: depth 4 reached, tagging now on
> > Jun 25 09:27:04 nicfs2 kernel: end_request: I/O error, dev sdc, sector
> > 1592060824
> > Jun 25 09:27:04 nicfs2 kernel: device-mapper: dm-multipath: Failing path 8:32.
> > Jun 25 09:27:04 nicfs2 kernel: end_request: I/O error, dev sdc, sector
> > 1592062936
> 
> I'm not sure if dm-multipath may be responsible.
> 
> > Following that was a flurry of JFS errors.  I assume these messages
> > have nothing at all to do with JFS, but I wanted to make certain.
> 
> I don't think that JFS is the cause.
> 
> > I can't turn up much googling that error.  If anyone has any idea what
> > caused that I'd love to hear it.
> 
> I'm copying this to linux-kernel in the hopes that someone there will be
> able to help.  It would be useful to know what kernel you are running.

Well, I meant to cc linux-kernel.  :-)

> > One last question, for an NFS server is it better to mount the volume
> > with errors=panic?  It seems like that would keep I/Os from failing
> > due to it being a read-only file system on error.  In this case it
> > would seem like a panic + boot would have let a lot of processes (this
> > is used in a batch environment) resume.
> 
> Seems reasonable, but I'll let others comment.
> 
> >    Chris
> 
> Thanks,
> Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


       reply	other threads:[~2005-06-27 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <111aefd05062707103d24f568@mail.gmail.com>
     [not found] ` <1119883314.9271.29.camel@localhost>
2005-06-27 14:45   ` Dave Kleikamp [this message]
2005-06-27 15:10     ` [Jfs-discussion] Re: Question about file system failure Chris Penney

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=1119883552.9296.32.camel@localhost \
    --to=shaggy@austin.ibm.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penney@msu.edu \
    /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.