Edit and Summary: Brasero refuses disk-images as too big, while they are not. It accepts an image of 4.2G, then reports xxx M of 4000M written during the burn-process. If you choose an image of 4700M (not 4.7G), it still is too big for Brasero. This is probably a bug in the software.

Good morning.

So, I thought I will create a 4700M big LUKS-encrypted iso-image to burn on DVD. Note, that I corrected this from 4.7G to 4700M. I did not make the error to provide a 4812M big container!

See screen shot for trouble: The directory that I am backing-up contains 4.3G of data, but the iso-image is of 4.8G and thus too big.

The same happens with a slightly smaller container (truncate -s 4600M).

Now I am limiting the iso-image to 4G to be sure. Brasero still reports 4.2G. Is the encryption responsible for the gain in size of the iso-image?

Sorry for the language. At least it is not German, this time.

Attached Thumbnails

 

you may pay attention to

https://en.wikipedia.org/wiki/Mebibyte

this is what i expect: 1 MiB = 220 bytes = 1024 kibibytes = 1048576bytes

harddrive manufactueres are idiots who use 1000 insteadof 1024. so you have the fuss with MIB vs MB, same goes for GB vs GIB and so on

I think same is for those worm media (write once .... e.g. DVD / CDR and such)

You did not read my above post
.