Unable to mount a partition because the unsettable "needs_recovery" flag is set.

When a partition formatted in Vu+Duo2 is mounted in a modern Linux system, the partition gets updated with the needs_recovery flag, which then makes the partition unmountable in Vu+Duo2 under OpenBlackHole 4.4.

Who is responsible for this bug?

(This flag is already present in the 3.13.5 kernel.)
 
Last edited:
I do not think that much has changed between the releases—namely: the kernel version—for this to be irrelevant.

I am simply trying to mount an ext4 partition in a Vu+Duo2 after the partition has been mounted in an up-to date Linux system. That seems impossible, as the partition has surreptitiously gained the incompatible flag needs_recovery and Vu+Duo2 now refuses to mount it.
 

Antikapitalista

Vu+ Newbie
What does the emotional state of Linux have to do with this?

The check is performed by a userland tool (from the e2fsprogs package); the file system is consistent, so it passes the file system check, but has the above-mentioned incompatible feature that is not supported by the kernel, which consequently refuses to mount the partition.
 
Top