Rodrigo Ventura schrieb:
? gtar: ./mnt/cdrom: Cannot savedir: No such file or directory
? gtar: ./mnt/cdrom/: Warning: Cannot stat: No such file or directory
? gtar: ./mnt/cdrw: Cannot savedir: No such file or directory
? gtar: ./mnt/cdrw/: Warning: Cannot stat: No such file or directory
[...]
?
On Feb 27, 2008, at 4:12 PM, Jean-Louis Martineau wrote:
What's in the "FAILED AND STRANGE DUMP DETAILS" section of the
email report?
I found out, following a previous reply suggestion, errors like these:
/-- omni / lev 1 FAILED [dump (16333) /usr/bin/tar returned 2]
se
DUMP SUMMARY:
omni/ lev 1 FAILED [dump (30447) /usr/bin/tar
returned 2]
and I don't have a clue on what's going on. I grepped /tmp/amanda and
found no reference to this. Any clues?
Cheers,
Rodrigo Ventura
Institute for Systems and Robotics
(www.isr.ist.utl.pt)
Ins
On 2008-02-27 15:56, Rodrigo Ventura wrote:
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/ lev 1 FAILED [dump (30447) /usr/bin/tar
returned 2]
and I don't have a clue on what's going on. I grepped /tmp/amand
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/ lev 1 FAILED [dump (30447) /usr/bin/tar
returned 2]
and I don't have a clue on what's going on. I grepped /tmp/amanda and
found no reference to this. Any clues?
C
* Jon LaBadie <[EMAIL PROTECTED]> [20050824 17:08]:
> On Wed, Aug 24, 2005 at 02:59:03PM -0400, Jean-Francois Malouin wrote:
> > Hi,
> >
> > In the last few days I've been getting this error:
> >
> > [/usr/freeware/bin/tar returned 2]
>
>
On Wed, Aug 24, 2005 at 05:46:25PM -0400, [EMAIL PROTECTED] wrote:
>
> For UNIX systems, return code 2 is "No such file or directory" or "File not
> found",
>
> This information is found in the /usr/include/errno.h on most UNIX systems
>
Unix standards specify a zero ("0") exit status for succe
last error code encountered.
Hope that helps clarify the admittedly cryptic error messages.
Thanks,
Donald L. (Don) Ritchey
Information Technology
Exelon Corporation
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 4:08 PM
To: AMANDA
On Wed, Aug 24, 2005 at 02:59:03PM -0400, Jean-Francois Malouin wrote:
> Hi,
>
> In the last few days I've been getting this error:
>
> [/usr/freeware/bin/tar returned 2]
Return code (exit status) 2 seems, I think, to be reserved by tar
for non-fatal situations from w
Hi,
In the last few days I've been getting this error:
[/usr/freeware/bin/tar returned 2]
in the sendbackup report on a client running 2.4.4p3-20040805 and the
whole backup run fails. This is the system disk "/" on the client.
Anyone has run into this before?
The client
--On Thursday, June 23, 2005 12:01:05 -0400 Jon LaBadie <[EMAIL PROTECTED]>
wrote:
> On Thu, Jun 23, 2005 at 04:39:02PM +0100, Chuck Amadi Systems Administrator
> wrote:
>> Hi PB
>>
>> I reverted back to ./var, ./tmp as you So suggested and added ./media to
>> the exclude list.
>>
>> I run amd
--On Thursday, June 23, 2005 09:31:25 -0400 Jon LaBadie <[EMAIL PROTECTED]>
wrote:
> On Thu, Jun 23, 2005 at 01:03:13PM +0200, Paul Bijnens wrote:
>>
>> >> ? gtar: ./media/cdrom: Cannot savedir: No medium found
>> [...]
>> >>| gtar: ./var/spool/postfix/public/showq: socket ignored
>> >
>>
>> N
Hi Thanks for the advise
I will monitor as suggested but worth the voyager.
Cheers All
On Thu, 2005-06-23 at 12:01 -0400, Jon LaBadie wrote:
> ./var/tmp
> ./var/spool/postfix
> ./var/spool/cups
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Labor
On Thu, Jun 23, 2005 at 04:39:02PM +0100, Chuck Amadi Systems Administrator
wrote:
> Hi PB
>
> I reverted back to ./var, ./tmp as you So suggested and added ./media to
> the exclude list.
>
> I run amdump and It looks like it's working accordingly as per the Dump
> Summary.
Starting to look goo
Hi PB
I reverted back to ./var, ./tmp as you So suggested and added ./media to
the exclude list.
I run amdump and It looks like it's working accordingly as per the Dump
Summary.
Here's my output Sorry for the constant mails I now have a better
understanding on whats going on and by next week wil
On Thu, Jun 23, 2005 at 01:03:13PM +0200, Paul Bijnens wrote:
>
> >>? gtar: ./media/cdrom: Cannot savedir: No medium found
> [...]
> >>| gtar: ./var/spool/postfix/public/showq: socket ignored
> >
>
> Note that the error is not in the sockets (those lines are marked
> with a pipe-symbol as "normal"
Hi
Great News
I have included the ./media or be it ./media/cdrom and ./media/floppy I
will use the simpler format and run the amdump.
Cheers
Chuck
On Thu, 2005-06-23 at 14:52 +0200, Paul Bijnens wrote:
> Chuck Amadi Systems Administrator wrote:
> > My fstab is as follows but when using Yast
Chuck Amadi Systems Administrator wrote:
My fstab is as follows but when using Yast and floppy I have had no
issues.
/dev/cdrom /media/cdrom subfs
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppysubfs
fs=floppyfss,procuid,nodev
Hi
I am using SuSE SLES 9,version Amanda 2.4.2 and /etc/fstab.
Very weired I just mounted a floppy and cdrom with no problems
So it is working.
Cheers
On Thu, 2005-06-23 at 13:03 +0200, Paul Bijnens wrote:
> [EMAIL PROTECTED] wrote:
> >
> >>/-- server / lev 0 FAILED [/
Hello, Chuck,
on 23.06.2005, 12:35 you wrote to amanda-users@amanda.org:
> # Thus use exclusions for all those sockets? This would remove all
> # those nasty ignore-errors and No media found in the Report.
> ./dev
> ./tmp
> ./var
> ./media/cdrom
> ./media/floppy
> I assume the last five entries
rom subfs
fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppysubfs
fs=floppyfss,procuid,nodev,nosuid,sync 0 0
On Thu, 2005-06-23 at 13:03 +0200, Paul Bijnens wrote:
> [EMAIL PROTECTED] wrote:
> >
> >>/-- server / lev 0 FAILED
[EMAIL PROTECTED] wrote:
/-- server / lev 0 FAILED [/bin/tar returned 2]
sendbackup: start [greenbottle.smtl.co.uk:/ level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar
ks:
>
> >> Total bytes written: 5874155520 (5.5GB, 3.5MB/s)
>
> > USAGE BY TAPE:
> > Label Time Size %Nb
> > DailySet110 0:274212.7 21.6 1
>
> Seems you use the right tapetype now ...
>
> > F
gt;
> > USAGE BY TAPE:
> > Label Time Size %Nb
> > DailySet110 0:274212.7 21.6 1
>
> Seems you use the right tapetype now ...
>
> > FAILED AND STRANGE DUMP DETAILS:
>
> > /-- server / lev 0 FAILED [/bin/tar returned
> /-- server / lev 0 FAILED [/bin/tar returned 2]
> sendbackup: start [greenbottle.smtl.co.uk:/ level 0]
> sendbackup: info BACKUP=/bin/tar
> sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
>
ver: result time 1615.665 from dumper0: FAILED 01-2 [/bin/tar
returned 2]
Amanda Report below:
These dumps were to tape DailySet110.
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: DailySet101.
FAILURE AND STRANGE DUMP SUMMARY:
server / lev 0 FAILED [/
On Thu, 13 Mar 2003 at 9:53am, wab wrote
> It's obviously this I/O error that's causing the problem... the
> filesystem is 67 gig (df -k says 67108864 1048-K blocks). The other
> filesystems being backed up to the tape only are using 3-4% of tape
> capacity... and it's a DLT 40/80. The compression
wab wrote:
It's obviously this I/O error that's causing the problem... the
filesystem is 67 gig (df -k says 67108864 1048-K blocks). The other
filesystems being backed up to the tape only are using 3-4% of tape
capacity... and it's a DLT 40/80. The compression ratio seems like all
this should fit o
On Thu, 13 Mar 2003 at 9:47am, wab wrote
> It's AIX.
>
> So is this I/O error referring to writing to tape, or reading the file
> from disk? I'd much rather use tar than dump...
Reading from disk -- check the client's system logs.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Du
ge-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Bijnens
Sent: Thursday, March 13, 2003 5:04 AM
To: wab
Cc: [EMAIL PROTECTED]
Subject: Re: level 0 of huge filesystem not working (tar returned 2, and
the backup fails)
wab wrote:
> One filesystem I'm trying to back u
It's AIX.
So is this I/O error referring to writing to tape, or reading the file
from disk? I'd much rather use tar than dump...
-Original Message-
From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]
> ? gtar: Read error at byte 53808128, reading 10240 bytes, in file
> ./archive/www/acc
wab wrote:
One filesystem I'm trying to back up with AMANDA is really huge and I'm
encountering errors:
This filesystem is so huge, a level 0 is taking longer than 24 hours.
Any ideas on what could be going wrong? My best guesses:
1. The filesystem is just too big for TAR.
No, at the end of the tar
best guesses:
>
> 1. The filesystem is just too big for TAR.
> 2. The filesystem is so big, its contents are changing during the tar
> process and confusing it or amanda.
No I don't think this is the situation.
> /-- /usr lev 0 FAILED [/usr/local/bin/tar returned 2]
>
s (no
compression). Of course, that Linux server is rather fast.
> /-- /usr lev 0 FAILED [/usr/local/bin/tar returned 2]
> sendbackup: start [:/usr level 0]
> sendbackup: info BACKUP=/usr/local/bin/tar
> sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar
o big, its contents are changing during the tar
process and confusing it or amanda.
/-- /usr lev 0 FAILED [/usr/local/bin/tar returned 2]
sendbackup: start [:/usr level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/
On Fri, Jan 10, 2003 at 10:59:01AM -0500, wab wrote:
> what does this mean? (not that familiar with tar)
It is amanda telling you that tar failed.
Somewhere earlier, or in the /tmp/amanda debug files,
would be output from tar about why it was unhappy.
--
Jon H. LaBadie [EMAIL P
what does this mean? (not that familiar with tar)
wab
On Wed, Feb 27, 2002 at 12:51:33PM -0500, Chris Dahn wrote:
> On Monday 25 February 2002 11:29 am, Carl Wilhelm Soderstrom wrote:
> > due to permission problems, we've had repeated cases of tar returning error
> > message '2', even tho amanda uses the --ignore-failed-read option (tar
> > 1.3.25).
On Wed, Feb 27, 2002 at 12:51:33PM -0500, Chris Dahn wrote:
> On Monday 25 February 2002 11:29 am, Carl Wilhelm Soderstrom wrote:
> > due to permission problems, we've had repeated cases of tar returning error
> > message '2', even tho amanda uses the --ignore-failed-read option (tar
> > 1.3.25).
On Monday 25 February 2002 11:29 am, Carl Wilhelm Soderstrom wrote:
> due to permission problems, we've had repeated cases of tar returning error
> message '2', even tho amanda uses the --ignore-failed-read option (tar
> 1.3.25). as I understand it, amanda should still accept the backup data
> tha
> due to permission problems, we've had repeated cases of tar returning error
> message '2', even tho amanda uses the --ignore-failed-read option (tar
> 1.3.25). as I understand it, amanda should still accept the backup data that
> tar got, but it doesn't. it simply ignores the backup.
let me rep
due to permission problems, we've had repeated cases of tar returning error
message '2', even tho amanda uses the --ignore-failed-read option (tar
1.3.25). as I understand it, amanda should still accept the backup data that
tar got, but it doesn't. it simply ignores the backup.
is there an option
42 matches
Mail list logo
