From: Eric Sandeen <sandeen@sandeen.net>
To: pgf111000 <junkmail@petergfrazier.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: I/O error, SCSI error, reservation conflict.... xfs suggestions?
Date: Fri, 23 Feb 2007 13:33:03 -0600 [thread overview]
Message-ID: <45DF416F.5050907@sandeen.net> (raw)
In-Reply-To: <9124908.post@talk.nabble.com>
pgf111000 wrote:
> In the middle of read/write operations on the xfs formatted areca array I
> experience the following repetative message (from /var/log/messages):
>
> sd 3:0:1:0: reservation conflict
> sd 3:0:1:0: SCSI error: return code = 0x00070018
> end_request: I/O error, dev sdx, sector 681896097
...
> Any and all thoughts/suggestions will be warmly received....
Well, this isn't an xfs problem. Something is happening at the scsi
layer, whatever xfs does after that is simply reacting (properly) to it.
I'd try another list... :)
-Eric
next prev parent reply other threads:[~2007-02-23 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 19:13 I/O error, SCSI error, reservation conflict.... xfs suggestions? pgf111000
2007-02-23 19:33 ` Eric Sandeen [this message]
2007-02-23 19:41 ` Chris Wedgwood
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=45DF416F.5050907@sandeen.net \
--to=sandeen@sandeen.net \
--cc=junkmail@petergfrazier.com \
--cc=linux-xfs@oss.sgi.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