public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: cdrecord from ext3
Date: Wed, 31 Oct 2001 00:18:46 +0100	[thread overview]
Message-ID: <20011031001846.A1840@werewolf.able.es> (raw)

Hi all,

I have found a strange problem using cdrecord from an ext3 partition.
When burning a cd image (about 500Mb), with cdrecord -v to see some info,
after about 150Mb the percentage of fifo filled begins to drop, until the
burning fails. I though it was related to some buffer/cache issue, but
then I just copied the image to an ext2 partition (so the cache still
filled more, just reaching my ram size), and burnt perfect from the
ext2 partition.

So it looks like ext3 can not give a sustained read rate (not so much,
burning was at 8x). Fifo from ext2 never dropped below 99%.

Is this a bug or the answer is just 'never toast from a journaled fs' ?

Kernel: 2.4.13-ac5+bproc, controller is an Adaptec

Controller:
Adaptec AIC7xxx driver version: 6.2.4
aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

Drives:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: DDYS-T09170N     Rev: S96H
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM      Model: DCAS-34330W      Rev: S65A
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: CREATIVE Model: CD5230E          Rev: 1.01
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 00
  Vendor: YAMAHA   Model: CRW8424E         Rev: 1.0j
  Type:   CD-ROM                           ANSI SCSI revision: 02

Settings:
Channel A Target 0 Negotiation Settings
        User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
        Goal: 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
        Curr: 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
		(ext2)
Channel A Target 1 Negotiation Settings
        User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
        Goal: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
        Curr: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
		(ext3)

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.13-ac5-beo #1 SMP Tue Oct 30 00:10:00 CET 2001 i686

             reply	other threads:[~2001-10-31  1:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 23:18 J . A . Magallon [this message]
2001-10-31  1:34 ` cdrecord from ext3 Daniel T. Chen
2001-10-31  1:44 ` Andrew Morton
2001-10-31 14:59   ` J . A . Magallon
2001-10-31 17:52     ` H. Peter Anvin
2001-10-31 18:40       ` Mike Castle
2001-10-31 23:40         ` M. R. Brown
2001-10-31 23:57           ` Mike Castle
     [not found]     ` <200110311752.JAA06153@cesium.transmeta.com>
     [not found]       ` <20011031192425.A1757@werewolf.able.es>
     [not found]         ` <3BE04AA3.7010303@zytor.com>
     [not found]           ` <20011102010824.C12958@werewolf.able.es>
2001-11-02  0:09             ` cdrecord from ext3 [jamagallon@able.es] J . A . Magallon

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=20011031001846.A1840@werewolf.able.es \
    --to=jamagallon@able.es \
    --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