From: Bryce Nesbitt <bryce@obviously.com>
To: Andries.Brouwer@cwi.nl, util-linux@math.uio.no
Cc: Lionel.Bouton@free.fr, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: Why would a valid DVD show zero files on Linux?
Date: Fri, 04 Jan 2002 23:20:40 -0500 [thread overview]
Message-ID: <3C367F18.4F879E3B@obviously.com> (raw)
In-Reply-To: <UTC200201050250.CAA232926.aeb@cwi.nl>
Confirmed. The DVD in question (DeLorme Topo USA) shows files when mounted
with "nojoliet". But when the application is run, the maps are scrambled.
It must be mounted as udf to work.
The original bug report incorrectly asserted that the iso9660 filesystem
was empty, sorry about that.
But this does seem to be an example (which
has been widely reported elsewhere) of a DVD with a differing udf and iso9660
filesystems. Lots of people have reported that, since Windows no longer
uses the "iso9660 udf bridge", lots of mastered DVDs have unintentionally
corrupt versions of it. Others have hinted this is done deliberately for
copy protection reasons.
-Bryce
Solving the problem by documentation
------------------------------------
The patches already supplied to mount(8) and fstab (5) give give a sysadmin
the tools to learn about and solve the problem, thanks for applying them!
It just seems like there's a bit more to say about potentially differing udf
and iso9660 filesytems on the same disc... that's the thiking behind the extra
paragraph in the patch.
Solving the problem automatically (keeping the issue out of the users face)
---------------------------------------------------------------------------
Mastering houses will test their discs on Windows. While in general emulating Windows
is something I hate, here it makes sense. The more
closely the mount automounter emulates how windows automounts, the more likely
this type of discussion will never need to come up.
According to Alan Windows tries udf first, blindly, then falls back to iso9660.
As many people pointed out, this is not a kernel issue, it's a automount
isuse.
Andries.Brouwer@cwi.nl wrote:
>
> > Here are the first 2048 1024 byte blocks.
>
> Hmm. I am a bit slow, but just looked at this image.
> It looks fine in iso9660 style, provided you give the
> nojoliet option. I get:
>
> # mount DeLorme_TopoUSA_DVD.head /mnt -t iso9660 -o loop,nojoliet
> # ls -l /mnt
> total 12
> dr-xr-xr-x 1 root root 2048 Feb 28 2001 .
> drwxr-xr-x 31 root root 4096 Jan 3 02:11 ..
> -r-xr-xr-x 1 root root 2763 Feb 28 2001 cd.txt
> dr-xr-xr-x 1 root root 2048 Feb 28 2001 data
> -r-xr-xr-x 1 root root 196 Feb 28 2001 pdataset.txt
>
> and
>
> # mount DeLorme_TopoUSA_DVD.head /mnt -t udf -o loop
> # ls -l /mnt
> total 14
> dr-xr-xr-x 3 4294967295 4294967295 184 Feb 28 2001 .
> drwxr-xr-x 31 root root 4096 Jan 3 02:11 ..
> -r--r--r-- 1 4294967295 4294967295 2763 Feb 28 2001 CD.TXT
> dr-xr-xr-x 2 4294967295 4294967295 380 Feb 28 2001 DATA
> -r--r--r-- 1 4294967295 4294967295 196 Feb 28 2001 PDATASET.TXT
>
> so the iso9660 version looks a bit better than the udf version.
> (But I cannot look at the actual contents because the initial
> fragment is not large enough. You can check for yourself
> whether the nojoliet mount is OK.)
>
> Thus, there do not seem reasons to change mount(2) or mount(8)
> in the way you suggested. There is no "empty iso9660 filesystem" here.
>
> Andries
next prev parent reply other threads:[~2002-01-05 4:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 2:50 Why would a valid DVD show zero files on Linux? Andries.Brouwer
2002-01-05 4:20 ` Bryce Nesbitt [this message]
2002-01-05 16:14 ` Bryce Nesbitt
-- strict thread matches above, loose matches on Subject: below --
2002-01-05 17:16 Andries.Brouwer
2001-12-31 15:29 Andries.Brouwer
2002-01-01 11:50 ` Kai Henningsen
2001-12-31 3:01 RaúlNúñez de Arenas Coronado
2001-12-31 0:51 Bryce Nesbitt
2001-12-31 0:45 Bryce Nesbitt
2001-12-31 1:06 ` Alan Cox
[not found] ` <3C2FB85E.3080508@free.fr>
2001-12-31 2:07 ` Bryce Nesbitt
2001-12-31 13:13 ` Alan Cox
2001-12-31 14:21 ` Bryce Nesbitt
2001-12-31 14:48 ` Marius Gedminas
2002-01-01 10:40 ` Alan Cox
2001-12-31 15:10 ` Vitaly Lipatov
2001-12-31 23:37 ` Cameron Simpson
2002-01-01 5:34 ` Bryce Nesbitt
2002-01-01 10:12 ` Alan Cox
2002-01-01 10:30 ` Ryan Cumming
2002-01-01 10:43 ` Alan Cox
2002-01-01 10:46 ` Alan Cox
2002-01-01 14:22 ` Bryce Nesbitt
2002-01-01 15:24 ` Alan Cox
2002-01-01 23:29 ` Grahame Jordan
2002-01-01 23:49 ` Bryce Nesbitt
2002-01-01 23:53 ` Alan Cox
2002-01-02 7:57 ` Grahame Jordan
2002-01-30 15:08 ` Bryce Nesbitt
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=3C367F18.4F879E3B@obviously.com \
--to=bryce@obviously.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=Lionel.Bouton@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux@math.uio.no \
/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