From: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>
To: linux-kernel@vger.kernel.org
Subject: iso9660 vs udf
Date: Sat, 15 Sep 2007 23:49:31 +0200 [thread overview]
Message-ID: <20070915214926.GA31416@mette> (raw)
Today I got a CD. MacOS does not mount it and Linux does not
mount it without an explicit filesystemtype option.
That is,
# mount /dev/hdc /dir -t iso9660
works fine, but
# mount /dev/hdc /dir
mount: you didn't specify a filesystem type for /dev/hdc
I will try type udf
mount: wrong fs type, bad option, bad superblock on /dev/hdc,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
# dmesg | tail
UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'Wisk1956-82', timestamp 2006/03/07 16:26 (1078)
udf: udf_read_inode(ino 547) failed !bh
UDF-fs: Error in udf_iget, block=1, partition=1
Google gave me half a dozen other people that mentioned the same
problem (with the same inode 547). Clearly some CD mastering software
produces a format that Linux and MacOS do not handle easily.
One result of this letter will be that people with the same problem
learn via Google that using the "-t iso9660" option may help.
What goes wrong on the mount side is that when it hesitates between
iso9660 and udf it decides for udf when seeing "NSR02".
Maybe the heuristics in mount should be tuned.
On the other hand, this filesystem announces itself as UDF
("CD-RTOS" "CD-BRIDGE" "CDUDF File System - Adaptec Inc"),
perhaps the kernel code should be more robust.
If anybody feels responsible for mount and/or this kernel area
we might discuss.
Andries
next reply other threads:[~2007-09-15 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 21:49 Andries E. Brouwer [this message]
2007-09-18 14:47 ` iso9660 vs udf Jan Kara
2007-09-19 0:18 ` Satyam Sharma
2007-09-19 0:46 ` Andries E. Brouwer
2007-09-19 2:35 ` Satyam Sharma
2007-09-19 2:44 ` Randy Dunlap
2007-09-19 8:36 ` Andries E. Brouwer
2007-09-19 11:36 ` Kay Sievers
2007-09-19 11:11 ` Krzysztof Halasa
2007-09-19 13:23 ` Karel Zak
2007-09-19 19:37 ` Andries E. Brouwer
2007-09-19 21:51 ` Phillip Susi
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=20070915214926.GA31416@mette \
--to=andries.brouwer@cwi.nl \
--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;
as well as URLs for NNTP newsgroup(s).