Bug 1082360 - growisofs -M reports wrong number of free blocks with Blu-ray disc.
Summary: growisofs -M reports wrong number of free blocks with Blu-ray disc.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dvd+rw-tools
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Frantisek Kluknavsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-30 18:37 UTC by Luca Giuzzi
Modified: 2014-12-06 10:11 UTC (History)
3 users (show)

Fixed In Version: dvd+rw-tools-7.1-17.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-06 10:11:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Debian BTS 615978 0 None None None Never

Description Luca Giuzzi 2014-03-30 18:37:38 UTC
Description of problem:

growisofs -M reports wrong number of free blocks with Blu-ray disc;
as such, it is not possible to append to a pre-existing session unless
-overburn is specified.

Version-Release number of selected component (if applicable):

* growisofs by <appro.se>, version 7.1,


How reproducible:


Steps to Reproduce:
1. Write a blank blu-ray disc with growisofs -Z ...
2. Try and append a second session using growisofs -M ...
3.

Actual results:
error message

:-( /dev/sr1: -6810432 blocks are free, 1985136 to be written!
:-( write failed: No space left on device


Expected results:

the disc is recorded. Incidentally, with it seems that everything worked nicely with -overburn.

I copy the relevant part of the transcript in the latter case:

...

Writing:   Directory tree                          Start Block 9449404
:-( /dev/sr1: -6810432 blocks are free, 1985136 to be written!
:-! ignoring...
Done with: Directory tree                          Block(s)    141
Writing:   Joliet directory tree                   Start Block 9449545
Done with: Joliet directory tree                   Block(s)    71
Writing:   Directory tree cleanup                  Start Block 9449616
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 9449616
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 9449617
Total extents scheduled to be written = 1985136

...

Total translation table size: 0
Total rockridge attributes bytes: 161748
Total directory bytes: 274432
Path table size(bytes): 370
Done with: The File(s)                             Block(s)    1984745
Writing:   Ending Padblock                         Start Block 11434362
Done with: Ending Padblock                         Block(s)    150
Max brk space used 12b000
11434512 extents written (22333 MB)
builtin_dd: 1985136*2KB out @ average 1.5x4390KBps
/dev/sr1: flushing cache
/dev/sr1: copying volume descriptor(s)
/dev/sr1: flushing cache
/dev/sr1: closing track
/dev/sr1: reloading tray

Additional info:
Perhaps it is related to the debian bug here referenced (not so sure, though)

Comment 1 Frantisek Kluknavsky 2014-11-14 13:38:49 UTC
No idea why BD-R is an exception and nwa block is not counted. I erased the exception, now it is treated the same way as other media, as in the debian patch. I do not have a physical BD-R right now, please test the build http://koji.fedoraproject.org/koji/taskinfo?taskID=8142103
I would rather not push the change without any testing.

Comment 2 Luca Giuzzi 2014-11-20 10:37:32 UTC
I confirm that the new build appears to work properly.

Actually, after I wrote a first session I had 578047 extents being used...

Writing:   Ending Padblock                         Start Block 578047
Done with: Ending Padblock                         Block(s)    150
Max brk space used 21000
578197 extents written (1129 MB)
builtin_dd: 578208*2KB out @ average 1.0x4390KBps
/dev/sr1: flushing cache
/dev/sr1: closing track
/dev/sr1: reloading tray

On extending the record with a second session I got (as expected) the correct parameters to mkisofs

[lucag@poseidon Pictures-test]$ growisofs -J -r -v -v -v -M /dev/sr1 new

Executing 'mkisofs -J -r -v -v -v -C 16,578208 -M /dev/fd/3 new | builtin_dd of=/dev/sr1 obs=32k seek=36138'
I: -input-charset not specified, using utf-8 (detected in locale settings)

and no message abiyt the disk being overfull (as expected).

I shall try now appending a third session to see if errors are reported properly (but I suppose so).

Thanks,
 l

Comment 3 Fedora Update System 2014-11-20 10:48:34 UTC
dvd+rw-tools-7.1-17.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/dvd+rw-tools-7.1-17.fc21

Comment 4 Luca Giuzzi 2014-11-20 11:38:26 UTC
The output when the disk is overfull is a bit weird (but, at least, the system does not try to record it, so I would not complain) ... here it is:


:-( /dev/sr1: -7916032 blocks are free, 383 to be written!
:-( write failed: No space left on device


The session is beginning at 10002176 and the number of blocks to be written would be 9423968. It stands to reason that the remaining free blocks on the disk are just 1507936, so -7916032 is correct (even if I would phrase the sentence in a different way). What I do not quite understand is what 383 stands for here.

Comment 5 Fedora Update System 2014-11-22 20:22:22 UTC
Package dvd+rw-tools-7.1-17.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dvd+rw-tools-7.1-17.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-15623/dvd+rw-tools-7.1-17.fc21
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-12-06 10:11:01 UTC
dvd+rw-tools-7.1-17.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.