Hi, this looks more like a problem of genisoimage than of growisofs. Regrettably both are unmaintained in Debian and upstream.
Do you get better results if you use xorrisofs instead of genisoimage ? If not yet installed, get xorriso by: sudo apt install xorriso Use its mkisofs emulation named "xorrisofs" with growisofs by export GENISOIMAGE=xorrisofs growisofs -r -M /dev/sr1 test_dir It might be that xorrisofs throws an error on the existing genisoimage generated filesystem. So it might be necessary to start a new sequence of ISO 9660 sessions by growisofs -Z. Alternatively you could use xorriso in its native command mode which does the burning, too. The equivalent of growisofs -Z is done by command -outdev and command -blank with mode "as_needed", which will do nothing if the medium is already blank: xorriso -outdev /dev/sr1 -blank as_needed -map test_dir / -find / -exec mkisofs_r -- The equivalent of growisofs -M is done by -dev and without -blank: xorriso -dev /dev/sr1 -map test_dir / -find / -exec mkisofs_r -- You may use for testing a data file instead of /dev/sr1. It will behave like a DVD+RW medium in a drive. E.g. with "$HOME"/test.iso : xorriso -outdev "$HOME"/test.iso ... xorriso -dev "$HOME"/test.iso ... The parent directory of the file has to exist already. Note that the sequence of xorriso commands matters: First acquire the drive, then blank it, then put files into the emerging ISO filesystem by -map, then manipulate them by -find. The final write command -commit can be omitted, because xorriso writes the session at program end if changes to its model of the ISO filesystem are pending. I am the developer of xorriso. So i am biased, of course. Be aware that Linux misrepresents Rock Ridge file names which are longer than 253 bytes. Length 254 and 255 should be supported but aren't. The truncation of names > 253 bytes is coarse and can discard more than 100 bytes from the file name's end. Have a nice day :) Thomas
