From: Adam Kropelin <akropel1@rochester.rr.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.46: ide-cd cdrecord (almost) success report
Date: Wed, 6 Nov 2002 10:56:56 -0500 [thread overview]
Message-ID: <20021106155656.GA20403@www.kroptech.com> (raw)
In-Reply-To: <20021106072223.GB4369@suse.de>
On Wed, Nov 06, 2002 at 08:22:23AM +0100, Jens Axboe wrote:
> On Tue, Nov 05 2002, Adam Kropelin wrote:
> > Still without coaster I tried one more thing...
> > 'dd if=/dev/zero of=foo bs=1M' in parallel with another burn. That one
> > did it in. ;) I'm running ext3 and the writeout load totally killed
> > burn, which isn't surprising. I was asking for it, I know. What happened
>
> Really, this should work. The deadline scheduler should handle this just
> fine in fact. Which device is your burner and which device is the hard
> drive? It sounds like a bug.
Hard disk is sdc on onboard AIC7xxx.
Writer is hdc, the only device on the secondary onboard IDE channel.
All other disks (IDE & SCSI) were idle during the test.
Source image for the burn was on sdc3 and a directory on the same
partition was also the target for the 'dd'.
The system was exhibiting the usual spotty ext3 large writeout behavior
as has been discussed on the list before. Basically, vmstat 1 looks
something like this (captured from a different test on a different
machine but shows the same pattern):
0 1 1 120 4464 0 140856 0 0 0 15420 6235 520 0 42 58
0 1 1 120 4456 0 140856 0 0 0 3240 1094 36 0 2 98
1 0 0 120 4428 0 140844 0 0 0 52 1151 70 0 4 96
1 0 0 120 4440 0 141356 0 0 0 4 6810 541 1 42 57
0 0 0 120 4464 0 141320 0 0 0 0 6894 553 1 40 58
0 1 1 120 4396 0 140840 0 0 0 15508 6018 466 0 40 59
0 1 1 120 4388 0 140840 0 0 0 1608 1093 57 0 2 98
0 0 0 120 4404 0 140832 0 0 0 52 2350 165 0 12 87
0 0 0 120 4460 0 141380 0 0 0 4 7040 564 1 42 57
1 0 0 120 4356 0 141372 0 0 0 4 7073 570 1 45 54
> I'll try and reproduce that here, there's been a similar report (same
> oops) before. If you can just send me the dmesg output after a boot that
> should be fine.
Will do when I get home (now +9 hrs or so)...
> Thanks a lot for testing, it's this kind of testing I need to iron out
> the last few bugs!
No sweat. I've got three spindles of blank media left. ;)
--Adam, who remembers buying his first blank CDR for USD 19.95 and is
thankful CD writer testing is no longer so expensive.
next prev parent reply other threads:[~2002-11-06 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 4:13 2.5.46: ide-cd cdrecord (almost) success report Adam Kropelin
2002-11-06 7:22 ` Jens Axboe
2002-11-06 7:44 ` Jens Axboe
2002-11-06 23:25 ` Adam Kropelin
2002-11-07 14:33 ` Jens Axboe
2002-11-06 15:56 ` Adam Kropelin [this message]
2002-11-06 18:11 ` Patrick Mansfield
2002-11-06 23:33 ` Adam Kropelin
2002-11-06 23:52 ` Patrick Mansfield
2002-11-07 0:05 ` Adam Kropelin
2002-11-06 18:45 ` Jens Axboe
2002-11-06 23:23 ` Adam Kropelin
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=20021106155656.GA20403@www.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=axboe@suse.de \
--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 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.