mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Caputo <ccaputo@alt.net>
To: erich <erich@areca.com.tw>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: about ll_rw_blk.c of void generic_make_request(struct bio *bio)
Date: Thu, 6 Apr 2006 11:44:38 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0604060953000.13282@nacho.alt.net> (raw)
In-Reply-To: <026001c6595c$f6c5a890$b100a8c0@erich2003>

On Thu, 6 Apr 2006, erich wrote:
> I am so sorry that I reply this mail today.
> At 2006/4/3 my mother unexpectedly got paralysis and dead.
> I can not do any more "request testing" with this bug for some days.
> I do dump_stack as your request and attach it.
> And I do "fsck" before test this volume every time.
> It appears fine when do fsck with each testing volume.
> You can easily reproduce this bug from copy a 900MB file from ARECA volume
> (mkfs.ext2, mount -t ext2) to none ARECA volume.

Erich, my sincere condolences to you and your family.

With respect to this problem, is it possible with your driver that if a 
transfer read request is above a certain size, data corruption occurs?

It may be that fsck passes because it is doing smaller transfers while a 
file copy under ext2 (or in your example, ext3) fails because it is during 
those operations that the higher max_sectors makes a difference.

Curiously, the hex values of the "want=" field in your report are as 
follows:

  sdb1: rw=0, want=12126966488, limit=312496317
  2D2D2D2D8
  sdb1: rw=0, want=12126967088, limit=312496317
  2D2D2D530
  sdb1: rw=0, want=22232771288, limit=312496317
  52D2D2AD8
  sdb1: rw=0, want=22232771888, limit=312496317
  52D2D2D30

I wonder if 0x2D or 0xD2 corresponds to something on the disk such as in 
the file being copied or is otherwise familiar.

Chris

  reply	other threads:[~2006-04-06 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29  7:26 erich
2006-03-30 15:58 ` Jens Axboe
2006-03-31 17:32   ` Chris Caputo
2006-03-31 18:09     ` Chris Caputo
2006-03-31 20:22       ` Jens Axboe
2006-03-31 20:37         ` Chris Caputo
2006-04-06  9:32           ` erich
2006-04-06 11:44             ` Chris Caputo [this message]
2006-04-06 12:27               ` erich

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=Pine.LNX.4.64.0604060953000.13282@nacho.alt.net \
    --to=ccaputo@alt.net \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=erich@areca.com.tw \
    --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®