still no backups due to permissions problem in 2.5.1
Dear Amanda maintainers... As already noted, my ssh problems are all solved, BUT... I still have no backups at all, since upgrading to 2.5.1. The server creates the directory on the holdingdisk (that directory has a timestamp as its name), and then Amanda complains that it can't write anything on it. Then it deletes that (still empty) directory. While it lasts, that empty directory is owned by root. Its permissions are drwx--. If it were owned by amanda (my Amanda user is "amanda"), I suspect I wouldn't be having these problems. Or if the permissions included group write/search permissions. The same kind of problem applies to my tapelist file. Amanda changes its permissions, and then it can't read it during the next run. which prevents any tapers from doing any useful work. Does anyone have any ideas about why this is happening? Is my amanda.conf file THAT weird? I'm attaching it herewith. -- Steve Steven R. Newcomb, Consultant Coolheads Consulting Co-editor, Topic Maps International Standard (ISO/IEC 13250) Co-editor, draft Topic Maps -- Reference Model (ISO/IEC 13250-5) [EMAIL PROTECTED] http://www.coolheads.com direct: +1 540 951 9773 main: +1 540 951 9774 fax:+1 540 951 9775 208 Highview Drive Blacksburg, Virginia 24060 USA (Confidential to all US government personnel to whom this private letter is not addressed and who are reading it in the absence of a specific search warrant: You are violating the law and you are co-conspiring to subvert the Constitution that you are sworn to defend. You can either refuse to commit this crime, or you can expect to suffer criminal sanctions in the future, when the current administration of the United States of America has been replaced by one that respects the rule of law. I do not envy you for having to make this difficult choice, but I urge you to make it wisely.) amanda.conf Description: Binary data
Re: amrecover question.
* Lee, Raymond <[EMAIL PROTECTED]> [20060926 16:02]: > Sometimes the files you're recovering are on a tape that's no longer in > the changer, so you must manually insert it into the changer and mount > it to a drive before telling amrecover to continue. > > I think it would be nice if Amanda could mount the tape automatically > without asking you, if it knows that the required tape is already in the > changer. Can it already do this, or will it be a feature in a future > release? Please stop the top-replies and properly indent what you are replying to as otherwize it screws up attribution and makes it hard to sift through the archives afterwards. To get back to your question, in the amanda manpage: amrecover_changer string Default: ''. Amrecover will use the changer if you use 'settape ' and that string is the same as the amrecover_changer setting. As been available since 2.4.3 but I might be mistaken... HTH jf > > Ray > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of McGraw, Robert P. > Sent: Tuesday, September 26, 2006 2:55 PM > To: amanda-users@amanda.org > Subject: amrecover question. > > > I am running amanda-2.5.1 on a Sparc Solaris 10 > > When I run amrecover and do the extract, it tells me what tape needs to > be > mounted. I then have to go to another window and run amtape to mount the > tape. Since it knows what tape to mount, what is the reason to go to > another > window to run amtape to mount the tape? Am I not doing it correctly? Am > I > missing something? > > Thanks > > Robert > > > _ > Robert P. McGraw, Jr. > Manager, Computer System EMAIL: [EMAIL PROTECTED] > Purdue University ROOM: MATH-807 > Department of MathematicsPHONE: (765) 494-6055 > 150 N. University Street FAX: (419) 821-0540 > West Lafayette, IN 47907-2067 > > > > This communication is the property of Qwest and may contain confidential or > privileged information. Unauthorized use of this communication is strictly > prohibited and may be unlawful. If you have received this communication > in error, please immediately notify the sender by reply e-mail and destroy > all copies of the communication and any attachments. -- <° ><
RE: amrecover question.
Sometimes the files you're recovering are on a tape that's no longer in the changer, so you must manually insert it into the changer and mount it to a drive before telling amrecover to continue. I think it would be nice if Amanda could mount the tape automatically without asking you, if it knows that the required tape is already in the changer. Can it already do this, or will it be a feature in a future release? Ray -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of McGraw, Robert P. Sent: Tuesday, September 26, 2006 2:55 PM To: amanda-users@amanda.org Subject: amrecover question. I am running amanda-2.5.1 on a Sparc Solaris 10 When I run amrecover and do the extract, it tells me what tape needs to be mounted. I then have to go to another window and run amtape to mount the tape. Since it knows what tape to mount, what is the reason to go to another window to run amtape to mount the tape? Am I not doing it correctly? Am I missing something? Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
amrecover question.
I am running amanda-2.5.1 on a Sparc Solaris 10 When I run amrecover and do the extract, it tells me what tape needs to be mounted. I then have to go to another window and run amtape to mount the tape. Since it knows what tape to mount, what is the reason to go to another window to run amtape to mount the tape? Am I not doing it correctly? Am I missing something? Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Re: 2.5.1 nitpicks
* Jean-Louis Martineau <[EMAIL PROTECTED]> [20060922 20:16]: > Jean-Francois, > > Could you try this patch? sorry to get back that late... The patched amstat now show the tape usage and amtoc looks fine too. regards, jf > > Jean-Louis > > Jean-Francois Malouin wrote: > >Hello, > > > >I've been testing 2.5.1 for a few days now and I have 2 nitpicks: > > > >With 2.4.5 'amtoc -a' produces outputfile with names > >.toc as per the man page. This doesn't seem to be the > >case anymore with 2.5.1 where I just get a file called "tape.toc". And > >in the situation where more than one tape were used (runtapes>1) it > >simply clobbers all of them except for the last tape. I had a brief > >look at the diff between the 2.4.5 and 2.5.1 but couldn't find > >anything obvious. > > > >amstatus doesn't tell you which tapes are used and how much stuff was > >put on them. > > > >regards > >jf > > > -- <° ><
Re: No more holding disk space
I'm sorry, missed the early part of the thread. You are doing amdump and getting "no more holding disk" ? Amanda usually delays some partitions until it has enough holding disk to capture the DLE. Problems can arise when you run out of tape, a DLE is larger than estimated or something else is writing to the partition. - Does anything else write to the work area partition ? - Are there DLE's from previous runs that need to be flushed ? - Are the estimates somehow bad ?? At our site we've seen that the estimates where of a given size but much larger to backup when users added data to the the DLE during the amdump run. - Note - no way for amanda or any other backup software to account for such a moving target. On Tue, Sep 26, 2006 at 01:17:33PM -0400, Jon LaBadie wrote: > Please don't use html. > > I had trouble finding what you wrote. > > > On Tue, Sep 26, 2006 at 11:02:13AM -0500, James Wilson wrote: > > > > > > > > > > I have a server with 60 GB of disk space left after installing > > everything. I thought I gave amanda the whole 60 gigs. Should it need > > more that that? > > > > Jon LaBadie wrote: > > > type="cite"> > > On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: > > > > > > Hey All, > > > > Lately I've been gettting the Failed [no more holding disk space] for > > this one client. Is there something I can do to fix this? It has been > > backing up fine until Sunday night and Monday night. > > > > > > FAILURE AND STRANGE DUMP SUMMARY: > > amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE > > amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE > > vikings.transolutions.net /opt lev 1 STRANGE > > amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE > > amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE > > amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE > > amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE > > amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE > > amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED > > [no more holding disk space] > > > > > > > > > > At the risk of sounding pedantic, > > increase the amount of holding disk space. > > > > It doesn't have to be a single space, I'm currently using two > > and my previous installation had four holding disks (HDs). > > Just empty directories on different file systems that I let > > amanda use all the available space except one or two GB. > > And I set the chunk size to one or two GB so it is easy to > > split a DLE among the various HDs. > > > > You might also see if some junk is still in the HD. > > > > You might also split up the DLE so it doesn't require so much HD. > > > > It also sounds as if the estimate is incorrect as I don't think > > amanda will write to the HD if it expects the size to be bigger > > than the available space. Instead it would send that DLE direct > > to tape. > > > > > > > > > > > > > > Depends on what you are backing up. The entire DLE goes to the > holding disk before being taped. So if you are backing up a > 1 TB DLE, 60 GB is tiny. > > If you are backing up a bunch of 30 GB DLEs, not many can fit > on the holding disk at the same time. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) --- 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: No more holding disk space
Please don't use html. I had trouble finding what you wrote. On Tue, Sep 26, 2006 at 11:02:13AM -0500, James Wilson wrote: > > > > > I have a server with 60 GB of disk space left after installing > everything. I thought I gave amanda the whole 60 gigs. Should it need > more that that? > > Jon LaBadie wrote: > type="cite"> > On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: > > > Hey All, > > Lately I've been gettting the Failed [no more holding disk space] for > this one client. Is there something I can do to fix this? It has been > backing up fine until Sunday night and Monday night. > > > FAILURE AND STRANGE DUMP SUMMARY: > amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE > amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE > vikings.transolutions.net /opt lev 1 STRANGE > amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE > amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE > amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE > amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE > amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE > amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED > [no more holding disk space] > > > > > At the risk of sounding pedantic, > increase the amount of holding disk space. > > It doesn't have to be a single space, I'm currently using two > and my previous installation had four holding disks (HDs). > Just empty directories on different file systems that I let > amanda use all the available space except one or two GB. > And I set the chunk size to one or two GB so it is easy to > split a DLE among the various HDs. > > You might also see if some junk is still in the HD. > > You might also split up the DLE so it doesn't require so much HD. > > It also sounds as if the estimate is incorrect as I don't think > amanda will write to the HD if it expects the size to be bigger > than the available space. Instead it would send that DLE direct > to tape. > > > > > > Depends on what you are backing up. The entire DLE goes to the holding disk before being taped. So if you are backing up a 1 TB DLE, 60 GB is tiny. If you are backing up a bunch of 30 GB DLEs, not many can fit on the holding disk at the same time. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: No more holding disk space
Thanks for the reply Jon. I thought I had 60 gig specified but infact I only had 10gig specified. Sorry for the inconvience. Jon LaBadie wrote: On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: Hey All, Lately I've been gettting the Failed [no more holding disk space] for this one client. Is there something I can do to fix this? It has been backing up fine until Sunday night and Monday night. FAILURE AND STRANGE DUMP SUMMARY: amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE vikings.transolutions.net /opt lev 1 STRANGE amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED [no more holding disk space] At the risk of sounding pedantic, increase the amount of holding disk space. It doesn't have to be a single space, I'm currently using two and my previous installation had four holding disks (HDs). Just empty directories on different file systems that I let amanda use all the available space except one or two GB. And I set the chunk size to one or two GB so it is easy to split a DLE among the various HDs. You might also see if some junk is still in the HD. You might also split up the DLE so it doesn't require so much HD. It also sounds as if the estimate is incorrect as I don't think amanda will write to the HD if it expects the size to be bigger than the available space. Instead it would send that DLE direct to tape.
Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
Date: Tue, 26 Sep 2006 07:47:48 -0400 David Trusty wrote: Hi, I checked the logs. There is no error message, and I have no cron running either. I can duplicate the problem every time. Is it always at the same place (part 51)? Yes. Could you provide the "LABEL=" line from the amidxtaped.*.debug file? amidxtaped: time 0.053: > LABEL=104:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175;105:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56 From: Jean-Louis Martineau <[EMAIL PROTECTED]> To: David Trusty <[EMAIL PROTECTED]> CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive What is the output of `amadmin find helix /mnt/dataa/invention`? I want to know if the part 51 should be read from the same tape or the next tape. Jean-Louis Interestingly, the amrecover says that it will need two tapes. When I put the first tape in, it reads it for a long time, gets the error I noted below, and then just gives up on asking for the second tape. Any other ideas? Thanks, David From: Ian Turner <[EMAIL PROTECTED]> To: "David Trusty" <[EMAIL PROTECTED]> CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive Date: Mon, 25 Sep 2006 14:27:19 -0400 The "device or resource busy" message comes from your operating system. Normally this error means that two programs tried to access the tape device simultaneously. I suspect one of the following: 1) A hardware problem or kernel bug. Check your kernel debug logs. 2) A cron job that accesses the tape. Check your cron log. --Ian On Friday 22 September 2006 19:21, David Trusty wrote: > Hi, > > I am trying to restore a file which is on a backup > which used tape spanning. I am running version 2.5.1. > > The backup says it completed successfully, but I get > the errors below from amrecover and imidxtaped. > > Any ideas? > > Thanks!! > > David > > amrecover output > > Looking for tape 104... > tar: Read 8192 bytes from - > tar: Unexpected EOF in archive > tar: Error is not recoverable: exiting now > Extractor child exited with status 2 > > > debug log for amidxtaped > ~~~ > midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: restore read error: Device or resource busy > amidxtaped: time 2988.892: restore read error: Device or resource busy > amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006 -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: No more holding disk space
I have a server with 60 GB of disk space left after installing everything. I thought I gave amanda the whole 60 gigs. Should it need more that that? Jon LaBadie wrote: On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: Hey All, Lately I've been gettting the Failed [no more holding disk space] for this one client. Is there something I can do to fix this? It has been backing up fine until Sunday night and Monday night. FAILURE AND STRANGE DUMP SUMMARY: amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE vikings.transolutions.net /opt lev 1 STRANGE amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED [no more holding disk space] At the risk of sounding pedantic, increase the amount of holding disk space. It doesn't have to be a single space, I'm currently using two and my previous installation had four holding disks (HDs). Just empty directories on different file systems that I let amanda use all the available space except one or two GB. And I set the chunk size to one or two GB so it is easy to split a DLE among the various HDs. You might also see if some junk is still in the HD. You might also split up the DLE so it doesn't require so much HD. It also sounds as if the estimate is incorrect as I don't think amanda will write to the HD if it expects the size to be bigger than the available space. Instead it would send that DLE direct to tape.
No more holding disk space
Hey All, Lately I've been gettting the Failed [no more holding disk space] for this one client. Is there something I can do to fix this? It has been backing up fine until Sunday night and Monday night. FAILURE AND STRANGE DUMP SUMMARY: amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE vikings.transolutions.net /opt lev 1 STRANGE amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED [no more holding disk space]
Re: No more holding disk space
On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: > Hey All, > > Lately I've been gettting the Failed [no more holding disk space] for > this one client. Is there something I can do to fix this? It has been > backing up fine until Sunday night and Monday night. > > > FAILURE AND STRANGE DUMP SUMMARY: > amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE > amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE > vikings.transolutions.net /opt lev 1 STRANGE > amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE > amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE > amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE > amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE > amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE > amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED > [no more holding disk space] > At the risk of sounding pedantic, increase the amount of holding disk space. It doesn't have to be a single space, I'm currently using two and my previous installation had four holding disks (HDs). Just empty directories on different file systems that I let amanda use all the available space except one or two GB. And I set the chunk size to one or two GB so it is easy to split a DLE among the various HDs. You might also see if some junk is still in the HD. You might also split up the DLE so it doesn't require so much HD. It also sounds as if the estimate is incorrect as I don't think amanda will write to the HD if it expects the size to be bigger than the available space. Instead it would send that DLE direct to tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
David Trusty wrote: Hi, I checked the logs. There is no error message, and I have no cron running either. I can duplicate the problem every time. Is it always at the same place (part 51)? Could you provide the "LABEL=" line from the amidxtaped.*.debug file? What is the output of `amadmin find helix /mnt/dataa/invention`? I want to know if the part 51 should be read from the same tape or the next tape. Jean-Louis Interestingly, the amrecover says that it will need two tapes. When I put the first tape in, it reads it for a long time, gets the error I noted below, and then just gives up on asking for the second tape. Any other ideas? Thanks, David From: Ian Turner <[EMAIL PROTECTED]> To: "David Trusty" <[EMAIL PROTECTED]> CC: amanda-users@amanda.org Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive Date: Mon, 25 Sep 2006 14:27:19 -0400 The "device or resource busy" message comes from your operating system. Normally this error means that two programs tried to access the tape device simultaneously. I suspect one of the following: 1) A hardware problem or kernel bug. Check your kernel debug logs. 2) A cron job that accesses the tape. Check your cron log. --Ian On Friday 22 September 2006 19:21, David Trusty wrote: > Hi, > > I am trying to restore a file which is on a backup > which used tape spanning. I am running version 2.5.1. > > The backup says it completed successfully, but I get > the errors below from amrecover and imidxtaped. > > Any ideas? > > Thanks!! > > David > > amrecover output > > Looking for tape 104... > tar: Read 8192 bytes from - > tar: Unexpected EOF in archive > tar: Error is not recoverable: exiting now > Extractor child exited with status 2 > > > debug log for amidxtaped > ~~~ > midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk > /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar > amidxtaped: restore read error: Device or resource busy > amidxtaped: time 2988.892: restore read error: Device or resource busy > amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006 -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
