[Bug 313551] Vista burned UDF volumes won't mount

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Vista burned UDF volumes won't mount
Alias: vista-udf

https://bugzilla.redhat.com/show_bug.cgi?id=313551


pebolle at tiscali.nl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pebolle at tiscali.nl




------- Additional Comments From pebolle at tiscali.nl  2008-06-24 09:31 EST -------
For what it's worth, I ran into a UDF formatted CD that couldn't be mounted with
the current F9 kernel (2.6.25.6-55.fc9.i686) but can be mounted with a recent
rawhide kernel (2.6.26-0.74.rc6.git4.fc10.i686). 

/var/log/messages simply says:
UDF-fs: Filesystem marked read-only because writing to pseudooverwrite partition
is not implemented.
UDF-fs INFO UDF: Mounting volume 'UDF Volume', timestamp 2008/03/24 18:53 (1078)

dmesg has more:
UDF-fs DEBUG fs/udf/lowlevel.c:43:udf_get_last_session: XA disk: no,
vol_desc_start=0
UDF-fs DEBUG fs/udf/super.c:1920:udf_fill_super: Multi-session=0
UDF-fs DEBUG fs/udf/super.c:613:udf_vrs: Starting at sector 16 (2048 byte
sectors)
UDF-fs DEBUG fs/udf/super.c:935:udf_load_pvoldesc: recording time 2008/03/24
16:53 (1000)
UDF-fs DEBUG fs/udf/super.c:944:udf_load_pvoldesc: volIdent[] = 'UDF Volume'
UDF-fs DEBUG fs/udf/super.c:949:udf_load_pvoldesc: volSetIdent[] = '10353852 UDF
Volume Set'
UDF-fs DEBUG fs/udf/super.c:1481:udf_load_logicalvol: Partition (0:8192) type 1
on volume 1
UDF-fs DEBUG fs/udf/super.c:1481:udf_load_logicalvol: Partition (1:8192) type 2
on volume 1
UDF-fs DEBUG fs/udf/super.c:1490:udf_load_logicalvol: FileSet found in
LogicalVolDesc at block=0, partition=1
UDF-fs DEBUG fs/udf/super.c:1271:udf_load_partdesc: Searching map: (8192 == 8192)
UDF-fs DEBUG fs/udf/super.c:1125:udf_fill_partdesc_info: Partition (0 type 1511)
starts at physical 288, block length 359296
UDF-fs DEBUG fs/udf/super.c:1125:udf_fill_partdesc_info: Partition (1 type 2012)
starts at physical 288, block length 359296
UDF-fs: Filesystem marked read-only because writing to pseudooverwrite partition
is not implemented.
UDF-fs DEBUG fs/udf/super.c:1745:udf_load_sequence: Using anchor in block 256
UDF-fs DEBUG fs/udf/super.c:1947:udf_fill_super: Lastblock=49120
UDF-fs DEBUG fs/udf/super.c:903:udf_find_fileset: Fileset at block=0, partition=1
UDF-fs DEBUG fs/udf/super.c:1062:udf_load_fileset: Rootdir at block=1,
partition=1
UDF-fs INFO UDF: Mounting volume 'UDF Volume', timestamp 2008/03/24 18:53 (1078)

part of hexdump looks similar to comment#11:
0000b0d0  00 00 00 21 00 08 00 00  00 2a 4f 53 54 41 20 55  |...!.....*OSTA U|
0000b0e0  44 46 20 43 6f 6d 70 6c  69 61 6e 74 00 00 00 00  |DF Compliant....|
0000b0f0  01 02 00 00 00 00 00 00  00 08 00 00 00 00 00 00  |................|

/proc/mounts just gives:
/dev/sr1 /mnt/tmp udf ro,utf8 0 0

So (part of?) this bug seems fixed in kernel 2.6.26-rc6. 

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.