Bug 2872 - Cannot read information from UDF disks.
Summary: Cannot read information from UDF disks.
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: File System
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Adrian Bunk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-12 02:37 UTC by Miguel Quiros
Modified: 2005-07-05 16:24 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.6
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Miguel Quiros 2004-06-12 02:37:10 UTC
Distribution: Fedora Core 2
Hardware Environment: It happens in a Pentium II and also in a Pentium IV
Software Environment:
Problem Description: After mounting a CD-RW, I cannot read the information on
it, previously recorded either from Windows or from linux packet-udf.
Doing ls -al, I can see only the names of the directories at the toplevel of the
disk but the owner, date, permissions, etc.. of these directories do not show up
(a lot of ????? appear instead). I cannot inspect the contents of these directories.
The problem happens with the 2.6.5 kernel shipped with Fedora Core 2 and also
with 2.6.6 compiled by me. Fortunately, I have kept in the system a copy of the
2.6.3 kernel. If I boot with 2.6.3, I can access the disk without problems (and
even writting to it via pktcdvd).
Something odd seems to have been introduced between 2.6.3 and 2.6.5/2.6.6.

Steps to reproduce: Mount a UDF formated disk with some information on it
previously written in other equipment with, for example, a Windows tool and try
to fetch the information.
Comment 1 Miguel Quiros 2004-06-23 00:27:43 UTC
I have taken the liberty of adding bfennema@falcon.csc.calpoly.edu to the CC of
this bug, since I have seen in the Changelog of kernel version 2.6.5 that he is
responsible for some changes in the udf module, perhaps related with this issue.
I have also seen in the Changelog of 2.6.7 that something has been fixed by him,
perhaps also related with this bug.
Comment 2 Miguel Quiros 2004-06-29 01:02:37 UTC
Seems to be fixed in kernel 2.6.7
Comment 3 Adrian Bunk 2005-07-05 16:24:02 UTC
As noted in the bug logs, this seems to be already fixed in more recent kernels.

Note You need to log in before you can comment on or make changes to this bug.