tar Command
Hi All ! I had a issue with a tar command with one of my customers, the same below listed command works fine for me but it doesnot seem to work for one of my customer, Please advice Thanks in advance [EMAIL PROTECTED] amanda]$ tar -cvf /dev/nst0 foldera > foldera/ > foldera/amanda.conf > foldera/disklist > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > tar: /dev/nst0: Cannot read: Input/output error > tar: At beginning of tape, quitting now > tar: Error is not recoverable: exiting now > [EMAIL PROTECTED] amanda]$ mt -f /dev/nst0 rewind > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > drwxr-xr-x amanda/disk 0 2005-04-01 13:35:46 foldera/ > -rw-r--r-- amanda/disk 17822 2005-04-01 13:33:22 foldera/amanda.conf > -rw-r--r-- amanda/disk5490 2005-04-01 13:33:22 foldera/disklist > [EMAIL PROTECTED] amanda]$ mt -f /dev/nst0 rewind > [EMAIL PROTECTED] amanda]$ tar -rvf /dev/nst0 folder > foldera folderb > [EMAIL PROTECTED] amanda]$ tar -rvf /dev/nst0 folderb > folderb/ > folderb/amanda.conf > folderb/disklist > [EMAIL PROTECTED] amanda]$ mt -f /dev/nst0 rewind > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > drwxr-xr-x amanda/disk 0 2005-04-01 13:35:46 foldera/ > -rw-r--r-- amanda/disk 17822 2005-04-01 13:33:22 foldera/amanda.conf > -rw-r--r-- amanda/disk5490 2005-04-01 13:33:22 foldera/disklist > drwxr-xr-x amanda/disk 0 2005-04-01 13:36:24 folderb/ > -rw-r--r-- amanda/disk 17834 2005-04-01 13:33:55 folderb/amanda.conf > -rw-r--r-- amanda/disk5288 2005-04-01 13:33:55 folderb/disklist > [EMAIL PROTECTED] amanda]$ -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. 1st Floor,'C'Wing, Fortune2000, Bandra Kurla Complex, Bandra(East), Mumbai 400051. Maharashtra India Tel: +91-22-3987 Fax: +91-22-39878899 Cell : +91-9820367783 E-mail : [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Newbie: amlabel: could not load slot "current": changerfile must be specified in amanda.conf
On Mon, Apr 11, 2005 at 04:07:28PM +1000, Jesus Salvo Jr. wrote: > > Hi, > > I have a StorEdge L7 on an E220R running Solaris9. > I have configured Solaris9 with sgen and mtx and chg-zd-mtx > mtx is working > chg-zd-mtx is also working > > The relevant entries in amanda.conf are: > > changerdev "/dev/scsi/changer/c2t1d0" > tpchanger "chg-zd-mtx" # the tape-changer glue script > tapedev "/dev/rmt/1n" # the no-rewind tape device to be used > changerfile "/usr/local/etc/amanda/Daily/chg-zd-mtx" > tapetype DLT8000 > > The conf file for chg-zd-mtx is: > /usr/local/etc/amanda/Daily/chg-zd-mtx.conf > > Note that the changerfile entry in amanda.conf does not have the ".conf" > suffix, as per the document in the chg-zd-mtx script ... and it is the only > way to get chg-zd-mtx working. > > However, when I do amlabel, I get: > > $ amlabel Daily Daily001 > amlabel: could not load slot "current": changerfile must be specified in > amanda.conf > You indicate that chg-zd-mtx is "working". Just to be certain: Have you exercised the changer script by invoking it directly with all the possible commands including "current" (if that is a chg-zd-mtx cmd). Have you exercised the changer script by invoking it with amtape and all the possible commands including "current". As I recall you have to edit chg-zd-mtx.conf. Perhaps some inadvertant editing change messed it up. Try running the diff command on the original source and on your edited script and see if all the changes are those you intended. I only played a bit with chg-zd-mtx. I use the more 'primitive' chg-mtx. But I see my chg-zd-mtx config file is executable. Don't recall if it had to be, but you might check. Some have reported mysterious problems with chg-zd-mtx that disappeared when using a POSIX-compatible shell. On solaris, /bin/sh is a true Bourne shell, not many of them around any more. If the changer file has a #! first line, you might point it to a POSIX shell, bash, ksh, or on Solaris, /usr/xpg4/bin/sh (actually ksh with perhaps a few tiny mods). jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tar Command
On Mon, Apr 11, 2005 at 02:43:55PM +0530, Kaushal Shriyan wrote: > Hi All ! > > I had a issue with a tar command with one of my customers, the same > below listed command works fine for me but it doesnot seem to work for > one of my customer, > > Please advice > > Thanks in advance > > [EMAIL PROTECTED] amanda]$ tar -cvf /dev/nst0 foldera > > foldera/ > > foldera/amanda.conf > > foldera/disklist > > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > > tar: /dev/nst0: Cannot read: Input/output error > > tar: At beginning of tape, quitting now > > tar: Error is not recoverable: exiting now > > [EMAIL PROTECTED] amanda]$ mt -f /dev/nst0 rewind > > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > > drwxr-xr-x amanda/disk 0 2005-04-01 13:35:46 foldera/ > > -rw-r--r-- amanda/disk 17822 2005-04-01 13:33:22 foldera/amanda.conf > > -rw-r--r-- amanda/disk5490 2005-04-01 13:33:22 foldera/disklist > > [EMAIL PROTECTED] amanda]$ mt -f /dev/nst0 rewind > > [EMAIL PROTECTED] amanda]$ tar -rvf /dev/nst0 folder > > foldera folderb > > [EMAIL PROTECTED] amanda]$ tar -rvf /dev/nst0 folderb > > folderb/ > > folderb/amanda.conf > > folderb/disklist > > [EMAIL PROTECTED] amanda]$ mt -f /dev/nst0 rewind > > [EMAIL PROTECTED] amanda]$ tar -tvf /dev/nst0 > > drwxr-xr-x amanda/disk 0 2005-04-01 13:35:46 foldera/ > > -rw-r--r-- amanda/disk 17822 2005-04-01 13:33:22 foldera/amanda.conf > > -rw-r--r-- amanda/disk5490 2005-04-01 13:33:22 foldera/disklist > > drwxr-xr-x amanda/disk 0 2005-04-01 13:36:24 folderb/ > > -rw-r--r-- amanda/disk 17834 2005-04-01 13:33:55 folderb/amanda.conf > > -rw-r--r-- amanda/disk5288 2005-04-01 13:33:55 folderb/disklist > > [EMAIL PROTECTED] amanda]$ > Unless I miss something, you show a correctly running series of commands. How about showing the error so we can analyze it? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Large Amanda installations
Nick, Amanda does not, as far as I know, allow backups to write to multiple drives concurrently. It can switch tape in a jukebox and it can swap to a second drive unit when the first is full, but concurrent writing isn't a feature I'm aware of. At my site I've done something that I believe is similar to what Joshua has done. I have an amanda server with two amanda configs, to avoid conficts, because they run at the same time, and because I wanted to avoid rebuilding binaries with non-standard sockets, I run one where all DLE are local to the server and one where the amanda-clients are all not-on-the-server. Within each config amanda does the scheduling but I'm able to make rapid use of two drives concurrently. FYI, these are LTO drives in 9 slot jukeboxes. On Sat, Apr 09, 2005 at 03:13:54PM -0500, Nick Jones wrote: > Wouldn't it still be more efficient to let AMANDA's planner take care of > which backups go to which drives and at what times? > > > -- > Nick > -Original Message- > From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 09, 2005 3:06 PM > To: Nick Jones > Cc: amanda-users@amanda.org > Subject: RE: Large Amanda installations > > On Sat, 9 Apr 2005 at 9:15am, Nick Jones wrote > > > As it stands (and as far as I know) the only way to tape to multiple > > drives simultaneously is to use "juke" in conjunction with AMANDA. > > Native support for a multi-slot and multi-drive changer would be nice. > Thanks. > > That's not exactly true. I use both drives in my changer simply by running > two configs simultaneously. To some extent, it's just an added level of > parallelization. When I had only one drive and was using 'runtapes=2', the > backups sometimes ran well into the day. With two drives, two configs, and > runtapes=1, they're always done in the early AM. > > As to the original question, I've got ~4.8TB of used space over 4 servers > (out of ~5.2GB formatted space), and back it up using a 2 drive, 19 slot > AIT3 changer. With a new 6TB server arriving Monday, I'm looking hard at > LTO3 changers... > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > > --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
RE: Newbie: amlabel: could not load slot "current": changerfile m ust be specified in amanda.conf
Did you read the comments in 'chg-zd-mtx'? Make sure you can successfully complete the basic test procedures written in 'chg-zd-mtx' -Original Message- From: Jesus Salvo Jr. [mailto:[EMAIL PROTECTED] Sent: Monday, April 11, 2005 2:07 AM To: amanda-users@amanda.org Subject: Newbie: amlabel: could not load slot "current": changerfile must be specified in amanda.conf Hi, I have a StorEdge L7 on an E220R running Solaris9. I have configured Solaris9 with sgen and mtx and chg-zd-mtx mtx is working chg-zd-mtx is also working The relevant entries in amanda.conf are: changerdev "/dev/scsi/changer/c2t1d0" tpchanger "chg-zd-mtx" # the tape-changer glue script tapedev "/dev/rmt/1n" # the no-rewind tape device to be used changerfile "/usr/local/etc/amanda/Daily/chg-zd-mtx" tapetype DLT8000 The conf file for chg-zd-mtx is: /usr/local/etc/amanda/Daily/chg-zd-mtx.conf Note that the changerfile entry in amanda.conf does not have the ".conf" suffix, as per the document in the chg-zd-mtx script ... and it is the only way to get chg-zd-mtx working. However, when I do amlabel, I get: $ amlabel Daily Daily001 amlabel: could not load slot "current": changerfile must be specified in amanda.conf Regards, John
amstatus formatting
Hello Amanda users, There isn't a ready equiv to "columnspec" for amstatus, is there ? I'd like to adjust the columns on a couple of my reports, or change the units, either way. samar 1# /usr/local/sbin/amstatus samar Using /usr5/amanda/DailySet1/amdump from Fri Apr 8 21:00:05 EDT 2005 samar:/ 1 1121k finished (22:05:20) samar:/usr1 1 25k finished (22:04:57) samar:/usr5/allengr 260896k finished (22:13:38) samar:/usr5/amanda 1 k finished (22:05:34) samar:/usr5/bimal 113948k finished (22:06:44) samar:/usr5/dtaylor 0145063106k finished (1+10:56:02) samar:/usr5/hxgao 126784k finished (22:15:13) samar:/usr5/joy 015329k dumping to tape (2+4:37:09) samar:/usr5/lalor 10k finished (22:03:45) samar:/usr5/leith 2 102601k finished (22:07:08) samar:/usr5/liw 1 160714k finished (22:17:53) samar:/usr5/ninggao 1 1401k finished (22:14:18) samar:/usr5/skaur 10k finished (22:03:31) samar:/usr5/tapu1 26k finished (22:04:43) thank you, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: amstatus formatting
On Monday 11 April 2005 10:50, Brian Cuttler wrote: >Hello Amanda users, > >There isn't a ready equiv to "columnspec" for amstatus, is there ? > >I'd like to adjust the columns on a couple of my reports, or change >the units, either way. > >samar 1# /usr/local/sbin/amstatus samar >Using /usr5/amanda/DailySet1/amdump from Fri Apr 8 21:00:05 EDT > 2005 > >samar:/ 1 1121k finished (22:05:20) >samar:/usr1 1 25k finished (22:04:57) >samar:/usr5/allengr 260896k finished (22:13:38) >samar:/usr5/amanda 1 k finished (22:05:34) >samar:/usr5/bimal 113948k finished (22:06:44) >samar:/usr5/dtaylor 0145063106k finished (1+10:56:02) >samar:/usr5/hxgao 126784k finished (22:15:13) >samar:/usr5/joy 015329k dumping to tape (2+4:37:09) >samar:/usr5/lalor 10k finished (22:03:45) >samar:/usr5/leith 2 102601k finished (22:07:08) >samar:/usr5/liw 1 160714k finished (22:17:53) >samar:/usr5/ninggao 1 1401k finished (22:14:18) >samar:/usr5/skaur 10k finished (22:03:31) >samar:/usr5/tapu1 26k finished (22:04:43) > > thank you, > > Brian > I think the only thing it pays any attention to is the k,m,g switch that was added to amanda.conf a year or so back. From my current amanda.conf: -- # This is a recently added item, "displayunit". # The default has always been K till now # One should set displayunit "m" # to make it use megabytes instead --- With the above setting, I get amstatus reports like this: --- coyote:/amanda 3 53m finished (3:09:15) coyote:/bin05m finished (3:13:01) coyote:/boot 0 47m finished (3:09:19) coyote:/dev09m finished (3:11:54) coyote:/dos17m finished (3:12:33) coyote:/etc07m finished (3:12:31) coyote:/home 0 159m finished (3:04:47) coyote:/lib0 28m finished (3:10:14) coyote:/opt10m finished (3:13:26) coyote:/root 1 384m finished (3:01:27) coyote:/sbin 0 18m finished (3:11:04) coyote:/tmp0 166m finished (3:08:46) coyote:/usr/FC310m finished (3:15:17) coyote:/usr/FC3-SRPMS 10m finished (3:15:01) coyote:/usr/X11R6 10m finished (3:13:34) coyote:/usr/bin0 277m finished (3:05:49) coyote:/usr/dlds-misc 0 1631m finished (2:24:13) Would that help you Brian? I note that it 'rounds down' however, and I personally would rather it rounded up. But... shrug. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: amstatus formatting
Gene, Thank you, will have to try this out, probably have to upgrade the server to a newer version, but that is go to do periodically anyway, not that I've ever encountered bugs, its always been a matter of feature upgrades for our site. I'm not sure if it would be confusing to dynamically choose the units based on field length and appy the designator k, m or g. thank you, Brian On Mon, Apr 11, 2005 at 12:04:43PM -0400, Gene Heskett wrote: > On Monday 11 April 2005 10:50, Brian Cuttler wrote: > >Hello Amanda users, > > > >There isn't a ready equiv to "columnspec" for amstatus, is there ? > > > >I'd like to adjust the columns on a couple of my reports, or change > >the units, either way. > > > >samar 1# /usr/local/sbin/amstatus samar > >Using /usr5/amanda/DailySet1/amdump from Fri Apr 8 21:00:05 EDT > > 2005 > > > >samar:/ 1 1121k finished (22:05:20) > >samar:/usr1 1 25k finished (22:04:57) > >samar:/usr5/allengr 260896k finished (22:13:38) > >samar:/usr5/amanda 1 k finished (22:05:34) > >samar:/usr5/bimal 113948k finished (22:06:44) > >samar:/usr5/dtaylor 0145063106k finished (1+10:56:02) > >samar:/usr5/hxgao 126784k finished (22:15:13) > >samar:/usr5/joy 015329k dumping to tape (2+4:37:09) > >samar:/usr5/lalor 10k finished (22:03:45) > >samar:/usr5/leith 2 102601k finished (22:07:08) > >samar:/usr5/liw 1 160714k finished (22:17:53) > >samar:/usr5/ninggao 1 1401k finished (22:14:18) > >samar:/usr5/skaur 10k finished (22:03:31) > >samar:/usr5/tapu1 26k finished (22:04:43) > > > > thank you, > > > > Brian > > > I think the only thing it pays any attention to is the k,m,g switch > that was added to amanda.conf a year or so back. From my current > amanda.conf: > -- > # This is a recently added item, "displayunit". > # The default has always been K till now > # One should set > displayunit "m" > # to make it use megabytes instead > --- > With the above setting, I get amstatus reports like this: > --- > coyote:/amanda 3 53m finished (3:09:15) > coyote:/bin05m finished (3:13:01) > coyote:/boot 0 47m finished (3:09:19) > coyote:/dev09m finished (3:11:54) > coyote:/dos17m finished (3:12:33) > coyote:/etc07m finished (3:12:31) > coyote:/home 0 159m finished (3:04:47) > coyote:/lib0 28m finished (3:10:14) > coyote:/opt10m finished (3:13:26) > coyote:/root 1 384m finished (3:01:27) > coyote:/sbin 0 18m finished (3:11:04) > coyote:/tmp0 166m finished (3:08:46) > coyote:/usr/FC310m finished (3:15:17) > coyote:/usr/FC3-SRPMS 10m finished (3:15:01) > coyote:/usr/X11R6 10m finished (3:13:34) > coyote:/usr/bin0 277m finished (3:05:49) > coyote:/usr/dlds-misc 0 1631m finished (2:24:13) > > Would that help you Brian? I note that it 'rounds down' however, and > I personally would rather it rounded up. But... shrug. > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.34% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com and AOL/TW attorneys please note, additions to the above > message by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Tar versions
Is there a list of known working/broken tar versions? I remember discussions about versions < 1.13.19 not building indexes correctly (and was bit by that myself when I first started), and I saw some remarks about the latest (at some time) version not working. Just asking because in the last week Debian Sarge is now distributing tar 1.14. My amanda at work is built to use a local version, but my home setup isn't. I intend to test it with some restores, but if there are some subtle changes I might not notice until it's too late ;-). Thanks, Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Tar versions
On Mon, 11 Apr 2005 at 11:17am, Frank Smith wrote > Is there a list of known working/broken tar versions? I remember > discussions about versions < 1.13.19 not building indexes correctly > (and was bit by that myself when I first started), and I saw some > remarks about the latest (at some time) version not working. 1.13.25 is well known to be quite stable. > Just asking because in the last week Debian Sarge is now distributing > tar 1.14. My amanda at work is built to use a local version, but my > home setup isn't. I intend to test it with some restores, but if there > are some subtle changes I might not notice until it's too late ;-). ISTR some discussions in the past of 1.14 being OK. Check the archives -- I think it was Gene. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Large Amanda installations
On Sat, 9 Apr 2005 at 3:13pm, Nick Jones wrote > Wouldn't it still be more efficient to let AMANDA's planner take care of > which backups go to which drives and at what times? Oh, sure. I was just commenting that you *can* (and I do) use a multi-drive library with amanda now without juke. Native support would indeed be nice. One limitation of my current setup is that any one client can only be in one of the configs. Well, you could get around that by compiling two amanda binaries on such clients as well as the server, but that's a bit ugly. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Tar versions
On Monday 11 April 2005 12:17, Frank Smith wrote: >Is there a list of known working/broken tar versions? I remember >discussions about versions < 1.13.19 not building indexes correctly >(and was bit by that myself when I first started), and I saw some >remarks about the latest (at some time) version not working. > Just asking because in the last week Debian Sarge is now > distributing tar 1.14. My amanda at work is built to use a local > version, but my home setup isn't. I intend to test it with some > restores, but if there are some subtle changes I might not notice > until it's too late ;-). > >Thanks, >Frank ISTR, but don't take it to the bank, that 1.14 had some sort of a gotcha. I never tried it myself however, so take that with a appropriate seasoning. It sure didn't last too long before it was replaced with 1.15.1 though if thats any indicator. I switched to the latest 1.15.1 about 6 months ago, and have had zilch problems with that version so far. 1.13-19 and 1.13-25 were also known to be good versions. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Tar versions
On Monday 11 April 2005 12:59, Joshua Baker-LePain wrote: >On Mon, 11 Apr 2005 at 11:17am, Frank Smith wrote > >> Is there a list of known working/broken tar versions? I remember >> discussions about versions < 1.13.19 not building indexes >> correctly (and was bit by that myself when I first started), and I >> saw some remarks about the latest (at some time) version not >> working. > >1.13.25 is well known to be quite stable. > >> Just asking because in the last week Debian Sarge is now >> distributing tar 1.14. My amanda at work is built to use a local >> version, but my home setup isn't. I intend to test it with some >> restores, but if there are some subtle changes I might not notice >> until it's too late ;-). > >ISTR some discussions in the past of 1.14 being OK. Check the > archives -- I think it was Gene. Tweren't me Joshua, I went straight to 1.15.1 about 6 months back and its been fine, but I don't think I ever tried 1.14 at all. It was pretty shortlived at gnu.org so that may be a clue that it wasn't quite right somehow. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Tar versions
Frank Smith wrote: Is there a list of known working/broken tar versions? I remember discussions about versions < 1.13.19 not building indexes correctly (and was bit by that myself when I first started), and I saw some remarks about the latest (at some time) version not working. Just asking because in the last week Debian Sarge is now distributing tar 1.14. My amanda at work is built to use a local version, but my home setup isn't. I intend to test it with some restores, but if there are some subtle changes I might not notice until it's too late ;-). My current knowledge: 1.13.19 is good. However it still sets return code 2 for some infrequent conditions even with --ignore-failed-read option. This results in amanda thinking the total archive is bad, and drops the complete archive. Those conditions are very rare on a quiet filesystem. 1.13.25: no problems found (yet). 1.13.9x have changed the format of "tar -t", resulting in amrecover not able to use the indexes. 1.14.x writes good archives, but when restoring, it has trouble with sparse files; the sparse file itself, and *all* files after it cannot be read anymore. But you can read the archive with a good tar version (i.e. the tar images produced are fine). 1.15.1 no problems found (yet). I'm using this version on most of my clients since january this year, and have already done successful restore too. -- 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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
splitting DLE's
I know this is one of the top 10 most frequent FAQs here. I understand
the answer conceptually, but I'm having trouble with the syntax, I
guess.
/ is one filesystem. /raidion is an external raid unit. I want to split
/raidion into 2 DLEs: /raidion/home/techops and /raidion/home/*
(exlcuding /techops).
riffraff.rfa.org/ comp-high-tar
riffraff.rfa.org/raidion/home/techops comp-high-tar
riffraff.rfa.org/raidion_HOME_REST /raidion/home/ {
comp-high-tar
exclude "/raidion/home/techops"
}
amcheck doesn't like the /raidion_HOME_REST DLE at all. What do the
fields mean when you add an inline dump-type? What did I do wrong or
what am I not understanding from the example given in the top 10
answers?
I also have a DLE problem with windows shares backed up via smbclient.
How do I specify a directory with a space in it's name?
say I want to specify "//server/share$/directory with spaces" ...
quoting it doesn't work and \ escaping the spaces doesn't work either.
Can I use something like //server/share$/directory* ?
This is on debian sarge using the debian packages for amanda (2.4.4p3-2)
and samba (3.0.10-1).
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
[EMAIL PROTECTED]
Re: Tar versions
Hi, Paul, on Montag, 11. April 2005 at 21:15 you wrote to amanda-users: PB> My current knowledge: PB> 1.13.19 is good. However it still sets return code 2 for some PB> infrequent conditions even with --ignore-failed-read option. PB> This results in amanda thinking the total archive is bad, PB> and drops the complete archive. Those conditions are very rare PB> on a quiet filesystem. PB> 1.13.25: no problems found (yet). PB> 1.13.9x have changed the format of "tar -t", resulting in amrecover PB> not able to use the indexes. PB> 1.14.x writes good archives, but when restoring, it has trouble PB> with sparse files; the sparse file itself, and *all* files after it PB> cannot be read anymore. But you can read the archive with a good PB> tar version (i.e. the tar images produced are fine). PB> 1.15.1 no problems found (yet). I'm using this version on most of PB> my clients since january this year, and have already done PB> successful restore too. Thanks a lot, Paul, for this listing. At slashdot.org I would moderate this as "Informative" ;-) If anyone has had the same or different experiences, please let us know. I'll include this information in the docs as soon as things have cleared up. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: splitting DLE's
Hi, Eric,
on Montag, 11. April 2005 at 22:18 you wrote to amanda-users:
EDR> riffraff.rfa.org/raidion/home/techops comp-high-tar
EDR> riffraff.rfa.org/raidion_HOME_REST /raidion/home/ {
EDR> comp-high-tar
EDR> exclude "/raidion/home/techops"
EDR> }
EDR> amcheck doesn't like the /raidion_HOME_REST DLE at all. What do the
EDR> fields mean when you add an inline dump-type? What did I do wrong or
EDR> what am I not understanding from the example given in the top 10
EDR> answers?
The value of the option exclude has to contain the RELATIVE path to
the DLE:
riffraff.rfa.org/raidion_HOME_REST /raidion/home/ {
comp-high-tar
exclude "./techops"
}
EDR> I also have a DLE problem with windows shares backed up via smbclient.
EDR> How do I specify a directory with a space in it's name?
EDR> say I want to specify "//server/share$/directory with spaces" ...
EDR> quoting it doesn't work and \ escaping the spaces doesn't work either.
EDR> Can I use something like //server/share$/directory* ?
(Several times in the archive):
"Export" your windows-directory as "directory_with_underscores" ...
Seems to get into the top 20 soon ;-)
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
Re: Tar versions
--On Monday, April 11, 2005 23:39:01 +0200 "Stefan G. Weichinger" <[EMAIL PROTECTED]> wrote: > Hi, Paul, > > on Montag, 11. April 2005 at 21:15 you wrote to amanda-users: > > PB> My current knowledge: > > PB> 1.13.19 is good. However it still sets return code 2 for some > PB> infrequent conditions even with --ignore-failed-read option. > PB> This results in amanda thinking the total archive is bad, > PB> and drops the complete archive. Those conditions are very rare > PB> on a quiet filesystem. > > PB> 1.13.25: no problems found (yet). > > PB> 1.13.9x have changed the format of "tar -t", resulting in amrecover > PB> not able to use the indexes. > > PB> 1.14.x writes good archives, but when restoring, it has trouble > PB> with sparse files; the sparse file itself, and *all* files after it > PB> cannot be read anymore. But you can read the archive with a good > PB> tar version (i.e. the tar images produced are fine). >From looking at the tar changelogs, it appears there were only two 1.14 versions: 1.14 and 1.14.90. It looks like 1.14.90 may have fixed the sparse file problem, but I saw this disturbing comment: * When restoring incremental dumps, --one-file-system option prevents directory hierarchies residing on different devices from being purged. With the previous versions of tar it was dangerous to create incremental dumps with --one-file-system option, since they would recursively remove mount points when restoring from the back up. This change fixes the bug. I don't know if 'previous versions' means 'previous 1.14 versions' or 'all versions until now'. Frank > > PB> 1.15.1 no problems found (yet). I'm using this version on most of > PB> my clients since january this year, and have already done > PB> successful restore too. > > Thanks a lot, Paul, for this listing. At slashdot.org I would moderate > this as "Informative" ;-) > > If anyone has had the same or different experiences, please let us > know. I'll include this information in the docs as soon as things > have cleared up. > > -- > best regards, > Stefan > > Stefan G. Weichinger > mailto:[EMAIL PROTECTED] > > > -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: splitting DLE's
On Mon, Apr 11, 2005 at 11:49:20PM +0200, Stefan G. Weichinger wrote:
> Hi, Eric,
> on Montag, 11. April 2005 at 22:18 you wrote to amanda-users:
> EDR> riffraff.rfa.org/raidion/home/techops comp-high-tar
> EDR> riffraff.rfa.org/raidion_HOME_REST /raidion/home/ {
> EDR> comp-high-tar
> EDR> exclude "/raidion/home/techops"
> EDR> }
> EDR> amcheck doesn't like the /raidion_HOME_REST DLE at all. What do the
> EDR> fields mean when you add an inline dump-type? What did I do wrong or
> EDR> what am I not understanding from the example given in the top 10
> EDR> answers?
> The value of the option exclude has to contain the RELATIVE path to
> the DLE:
>
> riffraff.rfa.org/raidion_HOME_REST /raidion/home/ {
> comp-high-tar
> exclude "./techops"
> }
ahha. thank you very much. I had to do it like this:
riffraff.rfa.org/raidion/home/ {
comp-high-tar
exclude "./techops"
}
With the /raidion_HOME_REST in there amcheck said:
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): selfcheck does not
support device.
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): sendsize does not
support device.
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): sendbackup does not
support device.
ERROR: riffraff.rfa.org: [BOGUS REQUEST PACKET]
> EDR> I also have a DLE problem with windows shares backed up via smbclient.
> EDR> How do I specify a directory with a space in it's name?
> EDR> say I want to specify "//server/share$/directory with spaces" ...
> EDR> quoting it doesn't work and \ escaping the spaces doesn't work either.
> EDR> Can I use something like //server/share$/directory* ?
> (Several times in the archive):
> "Export" your windows-directory as "directory_with_underscores" ...
gah I'm an idiot. In this case I was trying to do everything
starting from a top level share that includes these "named with spaces"
directories, forgetting that each directory is also shared on it's own
with a "nospacename". Sorry for the noise. Thanks for jogging my memory.
> Seems to get into the top 20 soon ;-)
ok. sorry for not finding it in the archives.
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
[EMAIL PROTECTED]
Re: splitting DLE's
On Mon, Apr 11, 2005 at 07:00:06PM -0400, Jon LaBadie wrote:
> On Mon, Apr 11, 2005 at 04:18:13PM -0400, Eric Dantan Rzewnicki wrote:
> > I know this is one of the top 10 most frequent FAQs here. I understand
> > the answer conceptually, but I'm having trouble with the syntax, I
> > guess.
> > / is one filesystem. /raidion is an external raid unit. I want to split
> > /raidion into 2 DLEs: /raidion/home/techops and /raidion/home/*
> > (exlcuding /techops).
> > riffraff.rfa.org/ comp-high-tar
> > riffraff.rfa.org/raidion/home/techops comp-high-tar
> > riffraff.rfa.org/raidion_HOME_REST /raidion/home/ {
> > comp-high-tar
> > exclude "/raidion/home/techops"
> > }
> > amcheck doesn't like the /raidion_HOME_REST DLE at all.
> An error message would be nice.
I didn't make my exclude relative. That was one problem ...
Sorry for the lack of error message.
See below.
> > What do the fields mean when you add an inline dump-type?
> They don't change because of the inline, the inline just replaces
> a dumptype name. From amanda manpage:
I read the manpage but couldn't figure out which of the optional fields
the /raidion_HOME_REST became. It turns out to not be needed. I was just
trying to follow the example given in the FAQ:
http://www.amanda.org/docs/topten.html#id2520555
which appears to give 4 fields for each DLE. But, with that 2nd field in
there amcheck says:
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): selfcheck does not
support device.
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): sendsize does not
support device.
ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): sendbackup does not
support device .
ERROR: riffraff.rfa.org: [BOGUS REQUEST PACKET]
> DISKLIST FILE
> The disklist file determines which disks will be backed up
> by Amanda. The file usually contains one line per disk:
>
> hostname diskname [ diskdevice ] dumptype [spindle [interface]]
>
> All pair [ hostname diskname ] must be unique.
>
> If there are three fields before the dumptype the second is the entry name
> (diskname ?or disklist name?) and the third is the starting directory or
> device name. Thus the diskname need not resemble a pathname if there are
> both a diskname and a starting directory (device name). If there are only
> two fields before the dumptype, the second field is still called a diskname
> but serves as both diskname and device name. Thus it must be a pathname.
My amcheck doesn't seem to like 3 fields before the dumptype. It works
fine if diskname also serves as device name.
> I don't see any error in your sample above, that is why I'd like to see
> the error you get.
> Two additional comments, unless /raidion has only "home" under it, you will
> NOT be backing up the entire /raidion directory tree.
I understand this. I do not want to backup the other directory under
/raidion. Thanks for the scrutiny, though.
> And second, more than one DLE can start from the same directory IF the
> disknames
> differ. For example, the above could have been entered as:
>
> riffraff.rfa.orgraidion_TECHOPS /raidion/home/ {
> comp-high-tar
> include file append "./techops"
> }
> riffraff.rfa.orgraidion_HOME /raidion/home/ {
> comp-high-tar
> exclude file append "./techops"
> }
I see. thank you.
> And if you have to backup other parts of /raidion, this might work.
>
> riffraff.rfa.orgraidion_NOHOME /raidion {
> comp-high-tar
> exclude file append "./home"
> }
Not needed in my case. But, again, thanks for the explanation.
> The "append" is optional. I tend to use it incase I'm nesting dumptypes
> and each might have their own excludes or includes. Or I might want to
> add more exclude directives and don't want to worry about having no more
> than one without an "append".
ah, ok. good to know.
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
[EMAIL PROTECTED]
Re: Tar versions
Stefan G. Weichinger wrote: on Montag, 11. April 2005 at 21:15 you wrote to amanda-users: PB> 1.13.25: no problems found (yet). If anyone has had the same or different experiences, please let us know. I'll include this information in the docs as soon as things have cleared up. ...still using 1.13.25 for over 2 years now, no problems found (yet, still using amanda 2.4.4 w/o patches), all restores fine until today. Cheers, Peter
Re: splitting DLE's
On Mon, Apr 11, 2005 at 07:20:24PM -0400, Eric Dantan Rzewnicki wrote: > > > > What do the fields mean when you add an inline dump-type? > > They don't change because of the inline, the inline just replaces > > a dumptype name. From amanda manpage: > ... > I read the manpage but couldn't figure out which of the optional fields > the /raidion_HOME_REST became. It turns out to not be needed. I was just > trying to follow the example given in the FAQ: > http://www.amanda.org/docs/topten.html#id2520555 > which appears to give 4 fields for each DLE. But, with that 2nd field in > there amcheck says: > ... > ERROR: riffraff.rfa.org:/raidion_HOME_REST (/raidion/home): selfcheck does > not support device. > > My amcheck doesn't seem to like 3 fields before the dumptype. It works > fine if diskname also serves as device name. > I was wondering, simply a guess. What happens if you leave the slashes out of the second field with a 4 field entry. I.e. raidion_HOME_REST rather than /raidion... I've never used the diskname in a 4 part'er with slashes. I'm thinking, maybe the leading slash makes some part of amanda think it is a pathname to the device/directory. Perhaps if there is no leading slash it will pick up the 3rd field as the device. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Newbie: amlabel: could not load slot "current": changerfile must be specified in amanda.conf
I knew I should have posted more information ... anyway ... On Monday 11 April 2005 23:57, Jon LaBadie wrote: > > You indicate that chg-zd-mtx is "working". Just to be certain: > > Have you exercised the changer script by invoking it directly with all > the possible commands including "current" (if that is a chg-zd-mtx cmd). Yes. I went through the chg-zd-mtx test: bash-2.05$ pwd /usr/local/etc/amanda/Daily bash-2.05$ ../../../libexec/chg-zd-mtx -reset 1 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 2 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot current 2 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 3 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 4 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 5 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 6 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 7 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot next 1 /dev/rmt/1n bash-2.05$ ../../../libexec/chg-zd-mtx -slot current 1 /dev/rmt/1n Clearly, the chg-zd-mtx script works and is able to read the chg-zd-mtx.conf file in /usr/local/etc/amanda/Daily, based on the debug files in /etc/amanda. For example: bash-2.05$ pwd /tmp/amanda bash-2.05$ more chg-zd-mtx.20050412111424.debug chg-zd-mtx: debug 1 pid 624 ruid 60008 euid 60008: start at Tue Apr 12 11:14:24 2005 11:14:25 Using config file /usr/local/etc/amanda/Daily/chg-zd-mtx.conf 11:14:25 Arg info: $# = 2 $0 = "../../../libexec/chg-zd-mtx" $1 = "-slot" $2 = "next" 11:14:25 Running: /usr/local/sbin/mtx status 11:14:25 Exit code: 0 Stdout: > > Have you exercised the changer script by invoking it with amtape and > all the possible commands including "current". It was earlier complaining: bash-2.05$ amtape Daily reset amtape: could not load tapelist "/usr/local/etc/amanda/Daily/tapelist" ... and the amanda man page says: TAPE MANAGEMENT The tapelist file contains the list of tapes in active use. This file is maintained entirely by Amanda and should not be created or edited for normal operation. It contains lines of the form: <...> After searching, it turns out that one has to create the tapelist file manually first, even though the document says: tapelist "string" Default: tapelist. The file name for the active tapelist file. Amanda maintains this file with infor- mation about the active set of tapes. Anyway, after creating an empty file tapelist in /usr/local/etc/amanda/Daily, I then run amtape again: bash-2.05$ amtape Daily reset amtape: could not reset changer: changerfile must be specified in amanda.conf The debug output in /tmp/amanda says: bash-2.05$ cat amtape.20050412112910.debug amtape: debug 1 pid 1077 ruid 60008 euid 60008: start at Tue Apr 12 11:29:10 2005 changer: got exit: 2 str: changerfile must be specified in amanda.conf amtape: could not reset changer: changerfile must be specified in amanda.conf amtape: pid 1077 finish time Tue Apr 12 11:29:10 2005 So .. I now run amgetconf: bash-2.05$ amgetconf Daily changerfile /usr/local/etc/amanda/Daily/chg-zd-mtx Of course, there is really no such file as that, since the script chg-zd-mtx says: # All variables are in "changerfile".conf where "changerfile" is set # in amanda.conf. For example, if amanda.conf has: # # changerfile="/etc/amanda/Dailyset1/CHANGER" # # the variables must be in "/etc/amanda/Dailyset1/CHANGER.conf". # # If "changerfile" is a relative path, it is relative to the directory # that contains amanda.conf. That also happens to be the directory Amanda # makes current before running this script. In fact, the chg-zd-mtx script will not work if the changerfile entry in amanda.conf is not valid / incorrect. In chg-zd-mtx script: changerfile=`amgetconf$SUF changerfile 2>/dev/null | grep -v BUGGY` if [ -z "$changerfile" ]; then Exit 2 \ "" \ "changerfile must be specified in amanda.conf" fi Here are the files in /usr/local/etc/amanda/Daily: bash-2.05$ pwd /usr/local/etc/amanda/Daily bash-2.05$ ls -alt total 56 drwxr-xr-x 2 amanda backup 512 Apr 12 11:53 . -rw-r--r-- 1 amanda backup 0 Apr 12 11:29 tapelist -rw-r--r-- 1 amanda backup 2 Apr 12 11:20 chg-zd-mtx-slot -rw-r--r-- 1 amanda backup 3 Apr 12 11:17 chg-zd-mtx-access -rw-r--r-- 1 amanda backup 1170 Apr 12 10:57 chg-zd-mtx.conf -rw-r--r-- 1 amanda backup 20311 Apr 11 15:30 amanda.conf -rw-r--r-- 1 amanda backup 0 Apr 10 17:52 chg-zd-mtx-barcodes -rw-r--r-- 1 amanda backup 2 Apr 10 17:52 chg-zd-mtx-clean -rw-r--r-- 1 amanda backup 901 Apr 10 12:00 chg-scsi-solaris.conf drwxr-xr-x 3 amanda backup 512 Apr 8 19:00 .. > > As I recall you have to edit chg-zd-mtx.conf. I modified the example to match my environment. All the changes are what I int
Re: Newbie: amlabel: could not load slot "current": changerfile m ust be specified in amanda.conf
On Tuesday 12 April 2005 00:29, Steve Yun wrote: > Did you read the comments in 'chg-zd-mtx'? > > Make sure you can successfully complete the basic test procedures written > in 'chg-zd-mtx' > As stated in an earlier post ... yes ... except for amtape, which was complaining of the same problem.
Re: Newbie: amlabel: could not load slot "current": changerfile must be specified in amanda.conf
On Tuesday 12 April 2005 12:01, Jesus Salvo Jr. wrote: > In fact, the chg-zd-mtx script will not work if the changerfile entry in > amanda.conf is not valid / incorrect. In chg-zd-mtx script: > > changerfile=`amgetconf$SUF changerfile 2>/dev/null | grep -v BUGGY` > if [ -z "$changerfile" ]; then > Exit 2 \ > "" \ > "changerfile must be specified in amanda.conf" > fi > That text "changerfile must be specified in amanda.conf" is the exact same text that amtape returns ... although clearly chg-zd-mtx is not having the same problem.
Re: Newbie: amlabel: could not load slot "current": changerfile must be specified in amanda.conf
On Tuesday 12 April 2005 12:01, Jesus Salvo Jr. wrote: > bash-2.05$ amtape Daily reset > amtape: could not reset changer: changerfile must be specified in > amanda.conf > > The debug output in /tmp/amanda says: > > bash-2.05$ cat amtape.20050412112910.debug > amtape: debug 1 pid 1077 ruid 60008 euid 60008: start at Tue Apr 12 > 11:29:10 2005 > changer: got exit: 2 str: changerfile must be specified in > amanda.conf amtape: could not reset changer: changerfile must be specified > in amanda.conf amtape: pid 1077 finish time Tue Apr 12 11:29:10 2005 > I think I know what the problem maybe, though I do not know the solution: The test that I did with chg-zd-mtx works only if I run it in the /usr/local/etc/amanda/Daily directory. If I do it anywhere else, I get the exact same error as amtape does: bash-2.05$ pwd /export/home/amanda bash-2.05$ /usr/local/libexec/chg-zd-mtx -reset changerfile must be specified in amanda.conf bash-2.05$ set | grep PATH LD_LIBRARY_PATH=:/usr/local/lib MANPATH=:/usr/local/man PATH=/usr/bin::/usr/local/bin:/usr/local/sbin:/usr/local/libexec Based on changer.c, amtape simply exec / calls chg-zd-mtx, so the error is the same. What must I do so that chg-zd-mtx will work from any directory ? I must have missed a very simple step. Regards, John
Re: Newbie: amlabel: could not load slot "current": changerfile must be specified in amanda.conf
On Tuesday 12 April 2005 13:07, Jesus Salvo Jr. wrote: > I think I know what the problem maybe, though I do not know the solution: > > The test that I did with chg-zd-mtx works only if I run it in > the /usr/local/etc/amanda/Daily directory. > > If I do it anywhere else, I get the exact same error as amtape does: > > bash-2.05$ pwd > /export/home/amanda > bash-2.05$ /usr/local/libexec/chg-zd-mtx -reset > changerfile must be specified in amanda.conf > > bash-2.05$ set | grep PATH > LD_LIBRARY_PATH=:/usr/local/lib > MANPATH=:/usr/local/man > PATH=/usr/bin::/usr/local/bin:/usr/local/sbin:/usr/local/libexec > > Based on changer.c, amtape simply exec / calls chg-zd-mtx, so the error is > the same. > > What must I do so that chg-zd-mtx will work from any directory ? > I must have missed a very simple step. > More info: I changed chg-zd-mtx so that I added an echo line just before it calls amgetconf: echo "amgetconf$SUF changerfile" changerfile=`amgetconf$SUF changerfile 2>/dev/null | grep -v BUGGY` if [ -z "$changerfile" ]; then Exit 2 \ "" \ "changerfile must be specified in amanda.conf" fi ... and here is the output: bash-2.05$ /usr/local/libexec/chg-zd-mtx -reset amgetconf changerfile changerfile must be specified in amanda.conf So chg-zd-mtx script does not pass the parameter to any of the am* executables, including amgetconf. Thus, amgetconf called from within chg-zd-mtx only works from within the directory containing the amanda.conf file. Anyway to resolve this without modifying the changer script ? Thanks, John
Append Files using tar
Hi Mr Kaushal, > > > > As per our conversation, i am sending you the screen shot of the steps > > followed by me. > > > > [EMAIL PROTECTED] tartest]# tar -cvf /dev/nst0 folderA > > folderA/ > > folderA/t1 > > folderA/t2 > > [EMAIL PROTECTED] tartest]# tar -tvf /dev/nst0 > > [EMAIL PROTECTED] tartest]# tar -tvf /dev/nst0 > > tar: /dev/nst0: Cannot read: Input/output error > > tar: At beginning of tape, quitting now > > tar: Error is not recoverable: exiting now > > [EMAIL PROTECTED] tartest]# mt -f /dev/nst0 rewind > > [EMAIL PROTECTED] tartest]# tar -tvf /dev/nst0 > > drwxr-xr-x root/root 0 2005-04-01 15:54:53 folderA/ > > -rw-r--r-- root/root 7 2005-04-01 15:54:48 folderA/t1 > > -rw-r--r-- root/root10 2005-04-01 15:54:55 folderA/t2 > > [EMAIL PROTECTED] tartest]# mt -f /dev/nst0 rewind > > [EMAIL PROTECTED] tartest]# tar -rvf /dev/nst0 folderB > > folderB/ > > folderB/t3 > > folderB/t4 > > [EMAIL PROTECTED] tartest]# mt -f /dev/nst0 rewind > > [EMAIL PROTECTED] tartest]# tar -tvf /dev/nst0 > > drwxr-xr-x root/root 0 2005-04-01 15:54:53 folderA/ > > -rw-r--r-- root/root 7 2005-04-01 15:54:48 folderA/t1 > > -rw-r--r-- root/root10 2005-04-01 15:54:55 folderA/t2 > > [EMAIL PROTECTED] tartest]# > > > > > > As you can see, in the end when i do tar -tvf /dev/nst0, only the contents > > of folder A > > are displayed and that of folderB are not displayed. This does not meet > our > > requirement. > > We want the contents of both the folders. > > > > Regards, > > Pooja SIngh. -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. 1st Floor,'C'Wing, Fortune2000, Bandra Kurla Complex, Bandra(East), Mumbai 400051. Maharashtra India Tel: +91-22-3987 Fax: +91-22-39878899 Cell : +91-9820367783 E-mail : [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
