[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Calculated and written ECMA-119 tree end differ" under very specifi
From: |
Valtteri Vuorikoski |
Subject: |
Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances |
Date: |
Tue, 02 Feb 2021 00:18:03 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1.90 (gnu/linux) |
Thanks for the fix and detailed explanation. I have compiled 1.5.5 and
verified with -version that everything looks correct. zlib with
compressBound was also "yes".
The good news is that the MOVIE test case and all other test cases I had
work now. The bad news is that the full backup job with some 140k files
fails using an invocation that worked previously (apparently because
zisofs was only applied to files from the local filesystem).
The failing invocation (with a few directory names changed) is:
xorriso -for_backup -disk_dev_ino on -assert_volid 'HOME_*' FATAL -dev /dev/sr0
-volid "HOME_$(date +%Y_%m_%d)" \
-cdx $HOME -follow mount:param:pattern -not_mgt
param_on:subtree_on:ignore_off \
-not_leaf '.notmuch' -not_leaf '.nnmaildir' -not_paths afs/tmp -- \
-update_r Mail /Mail -update_r afs /afs \
-update stuff /stuff -update Documents/README.xorr /README \
-update_r more/stuff /stuff2 -update_r dotfiles /dotfiles \
-hardlinks perform_update -find /Mail -type f -pending_data -exec
set_filter --zisofs -- -commit
(README.xorr is a single file, the other update targets are directories.)
The abbreviated output is:
GNU xorriso 1.5.5 : RockRidge filesystem manipulator, libburnia project.
Drive current: -dev '/dev/sr0'
Media current: BD-RE
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 90.2g free
[…]
xorriso : UPDATE : Writing: 35008s 0.7% fifo 100% buf 100% 0.8xB
libisofs: WARNING : Calculated and written ECMA-119 tree end differ: 37525 <>
37458
xorriso : UPDATE : Writing: 37024s 0.7% fifo 100% buf 100% 0.9xB
[…]
xorriso : UPDATE : Writing: 5055296s 99.9% fifo 100% buf 100% 1.0xB
libisofs: FATAL : Image is most likely damaged. Calculated/written tree end
address mismatch.
libisofs: FATAL : Image is most likely damaged. Calculated/written image end
address mismatch.
xorriso : FATAL : -abort_on 'FAILURE' encountered 'FATAL' during image writing
xorriso : NOTE : libburn has now been urged to cancel its operation
xorriso : UPDATE : Writing: 5056704s 100.0% fifo 94% buf 100%
0.6xB
xorriso : FAILURE : libburn indicates failure with writing.
The error in the calculated/written tree difference is now the other way
around, i.e. the calculated number is larger than actual. Unfortunately
I could not reproduce the error with any significantly simpler set of
target files: it only occurs when I -update_r everything I want to
backup.
Switching -for_backup to "-md5 on -hardlinks on -acl on" makes the
operation succeed. check_md5 afterwards also succeeds.
If you have ideas for things to test here I can try them, though the
scanning/filtering phase now takes a while. Since the resulting ISO now
contains my maildir I can't send that for inspection.
-Valtteri
signature.asc
Description: PGP signature
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/01
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances,
Valtteri Vuorikoski <=
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/01
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Valtteri Vuorikoski, 2021/02/01
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/02
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Valtteri Vuorikoski, 2021/02/02
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/02
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/02
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Valtteri Vuorikoski, 2021/02/02
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/02
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/03
- Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances, Thomas Schmitt, 2021/02/04