Re: Strange dump error
Paul Lussier wrote: > > In a message dated: Mon, 26 Nov 2001 22:58:35 +0100 > "Bernhard R. Erdmann" said: > > >Doublecheck /etc/fstab for this entry. Dump gets the corresponding block > >device to the filesystem in the disklist by looking at /etc/fstab. > > Hmmm, does that mean that if there's not an fstab entry that there > will be problems? No. You just use the block device in Amanda's disklist.
Re: Strange dump error
On Tue, 27 Nov 2001, Paul Lussier wrote: > Hmmm, does that mean that if there's not an fstab entry that there > will be problems? In my experience, yes. > Maybe I should re-write the disklist to contain the block device > instead of the filesystem names instead? Might work, I don't know. You could either a) try it, b) read the source, or c) hope someone else here knows. -Mitch
Re: Strange dump error
In a message dated: Mon, 26 Nov 2001 22:58:35 +0100 "Bernhard R. Erdmann" said: >Doublecheck /etc/fstab for this entry. Dump gets the corresponding block >device to the filesystem in the disklist by looking at /etc/fstab. Hmmm, does that mean that if there's not an fstab entry that there will be problems? Some of these file systems may or may not be physically present, since this is a cluster and they may have migrated to the other node. Therefore the cluster software manages which filesystems are mounted at boot time, and as such, they are not entered into /etc/fstab. Maybe I should re-write the disklist to contain the block device instead of the filesystem names instead? -- Seeya, Paul God Bless America! ...we don't need to be perfect to be the best around, and we never stop trying to be better. Tom Clancy, The Bear and The Dragon
Re: Strange dump error
> Anyone seen this error before? I just started getting it this > weekend, and can't figure out why. To my knowledge nothing has > changed on this system. > > /-- hacluster1 /var/sysmon/users lev 0 FAILED [/sbin/dump returned 1] > sendbackup: start [hacluster1:/var/sysmon/users level 0] > sendbackup: info BACKUP=/sbin/dump > sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... - > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > | DUMP: You can't update the dumpdates file when dumping a subdirectory > | DUMP: The ENTIRE dump is aborted. > sendbackup: error [/sbin/dump returned 1] > \ > > The disklist entry for this system is: > > hacluster1 /var/sysmon/users comp-root-always-full > > And this is a filesystem, not a subdirectory: > > hacluster1:~# df /var/sysmon/users/ > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/sdc3 20161204 2604744 16532320 14% /var/sysmon/users Doublecheck /etc/fstab for this entry. Dump gets the corresponding block device to the filesystem in the disklist by looking at /etc/fstab.
Strange dump error
Hi all, Anyone seen this error before? I just started getting it this weekend, and can't figure out why. To my knowledge nothing has changed on this system. /-- hacluster1 /var/sysmon/users lev 0 FAILED [/sbin/dump returned 1] sendbackup: start [hacluster1:/var/sysmon/users level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | DUMP: You can't update the dumpdates file when dumping a subdirectory | DUMP: The ENTIRE dump is aborted. sendbackup: error [/sbin/dump returned 1] \ The disklist entry for this system is: hacluster1 /var/sysmon/users comp-root-always-full And this is a filesystem, not a subdirectory: hacluster1:~# df /var/sysmon/users/ Filesystem 1k-blocks Used Available Use% Mounted on /dev/sdc3 20161204 2604744 16532320 14% /var/sysmon/users Any ideas? Thanks, -- Seeya, Paul God Bless America! ...we don't need to be perfect to be the best around, and we never stop trying to be better. Tom Clancy, The Bear and The Dragon
Re: strange dump error
>so the tape for tonight instead of 09, it jumps to 10. And this is >happening quite often lately so I can't predict which tape to go in next >and have to rely on the report. So I guess my question would be is there a >way to by pass certain directories, eg. the mail queue, ? Tape order and excluding directories are unrelated issues AFAIK. One depends on the order you used to label your tapes and first use them. At some time you skipped tape 9 and it got un-ordered. You could label your tapes blue, red, violet and green, there is no numbering of the tapes. Excluding file or directories is possible, it is documented. Olivier
Re: strange dump error
Hi Oliver, That is what I thought too. However, the tape number jump to different number of tape instead of the usual. For instance, in this case in the report: === These dumps were to tape Datapark08. Tonight's dumps should go onto 1 tape: Datapark10. === so the tape for tonight instead of 09, it jumps to 10. And this is happening quite often lately so I can't predict which tape to go in next and have to rely on the report. So I guess my question would be is there a way to by pass certain directories, eg. the mail queue, ? thanx, Jean At 08:20 AM 7/4/2001 +0700, you wrote: > >? gtar: Cannot add file ./var/spool/mqueue/xfMAA07342: No such file or > >directory > >| Total bytes written: 2192885760 > >When tar builkd the directory, the file was present, when it came to >back-up the file, it was not anymore, the mail had been sent and >removed from the queu. > >It is normal, just a warning. > >Olivier
Re: strange dump error
>These dumps were to tape Datapark08. >Tonight's dumps should go onto 1 tape: Datapark10. >... >so the tape for tonight instead of 09, it jumps to 10. And this is >happening quite often lately so I can't predict which tape to go in next >and have to rely on the report. ... Your tapelist file probably got out of order. If you are certain Datapark09 does not have any valid images on it and you want to use it next, hand edit the tapelist file, move that entry to the bottom of the file and give it the same datestamp as the next to last entry (which should be Datapark10). When you're done, test it with: amadmin tape You might want to save a copy of the tapelist file before you edit it just in case things go wrong :-). >So I guess my question would be is there a >way to by pass certain directories, eg. the mail queue, ? See the "exclude" and "exclude list" dumptype options. >Jean John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: strange dump error
>? gtar: Cannot add file ./var/spool/mqueue/xfMAA07342: No such file or >directory >| Total bytes written: 2192885760 When tar builkd the directory, the file was present, when it came to back-up the file, it was not anymore, the mail had been sent and removed from the queu. It is normal, just a warning. Olivier
strange dump error
Hi All, I am very new to this. So if the question I ask has been answered before, please bare with me and point me to the right direction. My problem is a "strange dump" error which seemed to occur more and more often. I think I know what the problem is but not know how to fix it or work around it. Here is the report from Amanda: === These dumps were to tape Datapark08. Tonight's dumps should go onto 1 tape: Datapark10. FAILURE AND STRANGE DUMP SUMMARY: freeway.da /dev/sda2 lev 0 STRANGE STATISTICS: Total Full Daily Dump Time (hrs:min) 1:06 0:33 0:00 (0:02 start, 0:31 idle) Output Size (meg) 1054.3 1054.3 0.0 Original Size (meg) 2091.3 2091.3 0.0 Avg Compressed Size (%) 50.4 50.4 -- Tape Used (%) 17.6 17.6 0.0 Filesystems Dumped 1 1 0 Avg Dump Rate (k/s) 617.2 617.2 -- Avg Tp Write Rate (k/s) 552.1 552.1 -- FAILED AND STRANGE DUMP DETAILS: /-- freeway.da /dev/sda2 lev 0 STRANGE sendbackup: start [freeway.datapark.com:/dev/sda2 level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/local/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Cannot add file ./var/spool/mqueue/xfMAA07342: No such file or directory | Total bytes written: 2192885760 sendbackup: size 2141490 sendbackup: end \ NOTES: driver: WARNING: /dump/data: 3072000 KB requested, but only 2790624 KB available. planner: Last full dump of freeway.datapark.com:/dev/sda2 on tape Datapark10 overwritten in 1 run. taper: tape Datapark08 kb 1079616 fm 1 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- -- freeway.d /dev/sda2 0 2141490 1079584 50.4 29:09 617.2 32:35 552.1 (brought to you by Amanda version 2.4.1) === I think the file that it can't find is a sendmail file. After the message is being sent, it will delete that file. So of course it is not there.Is there a way that I can by pass a certain directory so that it won't back up the temporary files? thanx. Jean
