I have been looking into making backups of personal files that can be put in a closet and forgotten about for years without worrying about disk failure or bit rot, and it seems that HTL BD-R's are the way to go.
I have a folder that contains files that I would like to back up. Every once in a while, some of these files may get updated or new files may be added, and I would like those to be backed up. But BD-R's are write-once media.
If I understand correctly, the UDF filesystem supports writing modifications and new files on write-once media using Virtual Allocation Tables. Since UDF seems pretty well supported across operating systems, I would like to take advantage of this for this particular usecase.
On Linux, I attempted to simulate a format a BD-R as UDF using the following command:
$ mkudffs -l Test -m bdr -n --vat /dev/sr0
Note: Not writing to device, just simulating
filename=/dev/sr0
label=Test
uuid=66f5a2c157e54521
blocksize=2048
blocks=1
udfrev=2.50
mkudffs: Error: Not enough blocks on device
First I was surprised to see that it complained about not having enough blocks. So I decided to remove the -n (simulate) parameter and just see what happens:
$ mkudffs -l NewHouse -m bdr --vat /dev/sr0
mkudffs: Error: Cannot open device '/dev/sr0': Read-only file system
At this point, I'm not sure what I'm doing wrong. Any pointers? And is my understanding of UDF with regards to write-once media correct? And in general, is this approach a good idea? Would a BD-RE make more sense here?