dmesg says : UDF-fs: error (device sr0): udf_fill_super: minUDFReadRev=260 (max is 250) After some read, seems like all Linux 3.xx kernels should read it, so this may be a left build option? Reproducible: Steps to Reproduce:
It's been a few years, and I've lost the details, but I think I've seen this as well. The last time I bought a laptop with Win7 installed, I ran the Win7 utility to burn a complete set of DVDs which could be used to restore Win7 as delivered, before wiping the hard drive to partition it for MGA. I remember trying to read those disks in MGA and getting UDF errors trying to mount them. I gave up because there was really no reason to pursue it. So, yeah, this has been around for awhile.
CC: (none) => ftg
Linux only supports 2.50 as the error: "(max is 250)" states, and it's still the same in current upstream git: fs/udf/udf_sb.h:#define UDF_MAX_READ_VERSION 0x0250
CC: (none) => tmb
Sorry, so Wikipedia UDF entry is wrong! Maybe I should update it?
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
It is a linux kernel limitation, let's close this bug.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX