[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070919004657.GB11444@mette>
Date: Wed, 19 Sep 2007 02:46:58 +0200
From: "Andries E. Brouwer" <Andries.Brouwer@....nl>
To: Satyam Sharma <satyam@...radead.org>
Cc: Jan Kara <jack@...e.cz>,
"Andries E. Brouwer" <Andries.Brouwer@....nl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: iso9660 vs udf
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists