Caught red-handed! The issue occurs if the media is appendable (status 1): because of the improperly applied DVD-RW media variable (in features instead of profiles) , everything is DVD-RW restricted overwrite just if the device is DVD recorder and if the disk is appendable (CD-R, CD-RW or DVD-RW in sequential mode) is going to be reset to blank as DVD-RW in restricted mode.
So our assumption was wrong: the first fix made it. And that's it.
BTW, we can easily add BD-RE to the mix - in t10 documentation you can find that it's the same as DVD+RW as far as status is concerned (0 -new, 2 -formatted so we need to read the media), it formats in the background like DVD+RW, just adds spare area as in DVD-RAM. But I have no hardware to test.
Caught red-handed! The issue occurs if the media is appendable (status 1): because of the improperly applied DVD-RW media variable (in features instead of profiles) , everything is DVD-RW restricted overwrite just if the device is DVD recorder and if the disk is appendable (CD-R, CD-RW or DVD-RW in sequential mode) is going to be reset to blank as DVD-RW in restricted mode.
The commit
http:// git.kernel. org/?p= linux/hotplug/ udev.git; a=commitdiff; h=2458db3edd8d6 6827b34978ff471 dff8f879e9ab
fixes the issue.
So our assumption was wrong: the first fix made it. And that's it.
BTW, we can easily add BD-RE to the mix - in t10 documentation you can find that it's the same as DVD+RW as far as status is concerned (0 -new, 2 -formatted so we need to read the media), it formats in the background like DVD+RW, just adds spare area as in DVD-RAM. But I have no hardware to test.