All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>
To: Satyam Sharma <satyam@infradead.org>
Cc: Jan Kara <jack@suse.cz>,
	"Andries E. Brouwer" <Andries.Brouwer@cwi.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: iso9660 vs udf
Date: Wed, 19 Sep 2007 02:46:58 +0200	[thread overview]
Message-ID: <20070919004657.GB11444@mette> (raw)
In-Reply-To: <alpine.LFD.0.999.0709190534490.26241@enigma.security.iitk.ac.in>

On Wed, Sep 19, 2007 at 05:48:28AM +0530, Satyam Sharma wrote:

> > > 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.
> 
> Could you send the complete dmesg log, and what you mean with filesystem/
> kernel (incorrectly?) announcing it as UDF here ... I agree with Jan,
> this sounds like an issue with mount(8) to me.

You already got the relevant part of the dmesg log. Slightly more below.

I think the filesystem can be treated both as iso9660 and as udf,
at least that is what I seem to recall CD-BRIDGE means.  Thus,
if the kernel cannot mount it as udf, I think it is a kernel flaw.
Given that kernel flaw, and the fact that mounting as iso9660 works,
mount(8) could work around the kernel problem by guessing iso9660.
But maybe we should first try to fix the kernel.

Andries

Failed mount:
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

Success:
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root


  reply	other threads:[~2007-09-19  0:45 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 [this message]
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=20070919004657.GB11444@mette \
    --to=andries.brouwer@cwi.nl \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satyam@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.