Re: Strange Dump Details
On Thu, 19 Aug 2010 09:47:01 +0530 Ranjan Das ranjan@ipsrsolutions.com wrote: Hi all, In my amanda backup mail report the following error is shown. STRANGE DUMP DETAILS: /-- station7.ipsrkochi.com /home/developer lev 1 STRANGE sendbackup: start [station7.ipsrkochi.com:/home/developer level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? /bin/tar: ./.gvfs: Warning: Cannot stat: Permission denied | /bin/tar: ./.config/google-chrome/SingletonSocket: socket ignored I see the same thing on Ubuntu. I've been ignoring it for a long time and had no problems. But then I don't have anything in the .gvfs directory. I believe it is part of the gnome virtual file system. The problem is in the permissions of .gvfs. It's a non-fatal error, as the dump summary will indicate. As for the Google Chrome socket, tar ignores sockets, and for good reason. I also ignore that. -- Charles Curley /\ASCII Ribbon Campaign Looking for fine software \ /Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com/ \No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Re: Strange Dump Details
Hi Charles Ok but i think that those files can be excluded somehow so that the report can be kept neat. How to add an exclude list? Thank You On Thu, Aug 19, 2010 at 6:02 PM, Charles Curley charlescur...@charlescurley.com wrote: On Thu, 19 Aug 2010 09:47:01 +0530 Ranjan Das ranjan@ipsrsolutions.com wrote: Hi all, In my amanda backup mail report the following error is shown. STRANGE DUMP DETAILS: /-- station7.ipsrkochi.com /home/developer lev 1 STRANGE sendbackup: start [station7.ipsrkochi.com:/home/developer level 1] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? /bin/tar: ./.gvfs: Warning: Cannot stat: Permission denied | /bin/tar: ./.config/google-chrome/SingletonSocket: socket ignored I see the same thing on Ubuntu. I've been ignoring it for a long time and had no problems. But then I don't have anything in the .gvfs directory. I believe it is part of the gnome virtual file system. The problem is in the permissions of .gvfs. It's a non-fatal error, as the dump summary will indicate. As for the Google Chrome socket, tar ignores sockets, and for good reason. I also ignore that. -- Charles Curley /\ASCII Ribbon Campaign Looking for fine software \ /Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com/ \No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Re: Strange Dump Details
Am 19.08.2010 15:01, schrieb Ranjan Das: How to add an exclude list? rtfm? http://wiki.zmanda.com/index.php/Exclude_and_include_lists
RE: Strange dump details
Is there any specific amanda developer list I could report this issue to? Thanks Nicklas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie Sent: den 17 juni 2005 02:14 To: amanda-users@amanda.org Subject: Re: Strange dump details On Thu, Jun 16, 2005 at 11:26:53PM +0200, Nicklas Bondesson wrote: I'm using amanda 2.4.5 to backup some Windows shares using amanda and smbclient. Everything went just fine until I upgraded Debian to the lastest stable (3.1). This upgrade went from Samba 2.2.3a to 3.0.14a. I now get this type of message on all of my Windows shares that I back up from amanda. FAILED AND STRANGE DUMP DETAILS: /-- ibiza //host/chare lev 0 STRANGE sendbackup: start [bakupserver://host/share level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? Domain=[DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] | tar: dumped 16 files and directories Total bytes written: 3689984 sendbackup: size 3604 sendbackup: end \ Backup programs like dump, tar, smbclient generate lots of messages that are informational fluff. Amanda has hard coded lists of things to not worry about. Others amanda knows to print error reports about. When one of the programs changes its fluff, sometimes even simple spacing changes, amanda may recognize the message as one to report as an error or ignore. These get reported as strange. Some future version of amanda will have adjusted for the samba changes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Strange dump details
Hello, Nicklas, on 16.06.2005, 23:26 you wrote to amanda-users@amanda.org: ? Domain=[DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Any ideas? Ignore it (it's not a problem) or browse the archives of this list for a patch that has been recently posted. Best regards, Stefan G. Weichinger. mailto://[EMAIL PROTECTED]
Re: Strange dump details
On Thu, Jun 16, 2005 at 11:26:53PM +0200, Nicklas Bondesson wrote: I'm using amanda 2.4.5 to backup some Windows shares using amanda and smbclient. Everything went just fine until I upgraded Debian to the lastest stable (3.1). This upgrade went from Samba 2.2.3a to 3.0.14a. I now get this type of message on all of my Windows shares that I back up from amanda. FAILED AND STRANGE DUMP DETAILS: /-- ibiza //host/chare lev 0 STRANGE sendbackup: start [bakupserver://host/share level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? Domain=[DOMAIN] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] | tar: dumped 16 files and directories | Total bytes written: 3689984 sendbackup: size 3604 sendbackup: end \ Backup programs like dump, tar, smbclient generate lots of messages that are informational fluff. Amanda has hard coded lists of things to not worry about. Others amanda knows to print error reports about. When one of the programs changes its fluff, sometimes even simple spacing changes, amanda may recognize the message as one to report as an error or ignore. These get reported as strange. Some future version of amanda will have adjusted for the samba changes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Strange dump details
--On Thursday, June 16, 2005 20:13:41 -0400 Jon LaBadie [EMAIL PROTECTED] wrote: Backup programs like dump, tar, smbclient generate lots of messages that are informational fluff. Amanda has hard coded lists of things to not worry about. Others amanda knows to print error reports about. When one of the programs changes its fluff, sometimes even simple spacing changes, amanda may recognize the message as one to report as an error or ignore. These get reported as strange. Some future version of amanda will have adjusted for the samba changes. Are there any plans to allow additional ignore patterns to be specified in the amanda.conf file so that they could be filtered out on the server side so as not to be reported as strange? Editing source code and recompiling seems like overkill. Frank -- Frank Smith[EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: STRANGE DUMP DETAILS
On Wed, 20 Nov 2002 at 9:54am, Mahidhar Kada wrote I am getting this error from past 2 days. What could be the problem? linux /dev/hda5 000 -- 0:000.0 35:46 554.8 driver: linux /dev/hda5 0 [dump to tape failed, will try again] FAILED AND STRANGE DUMP DETAILS: /-- linux /dev/hda5 lev 0 FAILED [data timeout] Is this an early 2.4 kernel? There are known (bad) interactions between early 2.4 kernels and old(er) versions of dump. Either a) upgrade to a recent kernel and the most recent version of dump/restore (available at http://dump.sourceforge.net) or b) switch to tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Strange dump details
Well, the weird thing is that I already replaced the hard drive once because I was thinking that it could only be a HD problem, but the problem still persists. What I also tryed is to do a manual dump on that machine and that works fine... So that sounds really strange... Any ideas ? Marc Ueda, To: [EMAIL PROTECTED] Yoshiakicc: [EMAIL PROTECTED] Subject: Re: Strange dump details om Sent by: [EMAIL PROTECTED] m 07/11/02 09:50 AM It isn't caused by amanda. It is hard drive problem. You have to try repair command at your drive, or replase hard drive. On Thu, 11 Jul 2002 09:32:15 +0200 [EMAIL PROTECTED] wrote: [cut] ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/hdc1: [block -909618816]: count=4096, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/hdc1: [sector -909618816]: count=512, got=0 [cut] Yoshiaki Ueda Cognex Corporation
Re: Strange dump details
Hm, just a wild guess: an active filesystem? Christoph [EMAIL PROTECTED] wrote: Well, the weird thing is that I already replaced the hard drive once because I was thinking that it could only be a HD problem, but the problem still persists. What I also tryed is to do a manual dump on that machine and that works fine... So that sounds really strange... Any ideas ? Marc Ueda, To: [EMAIL PROTECTED] Yoshiakicc: [EMAIL PROTECTED] Subject: Re: Strange dump details om Sent by: [EMAIL PROTECTED] m 07/11/02 09:50 AM It isn't caused by amanda. It is hard drive problem. You have to try repair command at your drive, or replase hard drive. On Thu, 11 Jul 2002 09:32:15 +0200 [EMAIL PROTECTED] wrote: [cut] ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: bread: lseek fails ? DUMP: short read error from /dev/hdc1: [block -909618816]: count=4096, got=0 ? DUMP: bread: lseek2 fails! ? DUMP: short read error from /dev/hdc1: [sector -909618816]: count=512, got=0 [cut] Yoshiaki Ueda Cognex Corporation
Re: strange dump details - (again)
Denise Ives wrote: My Amanda level 1 back-ups are failing consistanly on one of my drives. However there is small amounts of activity going on during the time amanda dump. Sometimes I have mtrg running in the background backing up files and folders - do you think that is the cause of these errors here? Maybe you want to dump ... | restore ... by hand to identify to files on fly and set the nodump-Flag onto them (chattr +d).
