Summary: | UDF (with DVD-RAM) isn't mountable/readable | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Oliver Herold <oliver> | ||||
Component: | kern | Assignee: | freebsd-fs (Nobody) <fs> | ||||
Status: | In Progress --- | ||||||
Severity: | Affects Only Me | CC: | decui, editor, emoaddict15, grahamperrin, mondo.debater_0q, mrT1188123, scineram, shitman71, weh, whu | ||||
Priority: | --- | ||||||
Version: | Unspecified | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Oliver Herold
2008-02-23 11:50:02 UTC
Responsible Changed From-To: freebsd-i386->freebsd-bugs This does not sound i386-specific. I wonder if it is related to kern/120967? CC: Mark Linimon: no, it's not related. As a maintainer of sysutils/udfclient port and a guy who spent a lot of time on in-kernel UDF FS, I can tell that this problem is caused by FreeBSD fs/udf supporting only older UDF standards. Newer UDF features (>=2.00), like extended file entries, are not supported. So, I am not sure how to qualify this PR: a bug, a feature request, or ... One thing is for sure: FreeBSD UDF fs doesn't get attention that it actually needs. -- Andriy Gapon Responsible Changed From-To: freebsd-bugs->scottl Assign to udf author Scott Long, who seems to be collecting udf PRs. Oliver, if you still have that disk around and have an opportunity to check it with FreeBSD, could you please try the patch attached? The patch is against RELENG_7 but it should apply cleanly to not so distant releases/branches. This patch contains larger fixes for various UDF problems and in addition it also contains very basic support for UDF 2.X. Technically speaking it adds support for Extended File Entry, but not anything else. Just in case, to apply the patch you need the following: 1. FreeBSD sources :-) 2. cd /usr/src 3. patch -p1 < /path/to/the/patch 4. cd sys/modules/udf 5. make obj && make depend && make && make install 6. kldload udf The above assumes that you use udf as module. If you have it built into kernel you then instead of 5 and 6 you would need to build the kernel and reboot. -- Andriy Gapon freebsd is still missing udf 2.x support. if wikipedia is correct the latest revision is udf 2.60 from 2005. reinoud zandijk has taken scotts udf 1.x work and extended it to support udf 2.60. [1] the code is in the netbsd (and also openbsd) tree. maybe somebody is willing to backport it to freebsd. cheers. alex [1] http://mail-index.netbsd.org/current-users/2006/02/02/0027.html -- Alexander Best on 19/07/2010 05:07 Alexander Best said the following: > freebsd is still missing udf 2.x support. if wikipedia is correct the > latest revision is udf 2.60 from 2005. > > reinoud zandijk has taken scotts udf 1.x work and extended it to > support udf 2.60. [1] the code is in the netbsd (and also openbsd) > tree. maybe somebody is willing to backport it to freebsd. Yeah. http://www.freebsd.org/projects/ideas/ideas.html#p-portudf -- Andriy Gapon In the header of this bug report the tag: Importance currently reads: Normal Affects Only Me This is incorrect. This issue affects others. I am presently using PCBSD10.3 and this exact issue is still present. I have also noted from google that it has affected several others. Anyone who wants to mount a modern UDF CD/DVD ROM will not be able to on FreeBSD (at least with version 10.3). I suspect correcting this tag could have an impact on getting some attention to this problem. mount_udf is clearly a problem, i cant mount or read any kind of new dvd. something like this seems to me important because it heavily impacts your workflow if things like this dont work. we now have bhyve and this requires using newer kinds of media, making iso-images and other stuff. This is still a problem. I've been debating for years to switch to FreeBSD as I really enjoy the BSD license over GPL. With XFCE4 FreeBSD works fairly well. However, I installed virtualbox so I could install Windows 7 in a VM for things that I will not be able to use natively. I am unable to mount my Windows 7 DVD because of this. Hi. mount_udf and the udf kernel code was originally my baby, but I did some very naive things in it that worked for mainstream DVD-ROM media but were not fully compliant with the spec. I can work on this for a few evenings, but I don't have a way to easily create a DVD-RAM test case. Would it work to do a 'dd' image of your test disk and make it available to me to download? That might help to accelerate my efforts on this. Hi Scott, Glad to see a response. Was not expecting one! The DVD is simply the Windows 7 install DVD, but you could achieve the same result with the freely downloadable Windows 10 DVD and burning it. The Windows 10 ISO is unfortunately downloaded by a tool so I don't know how well it work on FreeBSD with Wine: https://www.microsoft.com/en-us/software-download/windows10. If it helps, I could make a stripped down Windows 7 ISO that removes the large WIM files and upload that somewhere or email you a link. Thanks, Frank Is dd equal to illegal disk copy tools? You need to copy your disk exactly equal the way it is if you want to do any testing. This means i have to make an illegal copy for you, can we do this? Rights could be an problem, i could help you otherwise by testing it myself on my own machine. There is many things i can test, i will give you some information what protocol is required on those disks. You can work on this. Hi! This would be nice to have. Wanted to create fat32 Windows 10 installer USB, but couldn't mount downloaded udf iso with these symptoms. Keyword: patch or patch-ready – in lieu of summary line prefix: [patch] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi> Triage: * severity reduced, to the norm for a non-security bug report * … With bugmeister hat, return to pool. This functionality would be nice to have, else have it in libarchive(3). |