linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Walter <srwalter@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: linux_udf@hpesjro.fc.hp.com, bfennema@falcon.csc.calpoly.edu
Subject: no files shown on UDF DVD
Date: Mon, 3 Sep 2001 19:48:09 -0500	[thread overview]
Message-ID: <20010903194809.A15650@hapablap.dyn.dhs.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

When I mount the Matrix DVD using the iso9660 filesystem, it appears
that the filesystem hierarchy is correct.

If, however, I use the udf filesystem, there are exactly zero files
shown as being on the CD.  As I understand it, this should not be the
case.

I've attached the UDF-fs DEBUG messages that resulted from
mounting the DVD.  I hope they're helpful in resolving this.
-- 
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
			-- George Orwell

[-- Attachment #2: udf-debug --]
[-- Type: text/plain, Size: 1705 bytes --]

UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0
UDF-fs DEBUG super.c:1410:udf_read_super: Multi-session=0
UDF-fs DEBUG super.c:1419:udf_read_super: Lastblock=0
UDF-fs DEBUG super.c:410:udf_vrs: Starting at sector 16 (2048 byte sectors)
UDF-fs DEBUG super.c:437:udf_vrs: ISO9660 Primary Volume Descriptor found
UDF-fs DEBUG super.c:446:udf_vrs: ISO9660 Volume Descriptor Set Terminator found
UDF-fs DEBUG super.c:760:udf_load_pvoldesc: recording time 933640160/0, 1999/08/02 17:29 (1e5c)
UDF-fs DEBUG super.c:770:udf_load_pvoldesc: volIdent[] = 'THE_MATRIX_16X9LB_N_AMERICA'
UDF-fs DEBUG super.c:777:udf_load_pvoldesc: volSetIdent[] = '27028BAA'
UDF-fs DEBUG super.c:961:udf_load_logicalvol: Partition (0:0) type 1 on volume 1
UDF-fs DEBUG super.c:971:udf_load_logicalvol: FileSet found in LogicalVolDesc at block=0, partition=0
UDF-fs DEBUG super.c:807:udf_load_partdesc: Searching map: (0 == 0)
UDF-fs DEBUG super.c:881:udf_load_partdesc: Partition (0:0 type 1511) starts at physical 665, block length 4097670
UDF-fs DEBUG super.c:1210:udf_load_partition: Using anchor in block 256
UDF-fs DEBUG super.c:732:udf_find_fileset: Fileset at block=0, partition=0
UDF-fs DEBUG super.c:793:udf_load_fileset: Rootdir at block=2, partition=0
UDF-fs INFO UDF 0.9.4.1-ro (2001/06/13) Mounting volume 'THE_MATRIX_16X9LB_N_AMERICA', timestamp 1999/08/02 19:29 (1ed4)
UDF-fs DEBUG directory.c:237:udf_get_fileident: 0x0 != TID_FILE_IDENT_DESC
UDF-fs DEBUG directory.c:239:udf_get_fileident: offset: 532 sizeof: 38 bufsize: 2048
UDF-fs DEBUG directory.c:237:udf_get_fileident: 0x0 != TID_FILE_IDENT_DESC
UDF-fs DEBUG directory.c:239:udf_get_fileident: offset: 532 sizeof: 38 bufsize: 2048

             reply	other threads:[~2001-09-04  0:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-04  0:48 Steven Walter [this message]
2001-09-05  1:57 ` no files shown on UDF DVD Rich Baum
     [not found]   ` <20010905110854.28802@dragon.linux.ix.netcom.com>
2001-09-06  0:14     ` Steven Walter

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=20010903194809.A15650@hapablap.dyn.dhs.org \
    --to=srwalter@yahoo.com \
    --cc=bfennema@falcon.csc.calpoly.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_udf@hpesjro.fc.hp.com \
    /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).