Hi, > a non-kernel workaround should not be the goal,
Not a final goal, indeed. But maybe we learn more from writing chunks of 64 KiB. > So there must be changes between kernel > 2.6.32.5 and 3.2.0.4 for ioctl I assume it's in the levels below the ioctl(). There is queing of command requests, driver code for particular busses and controller boards, ... lots of room to look for bugs. > I will test a newer kernel asap. This will at least clarify whether it was a short living problem in the kernel. ------------------------------------------------------- > growisofs sr0info [...] xorriso sr1info: Strange. The first mediainfo reports > Mounted Media: 41h, BD-R SRM which would match the media state that is used by libburn underneath xorriso. The second one is > Mounted Media: 41h, BD-R SRM+POW which would match growisofs. But this from the first one does not look like the libburn results on my own BD burners: > Disc status: complete > Number of Sessions: 1 > State of Last Session: complete > Number of Tracks: 1 > READ TRACK INFORMATION[#1]: > Track State: complete incremental > Track Start Address: 0*2KB > Free Blocks: 0*2KB > Track Size: 12219392*2KB > Last Recorded Address: 5908367*2KB This is a closed medium (use xorriso -as cdrecord option -multi to keep it appendable if this is desired). But why does the drive report as track size the whole medium ? Well, the read size info looks ok: > READ CAPACITY: 5908368*2048=12100337664 Probably the message by xorriso is a consequence of the Pseudo Overwrite formatting which growisofs applied. Hard to say whether this is sane or not. libburn does not do POW. The growisofs medium is appendable. But that does not mean it would have an incomplete session. (I will have to invest a BD-R for learning more about the doings of growisofs on these media.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org