linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: iso9660 vs udf
Date: Wed, 19 Sep 2007 17:51:08 -0400	[thread overview]
Message-ID: <46F199CC.4080600@cfl.rr.com> (raw)
In-Reply-To: <20070915214926.GA31416@mette>

Andries E. Brouwer wrote:
> 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

What does the line for hdc show in /etc/fstab?  Mount tries whichever 
filesystem(s) is/are listed there if you omit -t.  My guess is that it 
only lists udf and this is a cd so it contains iso9660, not udf.


      parent reply	other threads:[~2007-09-19 21:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 21:49 iso9660 vs udf Andries E. Brouwer
2007-09-18 14:47 ` 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 [this message]

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=46F199CC.4080600@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=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).