Re: Holding disk size misread by amcheck
LaValley, Brian E wrote: I have a Fedora Core 3 amanda server. I have specified an nfs mounted directory for one of the holding disks. Does anyone know why amcheck finds much less space available on this drive than a command like 'df' does? You need to explain a little more. "amcheck" checks only for free space (at least 64K) n AMANDA_TMPDIR, AMANDA_DBGDIR, and /etc. "amcheck" does not check space on the disklist entries. Show the messages that make you that. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Holding disk size misread by amcheck
Paul Bijnens wrote: LaValley, Brian E wrote: I have a Fedora Core 3 amanda server. I have specified an nfs mounted directory for one of the holding disks. Does anyone know why amcheck finds much less space available on this drive than a command like 'df' does? You need to explain a little more. "amcheck" checks only for free space (at least 64K) n AMANDA_TMPDIR, AMANDA_DBGDIR, and /etc. "amcheck" does not check space on the disklist entries. Show the messages that make you that. Oops, following up on myself. Still no coffee here, only water. Holdingdisk is indeed checked by amcheck, sorry. Two remarks: NFS is usualy a bad choice for holdingdisk. Can your network feed the bytes to the tape at tapedrive speed? Calculate the bandwith needed for the incoming bytes too. If you cannot feed the bytes fast enough to a tapedrive, the drive needs to stop/rewind/restart frequently, loosing lots of capacity, time, and will need replacement very soon. About the stated capacity: could it be you're somewhere in the terabytes of free space, and you're overflowing a 32bit long (size in KB used inside amanda)? Showing the exact output of the commands still helps a lot. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Problem with backup of windows shares
--- Paul Bijnens <[EMAIL PROTECTED]> a écrit : > tanguy yoann wrote: > > >>Perhaps on the one system something other than > >>amanda/samba > >>prevents (or causes) this archive bit to flip. > That > > You need administrator privilege on the PC to be > able > to reset the archive bit. (At least I think so. > Great ignorance of ms windows here too :-) > > > >>would > >>be analogous to "touch"ing a file on a unix system > >>and > >>making the file look like it needs backup. > > > > > > Yes, amanda use the bit archive to know who data > > backup. I have a problem with some shares but I > can't > > know the value of the archive bit of these shares. > I > > don't know how I can do ? > > > smbclient '//pc/share' -U ... -W ... > password: . > > smb: \> dir > ... >Documents and Settings D 0 Tue May 6 > 07:04:56 2003 >Program Files DR 0 Tue May 6 > 07:05:44 2003 >CONFIG.SYS H 0 Tue May 6 > 16:19:58 2003 >AUTOEXEC.BAT H 0 Tue May 6 > 16:19:58 2003 >IO.SYS AHSR 0 Tue May 6 > 16:19:58 2003 >MSDOS.SYS AHSR 0 Tue May 6 > 16:19:58 2003 > > The "A" in the flags column is the archive bit. > > Verify if the "archive bit" is cleared after you did > a level 0 backup. > Indeed, in one of my share, the archive bit is cleared after a full backup, and in the other, it isn't cleared. I don't understand why. There is the same files in the two shares. It's very strange. The same user access with smclient at the two shares. Regards. Yoann, TANGUY Student at ESINSA Sophia-Antipolis ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com
Re: Problem with backup of windows shares
tanguy yoann wrote:
Indeed, in one of my share, the archive bit is cleared
after a full backup, and in the other, it isn't
cleared. I don't understand why. There is the same
files in the two shares. It's very strange.
The same user access with smclient at the two shares.
"smclient": command not found :-)
Are it two share on the same PC?
Is one share shared as readonly?
Does the smbclient user has full access to the share and
the files in it? I add that user to the "Local Administrators".
Can you invoke the smbclient command manually using verbose debugging
mode? You can find the command in the sendbackup.*.debug files in
the AMANDA_DBGDIR directory ("amadin xx version" shows that value).
Level 0 backup are done like:
smbclient //pc/share -U user -W wrkgrp -E -d0 -Tqca arch.tar
Change the debug level -d0 to -d3 or even more,
and maybe leave out the "q" flag after -T (not quiet).
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
RE: Holding disk size misread by amcheck
Good point, my tape drive maximum sustained data transfer rate is 60 MBytes per second on a Gigabit ethernet network. Is that too slow? Amcheck produces: Amanda Tape Server Host Check - WARNING: holding disk /backup/amanda/dumps/dump2: only 88344348 KB free (104857600 KB requested) WARNING: holding disk /backup/amanda/: only 8842796 KB free (26214400 KB requested) amcheck-server: slot 0: date Xlabel DailySet1-A00 (new tape) NOTE: skipping tape-writable test Tape DailySet1-A00 label ok Server check took 690.657 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.063 seconds, 0 problems found (brought to you by Amanda 2.4.4p2) The NFS mount is /backup/amanda/dumps/dump2. "df" produces: Filesystem 1K-blocks Used Available Use% Mounted on jhaas-l:/native/amanda 207955672 25107104 172285032 13% /backup/amanda/dumps/dump2 So in reality, there is 172GB free and Amanda only sees 88GB free. What is the 32 bit long size you mention in amanda? -Original Message- From: Paul Bijnens [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 4:20 AM To: LaValley, Brian E Cc: Amanda (E-mail) Subject: Re: Holding disk size misread by amcheck Paul Bijnens wrote: > LaValley, Brian E wrote: > >> I have a Fedora Core 3 amanda server. I have specified an nfs mounted >> directory for one of the holding disks. Does anyone know why amcheck >> finds >> much less space available on this drive than a command like 'df' does? >> > > You need to explain a little more. "amcheck" checks only for > free space (at least 64K) n AMANDA_TMPDIR, AMANDA_DBGDIR, and /etc. > "amcheck" does not check space on the disklist entries. > Show the messages that make you that. > Oops, following up on myself. Still no coffee here, only water. Holdingdisk is indeed checked by amcheck, sorry. Two remarks: NFS is usualy a bad choice for holdingdisk. Can your network feed the bytes to the tape at tapedrive speed? Calculate the bandwith needed for the incoming bytes too. If you cannot feed the bytes fast enough to a tapedrive, the drive needs to stop/rewind/restart frequently, loosing lots of capacity, time, and will need replacement very soon. About the stated capacity: could it be you're somewhere in the terabytes of free space, and you're overflowing a 32bit long (size in KB used inside amanda)? Showing the exact output of the commands still helps a lot. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Holding disk size misread by amcheck
LaValley, Brian E wrote:
Good point, my tape drive maximum sustained data transfer rate is 60 MBytes
per second on a Gigabit ethernet network. Is that too slow?
Maybe. Maybe not.
Those modern drives sometimes (usually) slow down their motors when
the bytes do not flow in fast enough, so that they keep streaming, but
only at a lower speed.
Even gigabit ethernet cannot do 120 Mbytes/sec, or 60MB/sec full duplex.
To find out how amanda gets the numbers, you may download the sources
of amanda, do a complete configure and compile ("make install" not
needed), and create a little standalone program "statfs", like this:
$ ./configure --with-user=... etc. (not necessary to get
everyting completely correct, you don't
need to do a "make install"; compile should
succeed, of course)
$ make
$ cd common-crc
$ make statfs
And now run the standalone "statfs" on those filesystems.
It will show what kind of statfs call it uses, and the values of
the different fields the OS gives back.
e.g.
$ /tmp/quick/amanda-2.4.5/common-src/statfs .
statfs (SVR4 (Irix-5+, Solaris-2, Linux glibc 2.1))
name totalfree avail files ffree favail
--- --- --- --- -- -- --
. 129015488 83820512 77266912 16384000 16137345 16137345
As you can see, there is sometimes a difference between "free" and
"avail". I'm not sure why... probably the reserved space in the
filesystem. Amcheck uses the "avail" value.
My "df" is consistent:
$ df -k .
Filesystem 1k-blocks Used Available Use% Mounted on
xlate:/space/tm 129015488 45194976 77266912 37% /net/xlate/tm
Amcheck produces:
Amanda Tape Server Host Check
-
WARNING: holding disk /backup/amanda/dumps/dump2: only 88344348 KB free
(104857600 KB requested)
WARNING: holding disk /backup/amanda/: only 8842796 KB free (26214400 KB
requested)
amcheck-server: slot 0: date Xlabel DailySet1-A00 (new tape)
NOTE: skipping tape-writable test
Tape DailySet1-A00 label ok
Server check took 690.657 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.063 seconds, 0 problems found
(brought to you by Amanda 2.4.4p2)
The NFS mount is /backup/amanda/dumps/dump2. "df" produces:
Filesystem 1K-blocks Used Available Use% Mounted on
jhaas-l:/native/amanda 207955672 25107104 172285032 13%
/backup/amanda/dumps/dump2
So in reality, there is 172GB free and Amanda only sees 88GB free.
What is the 32 bit long size you mention in amanda?
Amanda internally uses a signed 32bit long, which holds the size
in units of 1 Kbyte. That means such variable can hold values
up to 1024 * 2^31 bytes, or about 2 TByte.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
amanda timeouts and weirdness solved!
So, you guys may recall I was having problems with amcheck and amdump taking ridiculously long. Well, it turns out that because on that client box, there was a dead Samba mount. As you guys know, when there's a Samba mount that's timed out, or the remote machine is unavailable, any operation checking mounted partitions takes forever and eventually times out. So... what in Amanda is checking mounted partitions on every operation, and can we limit to only the partitions we're actually backing up? :) Graeme -- Graeme Humphries ([EMAIL PROTECTED]) (306) 955-7075 ext. 485 My views are not the views of my employers.
Re: amanda timeouts and weirdness solved!
--On Wednesday, August 24, 2005 10:11:04 -0600 Graeme Humphries <[EMAIL PROTECTED]> wrote: > So, you guys may recall I was having problems with amcheck and amdump taking > ridiculously long. Well, it turns out that because on that client box, there > was a dead Samba mount. As you guys know, when there's a Samba mount that's > timed out, or the > remote machine is unavailable, any operation checking mounted partitions > takes forever and eventually times out. > > So... what in Amanda is checking mounted partitions on every operation, and > can we limit to only the partitions we're actually backing up? :) I don't think Amanda checks all your mounts. However, many filesystem operations 'stat' their way up the directory structure to /, and if you mount things directly in / (such as /remotedir) instead of down a level (/mnt/remotedir) many of those ops will hang if that mount is hung. Not sure if this even applies in your situation, it's just something I've observed with hung NFS mounts in /. Amanda does do a df of a couple of places (indexdir and tmp perhaps?) but I doubt those would hang unless they happened to be on your hung mount. Frank > > Graeme > > -- > Graeme Humphries ([EMAIL PROTECTED]) > (306) 955-7075 ext. 485 > > My views are not the views of my employers. -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda timeouts and weirdness solved!
Graeme Humphries wrote: So, you guys may recall I was having problems with amcheck and amdump taking ridiculously long. Well, it turns out that because on that client box, there was a dead Samba mount. As you guys know, when there's a Samba mount that's timed out, or the remote machine is unavailable, any operation checking mounted partitions takes forever and eventually times out. So... what in Amanda is checking mounted partitions on every operation, and can we limit to only the partitions we're actually backing up? :) That's probably gnutar itself. Gnutar runs with --one-filesystem option, but to be able to see when partitions are crossed, gnutar needs to do a check. Yes, and that can hang. Do you really need smbmounts? Apparently not, because days can pass without anyone noticing the dead mount... :-) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amanda timeouts and weirdness solved!
Frank Smith wrote: I don't think Amanda checks all your mounts. However, many filesystem operations 'stat' their way up the directory structure to /, and if you mount things directly in / (such as /remotedir) instead of down a level (/mnt/remotedir) many of those ops will hang if that mount is hung. Not sure if this even applies in your situation, it's just something I've observed with hung NFS mounts in /. This particular case was mounted under /tmp/somedir, and amanda's set to backup / on that box, so that could be it. Amanda does do a df of a couple of places (indexdir and tmp perhaps?) but I doubt those would hang unless they happened to be on your hung mount. Doesn't df always scan all the mounted filesystems? Or can you restrict it? Graeme
Re: amanda timeouts and weirdness solved!
--On Wednesday, August 24, 2005 11:02:47 -0600 Graeme Humphries <[EMAIL PROTECTED]> wrote: > Frank Smith wrote: > >> I don't think Amanda checks all your mounts. However, many filesystem >> operations 'stat' their way up the directory structure to /, and if >> you mount things directly in / (such as /remotedir) instead of down >> a level (/mnt/remotedir) many of those ops will hang if that mount >> is hung. Not sure if this even applies in your situation, it's just >> something I've observed with hung NFS mounts in /. >> >> > This particular case was mounted under /tmp/somedir, and amanda's set to > backup / on that box, so that could be it. I think Paul's point is valid about tar's one-filesystem flag, I haven't tried it, but perhaps if you exclude ./tmp it won't stat /tmp/somedir. The real solution, of course, is to not have hung mounts ;-). > >> Amanda does do a df of a couple of places (indexdir and tmp perhaps?) >> but I doubt those would hang unless they happened to be on your hung >> mount. >> >> > Doesn't df always scan all the mounted filesystems? Or can you restrict it? If you call df with a filename or directory argument it only reports on the mount point containing it. Frank > > Graeme -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda timeouts and weirdness solved!
Frank Smith wrote: I think Paul's point is valid about tar's one-filesystem flag, I haven't tried it, but perhaps if you exclude ./tmp it won't stat /tmp/somedir. The real solution, of course, is to not have hung mounts ;-). I agree. :) If you call df with a filename or directory argument it only reports on the mount point containing it. Ahhh.
tar returned 2 error???
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 is an O200 SGI running irix-6.5.x and the tar version seems ok: shadow::~> /usr/freeware/bin/tar --version tar (GNU tar) 1.13.25 Here's the relevent parts from the sendbackup and sendsize debug file on the client: [sorry for the long lines) sendbackup: debug 1 pid 144399 ruid 666 euid 666: start at Wed Aug 24 06:14:50 2005 /opt/amanda/amanda2/libexec/sendbackup: version 2.4.4p3-20040805 parsed request as: program `GNUTAR' disk `/' device `/' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;index;exclude-list=.amanda-gnutar-exclude-list.txt;exclude-optional;' [...] irrelevent connections/port stuff deleted sendbackup-gnutar: time 0.018: doing level 0 dump as listed-incremental to /opt/amanda/amanda2/var/amanda/gnutar-lists/shadow__0.new sendbackup-gnutar: time 2.824: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 2.874: started index creator: "/usr/freeware/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" sendbackup: time 2.874: spawning /opt/amanda/amanda2/libexec/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory / --one-file-system --listed-incremental /opt/amanda/amanda2/var/amanda/gnutar-lists/shadow__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda-conf2/sendbackup._.20050824061452.exclude . sendbackup-gnutar: time 2.880: /opt/amanda/amanda2/libexec/runtar: pid 147118 sendbackup: time 4.949: 124: strange(?): gtar: ./dev/fd: Cannot savedir: Function not implemented sendbackup: time 80.884: 124: strange(?): gtar: ./dev/fd: Warning: Cannot savedir: Function not implemented sendbackup: time 122.999: 60: normal(|): gtar: ./dev/entropy: socket ignored sendbackup: time 238.346: 60: normal(|): gtar: ./opt/prngd/egd-pool: socket ignored sendbackup: time 1520.322: 124: strange(?): gtar: ./var/adm/MAILOG: file changed as we read it sendbackup: time 1806.327: index created successfully sendbackup: time 1806.359: 53:size(|): Total bytes written: 3067299840 (2.9GB, 1.6MB/s) sendbackup: time 1806.365: 124: strange(?): gtar: Error exit delayed from previous errors sendbackup: time 1806.382: error [/usr/freeware/bin/tar returned 2] sendbackup: time 1806.382: pid 144399 finish time Wed Aug 24 06:44:56 2005 -- sendsize debug: sendsize[133766]: time 9086.776: calculating for amname '/', dirname '/', spindle 4 sendsize[133766]: time 9086.777: getting size via gnutar for / level 0 sendsize[100526]: time 9086.778: waiting for any estimate child: 1 running sendsize[133766]: time 9086.972: spawning /opt/amanda/amanda2/libexec/runtar in pipeline sendsize[133766]: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /opt/amanda/amanda2/var/amanda/gnutar-lis ts/shadow__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda-conf2/sendsize._.20050824054635.exclude . sendsize[133766]: time 9091.379: /usr/freeware/bin/tar: ./dev/fd: Cannot savedir: Function not implemented sendsize[133766]: time 9165.900: /usr/freeware/bin/tar: ./dev/fd: Warning: Cannot savedir: Function not implemented sendsize[133766]: time 9184.276: /usr/freeware/bin/tar: ./dev/entropy: socket ignored sendsize[133766]: time 9185.984: /usr/freeware/bin/tar: ./opt/prngd/egd-pool: socket ignored sendsize[133766]: time 9253.967: Total bytes written: 3067514880 (2.9GB, 18MB/s) sendsize[133766]: time 9253.975: /usr/freeware/bin/tar: Error exit delayed from previous errors sendsize[133766]: time 9253.975: . sendsize[133766]: estimate time for / level 0: 167.003 sendsize[133766]: estimate size for / level 0: 2995620 KB sendsize[133766]: time 9253.975: waiting for /usr/freeware/bin/tar "/" child sendsize[133766]: time 9253.993: after /usr/freeware/bin/tar "/" wait sendsize[133766]: time 9254.068: getting size via gnutar for / level 1 sendsize[133766]: Can't open exclude file '//.amanda-gnutar-exclude-list.txt': No such file or directory sendsize[133766]: time 9254.419: spawning /opt/amanda/amanda2/libexec/runtar in pipeline sendsize[133766]: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /opt/amanda/amanda2/var/amanda/gnutar-lis ts/shadow__1.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda-conf2/sendsize._.20050824054922.exclude . sendsize[133766]: time 9256.158: /usr/freeware/bin/tar: ./dev/fd: Cannot savedir: Function not implemented sendsize[133766]: time 9320.977: /usr/freeware/bin/tar: ./dev/fd: Warning: Cannot savedir: Function not implemented sendsize[133766]: time 9339.794: /usr/freeware
Re: tar returned 2 error???
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 which it can continue doing its archive. Gnutar reports the file caused problems and sets a flag that causes an exit status of 2 when it gets to the normal end point. ... > sendsize[133766]: time 9395.075: /usr/freeware/bin/tar: ./dev/fd: Cannot > savedir: Function not implemented > sendsize[133766]: time 9458.503: /usr/freeware/bin/tar: ./dev/fd: Warning: > Cannot savedir: Function not implemented > sendsize[133766]: time 9477.462: /usr/freeware/bin/tar: ./dev/entropy: socket > ignored > sendsize[133766]: time 9479.274: /usr/freeware/bin/tar: ./opt/prngd/egd-pool: > socket ignored > sendsize[133766]: time 9550.026: /usr/freeware/bin/tar: > ./var/spool/pbs/server_priv/jobs/70085.shado.JB: Warning: Cannot stat: No > such file or directory > sendsize[133766]: time 9550.034: /usr/freeware/bin/tar: > ./var/spool/pbs/server_priv/jobs/70085.shado.SC: Warning: Cannot stat: No > such file or directory > sendsize[133766]: time 9551.503: Total bytes written: 3056629760 (2.8GB, > 18MB/s) > sendsize[133766]: time 9551.510: /usr/freeware/bin/tar: Error exit delayed > from previous errors > sendsize[133766]: time 9551.510: . ... > > > Any clue? Looks to me like: Some devices, sockets and whatever fd is (file descriptor, floppy disk, ???) could not be handled by tar and two temporary spool files existed when tar looked at the directory listing but had already disappeared when tar tried to get their size, ownership, ... Maybe some exclude's are needed? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: tar returned 2 error???
For UNIX systems, return code 2 is "No such file or directory" or "File not found", depending on the OS. This information is found in the /usr/include/errno.h on most UNIX systems (or wherever your version of UNIX stores the programming include files). Most programs will exit with a failure code from this file and looking up the value of the error number in the file will get you back to the reason for the failure. In the example presented, lines 5 and 6, the "No such file ore directory" messages, are probably the cause of the error number 2 return code. The reason that it reported those errors rather than the earlier messages about "Function not implemented" (which is probably error code 22 - invalid argument), is either that error code 22 is a less serious event than error code 2 to the program, or tar is designed to report the 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 users Subject: Re: tar returned 2 error??? 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 which it can continue doing its archive. Gnutar reports the file caused problems and sets a flag that causes an exit status of 2 when it gets to the normal end point. ... > sendsize[133766]: time 9395.075: /usr/freeware/bin/tar: ./dev/fd: Cannot > savedir: Function not implemented > sendsize[133766]: time 9458.503: /usr/freeware/bin/tar: ./dev/fd: Warning: > Cannot savedir: Function not implemented > sendsize[133766]: time 9477.462: /usr/freeware/bin/tar: ./dev/entropy: socket > ignored > sendsize[133766]: time 9479.274: /usr/freeware/bin/tar: ./opt/prngd/egd-pool: > socket ignored > sendsize[133766]: time 9550.026: /usr/freeware/bin/tar: > ./var/spool/pbs/server_priv/jobs/70085.shado.JB: Warning: Cannot stat: No > such file or directory > sendsize[133766]: time 9550.034: /usr/freeware/bin/tar: > ./var/spool/pbs/server_priv/jobs/70085.shado.SC: Warning: Cannot stat: No > such file or directory > sendsize[133766]: time 9551.503: Total bytes written: 3056629760 (2.8GB, > 18MB/s) > sendsize[133766]: time 9551.510: /usr/freeware/bin/tar: Error exit delayed > from previous errors > sendsize[133766]: time 9551.510: . ... > > > Any clue? Looks to me like: Some devices, sockets and whatever fd is (file descriptor, floppy disk, ???) could not be handled by tar and two temporary spool files existed when tar looked at the directory listing but had already disappeared when tar tried to get their size, ownership, ... Maybe some exclude's are needed? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) This e-mail and any of its attachments may contain Exelon Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Exelon Corporation family of Companies. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You.
Re: amlabel Issue
Indeed, amtape produces the same response. Does this help us to determine the cause? Thanks! On Aug 23, 2005, at 6:49 PM, Jon LaBadie wrote: On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote: We are currently experiencing the below issue using amlabel. I have tried with and without a tape loaded, with and without a slot specified etc.. All chg-zd-mtx "tests" described in the script notes have been confirmed to work.. As an intermediate test (between chg-zd-mtx direct and am- applications), did you try amtape to manipulate your drive and changer? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel Issue
Thanks for the help, everyone. This was a permissions issue. Thanks! On Aug 24, 2005, at 5:02 PM, James Jacocks wrote: Indeed, amtape produces the same response. Does this help us to determine the cause? Thanks! On Aug 23, 2005, at 6:49 PM, Jon LaBadie wrote: On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote: We are currently experiencing the below issue using amlabel. I have tried with and without a tape loaded, with and without a slot specified etc.. All chg-zd-mtx "tests" described in the script notes have been confirmed to work.. As an intermediate test (between chg-zd-mtx direct and am- applications), did you try amtape to manipulate your drive and changer? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tar returned 2 error???
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 successful execution of an
application, non-zero otherwise. The meaning of any specific non-zero value
is up to the application developer(s).
The value to which errno is set is not related to the exit status (aka return
code)
of an application. errno is intended to be used internally in the C code, and
any similiarity between it an the exit status is coincidence (or the application
developer's idea of an ordered world).
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
