Re: Linux, ISOFS, multi-extent files: what's the status?
On Mon, Jan 18, 2010 at 20:58, Bill Davidsen <davidsen@tmr.com> wrote:
> I have just turned down readahead in blockdev and my issues have gone away,
> but like you I don't see it much if a while.
Isn't the read-ahead thing solved with padding?
ie mkisofs adds 150k by default since some time, and when burning I've
always used 1MB of padding (ie cdrecord's padsize=512s), just to be
safe.
In the meantime I tried multi-extent in a > 4.7GB isofs image:
- On linux 2.4.33: success burning 6GB file on isofs and then on actual BD-RE
- On RHEL5 (2.6.18.something): 24GB file on an isofs image file is ok
(blu-ray burner will arrive in a few weeks)
--
giulioo@pobox.com
Reply to:
- References:
- Linux, ISOFS, multi-extent files: what's the status?
- From: Giulio <giulioo@gmail.com>
- Re: Linux, ISOFS, multi-extent files: what's the status?
- From: Joerg.Schilling@fokus.fraunhofer.de (Joerg Schilling)
- Re: Linux, ISOFS, multi-extent files: what's the status?
- From: Bill Davidsen <davidsen@tmr.com>
- Re: Linux, ISOFS, multi-extent files: what's the status?
- From: Volker Kuhlmann <hidden@paradise.net.nz>
- Re: Linux, ISOFS, multi-extent files: what's the status?
- From: Bill Davidsen <davidsen@tmr.com>