public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Sam Vilain <sam@vilain.net>, Luke-Jr <luke@dashjr.org>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	Bernhard Rosenkraenzer <bero@arklinux.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [slightly OT] dvdrecord 0.3.1 -- and yes, dev=/dev/cdrom works ;)
Date: Tue, 28 Feb 2006 17:30:54 -0500	[thread overview]
Message-ID: <4404CF1E.2010309@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602282012480.15391@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>> Yes. A 650 MB *CD*-RW (DVD-RW too?) formatted in packet mode only has like
>>> 500-something megabytes to allow for the sort of seeks required.
>>> On DVD+RW, you get the full 4.3 GB (4.7 gB) AFAICS.
>> DVD-RAM physically is formatted like a hard disk.  It is broken up into zones
>> that hold different numbers of sectors which are individually and randomly
>> read/writable.  CD/DVD+-RW media is organized as a single long groove that
>> consists of an unbroken series of large blocks composed of small blocks with
>> user and control data interleaved and error corrected.  It is for this reason
>> that historically it could only be recorded from start to finish in one pass.
>>
>> There are two modern techniques to allow pseudo random write access for all
>> forms of CD/DVD +/- RW media.  These are packet mode, and mount rainier mode.
>> MRW mode formats the disk into 32 KB blocks made up of 2048 byte sectors which
>> are individually writable as far as the OS knows, because an MRW compliant
>> drive is required to internally handle any required read/modify/write cycles to
>> update the 32 KB blocks.  MRW mode also reserves some of the disk for sector
>> sparing which the drive firmware also handles.  MRW mode is typically used on
>> dvd+rw media. IIRC, this format typically "wastes" about 10% of the capacity of
>> the medium.
>>
> I doubt that. 10% of a 4.3 GB disk are, well, roughly 430 MB, which would 
> make df show 3.9 GB as mountpoint size, not 4.3 GB. [MB and GB are powers 
> of 1024 here.]
> 
Was that DVD recorded MtR or packet?


-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  reply	other threads:[~2006-03-07 16:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 23:42 [slightly OT] dvdrecord 0.3.1 -- and yes, dev=/dev/cdrom works ;) Bernhard Rosenkraenzer
2006-02-25 18:17 ` David Gómez
2006-02-25 18:38   ` Jesper Juhl
2006-02-25 19:14 ` Gene Heskett
2006-02-26 13:30 ` Luke-Jr
2006-02-26 13:29   ` Jesper Juhl
2006-02-26 13:39     ` Luke-Jr
2006-02-26 13:36       ` Jesper Juhl
2006-02-26 15:50       ` Bernd Petrovitsch
2006-02-26 22:32       ` Jan Engelhardt
2006-02-26 23:59         ` Sam Vilain
2006-02-27 18:50           ` Jan Engelhardt
2006-02-28 18:58             ` Phillip Susi
2006-02-28 19:14               ` Jan Engelhardt
2006-02-28 22:30                 ` Bill Davidsen [this message]
2006-03-08 13:52                   ` Jan Engelhardt
2006-03-01  0:05               ` Rob Sims
2006-02-27 15:32 ` Dick Streefland

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=4404CF1E.2010309@tmr.com \
    --to=davidsen@tmr.com \
    --cc=bero@arklinux.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@dashjr.org \
    --cc=sam@vilain.net \
    /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