if you don't like it remove that parameter from the $tarOptions and addman tar wrote:--totals
print total bytes written with --create
Code: Select all
du -sch $stage4Name.$stage4postfixif you don't like it remove that parameter from the $tarOptions and addman tar wrote:--totals
print total bytes written with --create
Code: Select all
du -sch $stage4Name.$stage4postfixCode: Select all
./mkstage4.sh -v -sCode: Select all
Best (tar.bz2):
(4) Interactive backup (added some small folders in the /home seperate partition, including /smb for samba)And I supposed that the stage4 creation is successfull, my root partition got 300M left, but I suppose it is still not quite running out of space.3840215040 (3.6GiBï¼1.1MiB/s)
* stage4 is done
* umounting boot
* Checking integrity
* Integrity check failed. Re-run the script and che
Code: Select all
echo "* md5sum archive: `md5sum $stage4Name.$stage4postfix`"hello dundas.
echo "* md5sum archive: `md5sum $stage4Name.$stage4postfix`"
this is just meant to be added to the script if you want to do a md5sum each time you run the script. an md5sum doesn't tell you if your stage4 has been built correctly - it just helps to verify upon burning and copying the stage4 if it is still the same as the original.
to test your stage4 manually execute (replace stage4name with your actual stage4 path):
cat stage4name.tar.bz2_* > stage4name.tar.bz2
# bzip2 --test stage4name.tar.bz2
or
# tar -tvf filename.tar.bz2
after discussing wiz them, and googling, we believe this is just a trivial warning, and my stage4 was made successfully, thx to you all!bzip2: (stdin): trailing garbage after EOF ignored

no, that wouldn't do you any good. md5sum doesn't actually error check the file itself: it just gives you a value based on some sort of algorithm ran against the file's binary value. this is good for ensuring there was no corruption from a file transfer (as the file you received should be exactly the same as the original, and thus will have the same md5sum value).dundas wrote:and got the following ending errors:
And I supposed that the stage4 creation is successfull, my root partition got 300M left, but I suppose it is still not quite running out of space.3840215040 (3.6GiBï¼1.1MiB/s)
* stage4 is done
* umounting boot
* Checking integrity
* Integrity check failed. Re-run the script and che
So is there any way for me to manually check the integrity again?
--just add ?and then use md5sum to check it?Code: Select all
echo "* md5sum archive: `md5sum $stage4Name.$stage4postfix`"
Code: Select all
# tar -tvf filename.tar.bz2
yes. amd64 is compatible with x86 compiled binaries. in fact, if one wanted to use a pure 32bit environment on an Athlon 64, the recommendation would be to use -march=athlon-xp (there was a thread on this in the amd64 forum all about what CFLAGS and such to use).ktech wrote:A little bit of off-topic:
do you guys know if I can restore a backup made in an Athlon XP 32 Bits into an Athlon 64 computer? I think I'm using the most restrictive of -marc/-mcpu (don't remember why as I'm not in that computer). Are they "binary compatible"?
Once I restore my backup I'll be compiling all of my apps into 64 bits, but I don't know if the backup will be running after restored...

Code: Select all
/var/www/localhost/htdocs/the54.com-OLDSITE/modules/gallery/netpbm/ppmtojpeg
sh: line 1: 8883 Broken pipe /usr/bin/find /* -path /dev -prune -o -path /lost+found -prune -o -path /mnt -prune -o -path /proc -prune -o -path /sys -prune -o -path /tmp -prune -o -path /usr/portage -prune -o -path /usr/src -prune -o -path /var/log -prune -o -path /var/tmp -prune -o -path /var/db -prune -o -path /var/cache/edb -prune -o -path /mnt/p4-camera -prune -o -path /home/ftp -prune -o -path /home/funkoolow -prune -o -path /home/funkweb -prune -o -path /home/t0mcat -prune -o -path /usr/src/linux-2.6.11-gentoo-r9 -prune -o -print
sh: line 1: 8843 Done(141) ( /usr/bin/find /var/db; echo /var/log/emerge.log; echo /usr/src; echo /usr/portage; echo /tmp; echo /sys; echo /proc; echo /mnt; echo /home; echo /dev/console; echo /dev/null; /usr/bin/find /usr/src/linux-2.6.11-gentoo-r9 -print; /usr/bin/find /home/t0mcat -print; /usr/bin/find /home/funkweb -print; /usr/bin/find /home/funkoolow -print; /usr/bin/find /home/ftp -print; /usr/bin/find /* -path /dev -prune -o -path /lost+found -prune -o -path /mnt -prune -o -path /proc -prune -o -path /sys -prune -o -path /tmp -prune -o -path /usr/portage -prune -o -path /usr/src -prune -o -path /var/log -prune -o -path /var/tmp -prune -o -path /var/db -prune -o -path /var/cache/edb -prune -o -path /mnt/p4-camera -prune -o -path /home/ftp -prune -o -path /home/funkoolow -prune -o -path /home/funkweb -prune -o -path /home/t0mcat -prune -o -path /usr/src/linux-2.6.11-gentoo-r9 -prune -o -print )
8845 Broken pipe | /bin/tar --bzip2 --preserve-permissions --create --absolute-names --totals --ignore-failed-read -v --file /mnt/p4-camera/funkserver-stage4-2005.07.17-custom.tar.bz2 --no-recursion -T -
* stage4 is done
* umounting boot
* Checking integrity
* Integrity check failed. Re-run the script and check your hardware.1. boot off a live-cd and repartition and create filesystems as necessary/dev/sda1 /boot
/dev/sda2 swap
/dev/sda3 /
/dev/sda4 /home
Code: Select all
# grub
grub> root (hd0,0) (since fedora /boot is on /sda1)
grub> setup (hd0) (still the mbr of the first hd)
grub> quit

Code: Select all
* mounting boot
Do you want to continue? (y/n) y
* Please wait while the stage4 is being created.
/bin/tar: /var/lib/dbus/system_bus_socket: socket ignorato
/bin/tar: /var/run/dbus/system_bus_socket: socket ignorato
/bin/tar: /var/run/acpid.socket: socket ignorato
/bin/tar: /var/run/xdmctl/dmctl/socket: socket ignorato
/bin/tar: /var/run/xdmctl/dmctl-\:0/socket: socket ignorato
Total bytes written: 2529454080 (2,4GiB, 2,9MiB/s)
* stage4 is done
* umounting boot
* Checking integrity
* Everything went smoothly. You successfully created a stage4.
Code: Select all
default_exclude_list="
...
/home/biter/.ut2004
/home/biter/.etwolf
...Code: Select all
/home/biter/.ut2004/
/home/biter/.ut2004/Cache/
/home/biter/.ut2004/Cache/0F0802C011D8FD9430000C8CB7637684-1.uxx
/home/biter/.ut2004/Cache/3ADC18814EB51B81C1B77E96E6F7CE63-1.uxx
/home/biter/.ut2004/Cache/C68430BC4794813072F223813183E4CA-1.uxx
/home/biter/.ut2004/Cache/8ECBE65540CF6B3C05930F841C17CC11-1.uxx
/home/biter/.ut2004/Cache/cache.ini
/home/biter/.ut2004/Cache/7492CDAD47C002364C6F408C429537FE-1.uxxCode: Select all
Cago-Ma3oxuct / # sh stage4-3.5.sh -v
Backup script v3.5
==================
What do you want to do? (Use CONTROL-C to abort)
Fast (tar.gz):
(1) Minimal backup
(2) Interactive backup
Best (tar.bz2):
(3) Minimal backup
(4) Interactive backup
Please enter your option: 2
Do you want to backup /home/biter? (y/n) y
Do you want to backup /home/common? (y/n) n
Do you want to backup /usr/src/linux-2.6.13-rc6? (y/n) y
* mounting boot
* creating the stage4 in /work/stage4-backups with the following command:
(/usr/bin/find /var/db; echo /var/log/emerge.log; echo /usr/src; echo /usr/portage; echo /tmp; echo /sys; echo /proc; echo /mnt; echo /home; echo /dev/console; echo /dev/null; /usr/bin/find /usr/src/linux-2.6.13-rc6 -print; /usr/bin/find /home/biter -print; /usr/bin/find /bin /boot /dev /etc /home /in /lib /mnt /opt /proc /root /sbin /stage4-3.5.sh /stage4.sh /sys /tmp /usr /var /work -path /home/common -prune -o -path /dev -prune -o -path /lost+found -prune -o -path /mnt -prune -o -path /proc -prune -o -path /sys -prune -o -path /tmp -prune -o -path /usr/portage -prune -o -path /usr/src -prune -o -path /var/log -prune -o -path /var/tmp -prune -o -path /var/db -prune -o -path /var/cache/edb -prune -o -path /opt/ut2004 -prune -o -path /opt/enemy-territory -prune -o -path /home/biter/.ut2004 -prune -o -path /home/biter/.etwolf -prune -o -path /in -prune -o -path /work -prune -o -path /work/stage4-backups -prune -o -path /home/biter -prune -o -path /home/common -prune -o -path /usr/src/linux-2.6.13-rc6 -prune -o -print) | /bin/tar --gzip --preserve-permissions --create --absolute-names --totals --ignore-failed-read -v --file /work/stage4-backups/Cago-Ma3oxuct-stage4-2005.08.17-custom.tar.gz --no-recursion -T -
Do you want to continue? (y/n) y


Code: Select all
original
-rw-r--r-- 1 root root 0 Oct 27 2004 .keep
lrwxr-xr-x 1 root root 31 Mar 21 13:24 linux -> /usr/src/linux-2.6.10-gentoo-r6
drwxr-xr-x 19 root root 4096 Mar 26 12:46 linux-2.6.10-gentoo-r6
drwxr-xr-x 18 root root 4096 Mar 26 22:15 linux-2.6.11-gentoo-r4
drwxr-xr-x 19 root root 4096 Mar 21 13:27 linux-2.6.9-gentoo-r1
Code: Select all
-rw-r--r-- 1 root root 0 Oct 27 2004 .keep
lrwxrwxrwx 1 root root 31 Aug 26 08:48 linux -> /usr/src/linux-2.6.10-gentoo-r6
drwxr-xr-x 18 root root 4096 Mar 26 22:15 linux-2.6.11-gentoo-r4
drwxr-xr-x 19 root root 4096 Mar 21 13:27 linux-2.6.9-gentoo-r1
