#3588 Issue open: Remove 'ebiso' support in ReaR 3.0¶
Labels: cleanup
jsmeix opened issue at 2026-03-20 13:47:¶
Related to
https://github.com/rear/rear/pull/3306
and
https://github.com/rear/rear/pull/3587
I think that 'ebiso' support could be removed
to avoid that we (in particular I)
may have to deal with special 'ebiso' issues
where 'xorrisofs' should be the better generic tool.
pcahyna commented at 2026-03-20 15:16:¶
With ebiso support removed, could we set ISO_FILE_SIZE_LIMIT to 0 to
stop our default configuration break setups with big backups embedded in
the iso? Seems that #2525 would not be necessary anymore.
jsmeix commented at 2026-03-23 09:02:¶
ebiso is one example why the default ISO_FILE_SIZE_LIMIT
is set to 2 GiB to be by default on the safe side.
With ebiso support removed, this example is no longer there.
I know nothing at all about ISO creating tools in practice
if there still could be a ISO_FILE_SIZE_LIMIT of 2 GiB.
The Wikipedia article
https://en.wikipedia.org/wiki/ISO_9660
still metiones a limit of 4 GiB, see
https://github.com/rear/rear/pull/2525#issuecomment-4108934909
So perhaps after ebiso support is removed
ISO_FILE_SIZE_LIMIT=4294967296
in default.conf is still needed to be by default on the safe side?
Cf.
https://github.com/rear/rear/pull/2525#issuecomment-734253649
and my comment in the default.conf description (excerpt):
When there is a 2GiB file size limit a backup.tar.gz
that is greater than 2GiB will get corrupted in the ISO
so backup restore via "rear recover" would fail
which is a dead end because the backup in the ISO
got corrupted which is a severe error.
Whether or not a default ISO_FILE_SIZE_LIMIT=0
should be set is not something which I further discuss
or even implement "by the way" within this issue here
but via the separated issue
https://github.com/rear/rear/issues/3589
[Export of Github issue for rear/rear.]