Re: NOTES: big estimate
Jon, We also see 'big estimate' output for some partitions. I assumed some sort of bounding but never looked into it any further. Reminds me of the O (big-oh) and omega we'd compute for algorithms back in computer science class [upper and lower bounds limits for algorithms]. Something that I suspect is missing from more current programming classes. Brian On Tue, Mar 15, 2011 at 12:44:19PM -0400, Jon LaBadie wrote: My daily reports regularly contain lines like the following (commas added): NOTES: big estimate: lastchance Cdrive 1 est: 6,944,416Mout 975,940M big estimate: mumsxp Cdrive 1 est: 3,303,904Mout 288,480M big estimate: vostxp Cdrive 1 est: 1,902,400Mout 390,089M big estimate: vost Home 0 est: 17,729,952Mout 12,318,804M The first 3 are Windows partitions and are using ZWC on the clients. They always show up big. Others show up sporadically, but I can assure you my laptop vost does not have a 17 terrabyte drive :) Obviously these are KB, not MB as the units suffix suggests. But even adjusting for that, the estimates are way off. For example, 6.9GB reported in the above compared with 1.4GB dumped in the Summary below. DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-MB OUT-MB COMP% MMM:SS KB/s MMM:SS KB/s --- - lastchance Cdrive 1147095365 14:00 1162 0:45 21688 mumsxp Cdrive 1 66828242 57:34 84 0:12 24040 vostxp Cdrive 1 880381439:28686 0:17 22946 vost Home0 21726 1203055 105:22 1948 9:14 22236 Is anyone else seeing this? Jon -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive(703) 787-0884 Reston, VA 20194(703) 787-0922 (fax) --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: notes
On Wed, 2 Aug 2006, Frank Smith wrote: Glenn English wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The backup works and verifies, but the report says: planner: disk zbox.slsware.lan:/usr/bin, estimate of level 2 failed. planner: disk zbox.slsware.lan:/var, estimate of level 1 failed. planner: disk zbox.slsware.lan:/home, estimate of level 1 failed. planner: disk zbox.slsware.lan:/boot, estimate of level 1 failed. planner: disk zbox.slsware.lan:/, estimate of level 1 failed. for every DLE on this host. It does level 0s, so things get backed up. And it just started; I didn't change anything. Any explanations? Yes, you updated your packages and got tar 1.15.91, which changed something related to --listed-incremental. I believe there is a current snapshot of Amanda that addresses that issue, but you might want to just revert to a previous version of tar, as 1.15.91 also has an issue with using --one-file-system in conjunction with the --listed-incremental option that causes it to leak out of the base filesystem, Indeed. The only way to get my backups working again was downgrading to tar from sarge: apt-get install tar=1.14-2.2 Debian Linux, testing; VERSION=Amanda-2.5.0p2; installed by apt-get. This is the Amanda host; these DLEs are local disks. The hosts on the nets are fine. Does that first entry mean that the level 1 worked but the 2 didn't? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say programmer or something like that. -- Linus Torvalds
Re: notes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Geert Uytterhoeven wrote: Indeed. The only way to get my backups working again was downgrading to tar from sarge: apt-get install tar=1.14-2.2 That's exactly what I did 5 minutes after reading Frank Smith's reply. That fixed the incrementals. Now it says: /-- zbox.slsware.lan /boot lev 1 STRANGE sendbackup: start [zbox.slsware.lan:/boot level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end ? gtar: /var/lib/amanda/gnutar-lists/zbox.slsware.lan_boot_1.new:1: Invalid time stamp ? gtar: /var/lib/amanda/gnutar-lists/zbox.slsware.lan_boot_1.new:2: Invalid inode number | Total bytes written: 13301760 (13MiB, 5.1MiB/s) | gtar: Error exit delayed from previous errors sendbackup: size 12990 sendbackup: end \ And I just now tried to recover. It didn't work. Something's significantly bent here. A project for the afternoon... - -- Glenn English [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE0kQW04yQfZbbTLYRAvXIAJ9AlGX/6Db7kV9cuBoH9AYpwT+utwCgqmk7 RCfOY0x4RIMqb7n+XYWf7lA= =mjED -END PGP SIGNATURE-
Re: notes
On Thu, 3 Aug 2006, Glenn English wrote: Geert Uytterhoeven wrote: Indeed. The only way to get my backups working again was downgrading to tar from sarge: apt-get install tar=1.14-2.2 That's exactly what I did 5 minutes after reading Frank Smith's reply. That fixed the incrementals. Now it says: /-- zbox.slsware.lan /boot lev 1 STRANGE sendbackup: start [zbox.slsware.lan:/boot level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end ? gtar: /var/lib/amanda/gnutar-lists/zbox.slsware.lan_boot_1.new:1: Invalid time stamp ? gtar: /var/lib/amanda/gnutar-lists/zbox.slsware.lan_boot_1.new:2: Invalid inode number | Total bytes written: 13301760 (13MiB, 5.1MiB/s) | gtar: Error exit delayed from previous errors sendbackup: size 12990 sendbackup: end \ And I just now tried to recover. It didn't work. Something's significantly bent here. A project for the afternoon... The format for incrementals was changed in 1.15.91. While the new tar can probably read old incrementals, I guess the old tar can't read the new format. Probably I didn't suffer from the downgrade since all my level zero dumps were long overdue, and Amanda no longer wanted to do incrementals. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say programmer or something like that. -- Linus Torvalds
Re: notes
Glenn English wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The backup works and verifies, but the report says: planner: disk zbox.slsware.lan:/usr/bin, estimate of level 2 failed. planner: disk zbox.slsware.lan:/var, estimate of level 1 failed. planner: disk zbox.slsware.lan:/home, estimate of level 1 failed. planner: disk zbox.slsware.lan:/boot, estimate of level 1 failed. planner: disk zbox.slsware.lan:/, estimate of level 1 failed. for every DLE on this host. It does level 0s, so things get backed up. And it just started; I didn't change anything. Any explanations? Yes, you updated your packages and got tar 1.15.91, which changed something related to --listed-incremental. I believe there is a current snapshot of Amanda that addresses that issue, but you might want to just revert to a previous version of tar, as 1.15.91 also has an issue with using --one-file-system in conjunction with the --listed-incremental option that causes it to leak out of the base filesystem, Frank Debian Linux, testing; VERSION=Amanda-2.5.0p2; installed by apt-get. This is the Amanda host; these DLEs are local disks. The hosts on the nets are fine. Does that first entry mean that the level 1 worked but the 2 didn't? - -- Glenn English [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE0Q0E04yQfZbbTLYRAh9RAKCNXgsY1+6yuE+4Vzyv0RVBu3hOxgCeK9Y0 NSE0z9k0Qk8W6HG/DCXf26o= =w4hQ -END PGP SIGNATURE- -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501