Hi,
yeah, this "$Delano" looked wrong. (Unless you have set
)
Without such preparation, "$Delano" is evaluated by the shell as empty
text. I.e. you effectively told xorriso
Code:
-map /files /files1
and the path "/files" does not exist on your hard disk.
"HOME" is a variable which is predefined by the command shell:
Code:
$ echo "$HOME"
/home/thomas
> xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0% 0.0xD
> xorriso : UPDATE : Thank you for being patient. Working since 20 seconds.
> ISO image produced: 28 sectors
> Written to medium : 192 sectors at LBA 32
> Writing to '/dev/sr0' completed successfully.
That's a very small burn job. 28 blocks of payload, 150 blocks of padding,
rounded up to full multiples of 16 = 192.
The start block 32 lets room for a main superblock, which will direct
readers to the root directory of the youngest session. That's a preparation
for multi-session which xorriso does on formatted media. On a sequential
medium the start LBA would be 0, because those media maintain their own
table of content which marks the written sessions.
You may now add more sessions to the medium. Just use -dev instead of
-outdev in order to let xorriso read the previous directory tree and learn
the next writable block address. Do not use -blank "as_needed" unless you
want to invalidate the previous sessions and start a new series of sessions.
----------------------------------------------------------------------
The most elaborate way of doing multi-session is shown as example in
man xorriso. This is how i make daily incremental backups:
Code:
xorriso \
-abort_on FATAL \
-for_backup -disk_dev_ino on \
-assert_volid 'PROJECTS_MAIL_*' FATAL \
-dev /dev/sr0 \
-volid PROJECTS_MAIL_"$(date '+%Y_%m_%d_%H%M%S')" \
-not_leaf '*.o' -not_leaf '*.swp' \
-update_r /home/thomas/projects /projects \
-update_r /home/thomas/personal_mail /personal_mail \
-commit -toc -check_md5 FAILURE -- -eject all
-abort_on "FATAL" sets a high limit for program abort. Only events of
severity "FATAL" will cause xorriso to abort.
-for_backup enables recording of checksums and possibly present file
attributes like ACL.
-disk_dev_ino "on" speeds up the comparison of disk state and backup state.
It depends on stable device and inode numbers on hard disk. (If each backup
update copies all files, then those numbers are not stable enough. Omit
the command -disk_dev_ino in this case. Comparison will just be slower then.)
-assert_volid shall recognize if you have inserted the wrong DVD. It checks
whether the found Volume Id looks like the one which will be set by the
-volid command. (It also accepts blank DVD without any Volume Id.)
-dev reads the existing filesystem info and opens the drive for writing.
-volid PROJECTS_MAIL_"$(date '+%Y_%m_%d_%H%M%S')" sets the Volume Id to
a text like PROJECTS_MAIL_2020_01_22_092016. Here the shell calls program
"date" with formatted output to generate the timestamp "2020_01_22_092016".
-not_leaf '*.o' excludes files which are produced by the C compiler and
used by the linker to produce executable programs. They get rebuilt often
and are of no permanent use.
-not_leaf '*.swp' excludes the swapfiles of the text editor "vim". They
exist only as long as vim is operating on the file with the same name but
without ".swp". They should not be backuped, because vim believes to see
a crash site when it encounters them at start of a text editinng session.
-update_r compares a directory tree on hard disk with a tree in the ISO.
It performs the necessary xorriso actions which make the ISO tree a true
copy of the tree on the hard disk. I.e. files get added to the ISO, deleted
from it, or get their file properties changed.
-commit starts the burn run.
-toc afterwards shows the new session list.
-check_md5 "FAILURE" "--" does a checkread run of the newest session, looking
for i/o errors or for mismatches of the recorded MD5 checksums.
-eject "all" finally lets the tray move out. (If not FATAL error occured
before which would have aborted the program run.)
I run this daily, until the medium is full. When full, i put it on the
shelf for a few months and use a blank medium to start a new session
series. When i want to re-use such full media, i run xorriso with command
-blank "as_needed".
My backup-worthy storage area has about 4.5 GB.
Normally i use BD-RE media for backups, because they take up to 25 GB.
One of my backup strains is on DVD+RW, though, using zisofs compression
which reduces the full backup size to about 2.5 GB. So i can add about
20 sessions before the medium is full.
Have a nice day
Thomas
Midia Check
