Re: misleading error messages

[Thomas Schmitt]

Hi,

Mike Scheutzow wrote:
> At the very end, it did print the following (but I didn't notice it until
> after much debugging effort):
> xorriso : FAILURE : Image size 13004673s exceeds free space on media 12219392s

That's really a strange sequence of messages.


> xorriso : SORRY : Missing on disk and in ISO: disk_path
'/d2/android-studio'
> Not ok. Comparison or update failed due to error. (runtime 0.0 s)

These messages seems not to be related to the later reported size
overflow. There rather seems to be an -update_r command for a non-existing
disk path.


> xorriso : WARNING : No session MD5 is recorded with the loaded session
> MD5 MISMATCH WITH DATA OF LOADED SESSION !
> xorriso : FAILURE : Event triggered by MD5 comparison mismatch
> xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
> xorriso : FAILURE : -eject: Image changes pending. -commit or -rollback first

These look like a -commit command has already failed, probably due to
the size overflow, and a subsequent -check_md5 or -check_md5_r finds
no new session and no MD5 checksums.
But then the "Image size exceeds free space" message should have
preceeded the follow-up problems.

For now i cannot reproduce this strange effect.


What was the complete xorriso command line (maybe with anonymized
directory names except '/d2/android-studio') ?

Which version of xorriso are you using ?


> My suggestion is that if a disk does not have sufficient free space, it'd be
> much clearer if the app aborted immediately with that final FAILURE message

Obviously you have -abort_on set to FATAL or NEVER. Else there would
not be the message about -eject because the MD5 problem of severity
FAILURE would already have caused the program to end.

One could lower the threshold back to the default of FAILURE before
the -commit command. But for now it is not fully clear what caused the
MD5 problem without emitting an "Image size exceeds free space" message.
So it's not the time for fine tuning yet.


Have a nice day :)

Thomas