All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Dave Jones <davej@redhat.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible EXT2 race
Date: Fri, 07 Dec 2007 21:44:53 -0600	[thread overview]
Message-ID: <475A1335.1080708@shaw.ca> (raw)
In-Reply-To: <fa.KAMBv2HxgDHKEZW9BUNlO1zsYAg@ifi.uio.no>

linux-os (Dick Johnson) wrote:
> On Fri, 7 Dec 2007, Dave Jones wrote:
> 
>> On Fri, Dec 07, 2007 at 08:15:42AM -0500, linux-os (Dick Johnson) wrote:
>>
>>> Dec  7 04:05:55 chaos kernel: sd 0:0:1:0: [sdb] Add. Sense: Peripheral device write fault
>> This sounds more like a hardware problem.
>>
>> 	Dave
>>
> 
> There was an attempt to write beyond the end of the device because
> everything in the file-system was getting trashed. I can read/write
> the 5 year-old SCSI physical drive with no errors from both within
> linux and through the Adaptec BIOS. This problem only occurs
> when I attempt to truncate a file that is being written by another
> task.

That SCSI error code doesn't sound like a reasonable one for the drive 
getting a bad block address. The more typical one in that case would be 
"Logical block address out of range", or maybe the catch-all "Invalid 
field in CDB". "Peripheral device write fault", especially as a deferred 
error (i.e. after the drive already returned a normal completion for the 
data, and then is reporting the failure to actually write to the media 
on the next command), really sounds like a drive problem.

And the kernel is supposed to trap those at the disk layer, like these 
are saying it is, _after_ that error occurs:

Dec  7 04:08:13 chaos kernel: attempt to access beyond end of device
Dec  7 04:08:13 chaos kernel: sdb1: rw=0, want=29687515944, limit=33736437

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-12-08  3:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.GlQhcAEmKY+sQUhug9FU2RfqU7U@ifi.uio.no>
     [not found] ` <fa.drfDhE7MUuSb7VZP+2J0c3nmSCc@ifi.uio.no>
     [not found]   ` <fa.KAMBv2HxgDHKEZW9BUNlO1zsYAg@ifi.uio.no>
2007-12-08  3:44     ` Robert Hancock [this message]
2007-12-07 13:15 Possible EXT2 race linux-os (Dick Johnson)
2007-12-07 16:51 ` Dave Jones
2007-12-07 18:58   ` linux-os (Dick Johnson)
2007-12-08  8:57     ` Jon Masters

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=475A1335.1080708@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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.