So I back up the installation of that Other OS by basically creating a
partition image and compressing it with bzip2 (note: bzip2's output is
less than 2% smaller than gzip's, but it takes MUCH longer to create). A
13 GB partition compressed to 8G. I split into two chunks, each slightly
smaller than a DVD. Then I find out the hard way that isofs can't handle
files >2GB. Duh; I knew that. A little "split" action later, and I have:
DVD 1:
2.0G hda1.bz2.1 2.0G hda1.bz2.2 106M hda1.bz2.3
DVD2:
2.0G hda1.bz2.4 1.9G hda1.bz2.5
I used 'mkisofs -iso-level 3 -J -l -pad -R -o /mnt/temp/backup-1.iso .' to
create the ISOs:
4.2G /mnt/temp/backup-1.iso 3.9G /mnt/temp/backup-2.iso
Burning seems to go as usual. But, when I look at the result:
[eben@pc backup-1]$ ls /mnt/dvd2
total 0
0 ?????????????????????????????????????????????????????/
But the ISO has the correct names:
[root@pc root]# mount /mnt/temp/backup-1.iso /dvd2b/test -o loop,ro
hda1.bz2.1 hda1.bz2.2 hda1.bz2.3
everything looks OK. Reading works:
[root@pc root]# sum /scratch/backup-1/hda1.bz2.3 /dvd2b/test/hda1.bz2.3
26826 108544 /scratch/backup-1/hda1.bz2.3
26826 108544 /dvd2b/test/hda1.bz2.3
What could be the problem here? /scratch and /mnt/temp are both reiserfs
--
-eben ebQenW1@EtaRmpTabYayU.rIr.OcoPm home.tampabay.rr.com/hactar
This message was created using recycled electrons.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:02:14 EDT