public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: Connection to SAN times out after a few days
Date: Thu, 19 May 2005 15:26:11 -0400	[thread overview]
Message-ID: <a728f9f90505191226655f26a1@mail.gmail.com> (raw)

I have Nexsan ATAbeast SAN connected to an AMD64 (sun v20z) and
SPARC64 (sun 220R) server using lpfc HBAs (using the in kernel lpfc
driver, kernel 2.6.12-rc4).  About once every 4-5 days, the server
loses its connection to the SAN and I get these messages in my log:
May 19 09:01:08 nutcracker scsi1 (0:0): rejecting I/O to offline device
May 19 09:01:08 nutcracker metapage_read_end_io: I/O error
May 19 09:01:08 nutcracker scsi1 (0:0): rejecting I/O to offline device
May 19 09:01:08 nutcracker metapage_read_end_io: I/O error
May 19 09:01:08 nutcracker ERROR: (device dm-4): DT_GETPAGE: dtree page corrupt
May 19 09:01:09 nutcracker scsi1 (0:0): rejecting I/O to offline device
May 19 09:01:09 nutcracker metapage_read_end_io: I/O error
May 19 09:01:09 nutcracker ERROR: (device dm-4): DT_GETPAGE: dtree page corrupt

Nothing unusual shows up in the SAN logs.  I've already adjusted the
cache flushing on the SAN and changed the scsi timeouts to 45 seconds.
 I asked emulex about it, but I'm wondering if this is something in
the scsi layer.  Has anyone else had similar problems or know what the
problem may be?

Thanks,

Alex

             reply	other threads:[~2005-05-19 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 19:26 Alex Deucher [this message]
2005-05-19 19:39 ` Connection to SAN times out after a few days Patrick Mansfield
2005-05-19 19:59   ` Alex Deucher
  -- strict thread matches above, loose matches on Subject: below --
2005-05-20 13:14 James.Smart

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=a728f9f90505191226655f26a1@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=linux-scsi@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