Copyright (C) 2012 by Steve Litt, All rights reserved. Material provided as-is, use at your own risk.
truncate --size=25GB /bigdisk/mybr.udf
sudo mount -oloop,rw /bigdisk/mybr.udf /mnt/test
sudo chown slitt.slitt /mnt/test
/bigdisk/mybr.udf /mnt/test udf loop,noauto,user,noatime,nodiratime 0 0Looking at the option list, loop means you're mounting a file, not a device -- it's a loopback mount. noauto means it won't automatically mount on boot -- you don't want that happening. user means an ordinary user, like you, can mount it, and once mounted, only that same user can unmount it. noatime and nodiratime mean that access times aren't recorded, reducing disk writes and situations where rsync re-copies because the access time made it think there was a change. The 0 on the end means don't fsck check it -- you're probably going to be recreating the filesystem each time -- it's a lot faster than mass deletion.
mount /bigdisk/mybr.udfand unmounting will be:
umount /mnt/testNeither requires sudo because you used the user option in /etc/fstab. Note that the umount command must use the mountpoint, not the UDF file, as its argument. If you'd used the UDF file as its argument, it would have refused on the ground that "/dev/loop0 is not in the fstab". Likewise, don't use the mountpoint in the mount command, in case you have two devices that can mount to the same mountpoint. For instance, after you're all done making the UDF file, you could mount the Blu-Ray recorder to that same mountpoint to accuracy-check your recording.
growisofs -speed=1 -Z /dev/dvd=/bigdisk/mybr.udfBe sure /bigdisk/mybr.udf isn't mounted when you do this: You're using it as a Blu-Ray image, not as a filesystem. If you have Blu-Ray media that are known to perform well at elevated speeds, you can use a higher speed. This document is being written in 2012. In a few years Blu-Ray media will record at higher speeds, but for now, if you have no-name Blu-Rays, use a speed of 1.
sudo ./verify_disc bluray_device mountpointThe script iterates through every .md5 file on the mountpoint, and for each one it does an md5sum on the corresponding .tgz file. If their signatures match, the file's OK, otherwise it has problems. A log file is created (be sure to change this log file location to something relevant to your computer).