LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Gerold Jury <gml@inode.at>
Cc: Sergey Vlasov <vsu@altlinux.ru>, Mike Galbraith <efault@gmx.de>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: extra bytes written to SATA DVD drive on kernel 2.6.23 till 2.6.24.2
Date: Fri, 07 Mar 2008 17:40:07 +0900	[thread overview]
Message-ID: <47D0FF67.8050503@gmail.com> (raw)
In-Reply-To: <200803011329.11315.gml@inode.at>

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

Hello,

Gerold Jury wrote:
> Yes it happens with the DVD+RW (testet with dd now) and with DVD+R
> 
> Thank you for the byte interpretation.
> Now I have a hint where to start with the debugging.

I've tried to reproduce the problem here but failed.  Can you please try
the test with the file generated with the attached program?  "genseqfile
524288 > testfile" will give you 1 meg testfile and it will give us
better idea how the data is getting corrupted.

Thanks.

-- 
tejun

[-- Attachment #2: genseqfile.c --]
[-- Type: text/x-csrc, Size: 170 bytes --]

#include <unistd.h>
#include <stdio.h>

int main(int argc, char **argv)
{
	unsigned int i;

	for (i = 0; i < atoi(argv[1]); i++)
		fwrite(&i, 2, 1, stdout);
	return 0;
}

  reply	other threads:[~2008-03-07  8:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 19:05 Gerold Jury
2008-02-25 23:32 ` Andrew Morton
2008-02-26 18:57   ` Gerold Jury
2008-02-28  7:30 ` Mike Galbraith
2008-02-29 21:59   ` Gerold Jury
2008-03-01 11:53     ` Sergey Vlasov
2008-03-01 12:29       ` Gerold Jury
2008-03-07  8:40         ` Tejun Heo [this message]
2008-03-07 19:09           ` Gerold Jury
2008-03-07 19:52             ` Frans Pop
2008-03-07 20:32               ` Frans Pop
2008-11-17  3:05               ` Tejun Heo
2008-11-17  8:18                 ` Frans Pop

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=47D0FF67.8050503@gmail.com \
    --to=htejun@gmail.com \
    --cc=efault@gmx.de \
    --cc=gml@inode.at \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vsu@altlinux.ru \
    --subject='Re: extra bytes written to SATA DVD drive on kernel 2.6.23 till 2.6.24.2' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).