Messages in this thread |  | | Date | Tue, 30 Oct 2001 17:44:15 -0800 | From | Andrew Morton <> | Subject | Re: cdrecord from ext3 |
| |
"J . A . Magallon" wrote: > > 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' ?
The ext3 read paths are basically identical to ext2. The whole journalling thing only gets involved with writes.
> Kernel: 2.4.13-ac5+bproc, controller is an Adaptec >
bproc? scyld distributed process thing, or something else?
Something strange is happening. Could you please investigate further? For example:
dd if=/dev/zero of=foo bs-1024k count=600 time cat foo > /dev/null
How long does the `cat' take on ext2 and ext3?
- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |