unsubscribe
Re: level 0 dumps getting overwritten?
Darin Dugan wrote: At 04:01 PM 8/28/2001, Kurt Yoder wrote: Hello My level 0 dumps seem to be getting overwritten. I run amadmin and see only level 1 dumps: [...] Am I setting up my configuration file correctly? I've got: dumpcycle 7 days runspercycle 6 tapecycle 2 tapes So you're telling Amanda to make sure she has a full (level 0) backup of everything at least every 7 days, spread into 6 runs. But you're only giving her 2 tapes! *Buy more tapes!* Really. I've got a third tape in my tapelist so I can flush dumps from my holding disk. I'm trying to do 6 backups every 7 days (the 7th day has a weekly backup set that isn't part of this configuration) using two tapes (alternate between them). If you absolutely have to stick with two tapes, you pretty much need to do full dumps every run to be safe. (Take for instance the case where tape1 has level0's, tape2 has level1's, you go to do level0's on tape1 again and there's an error and the tape is fubar'd. You've just lost all hope of a restore.) Use 'dumpcycle 0' in the dumptype to force level 0's. I must be setting up my numbers wrong, or? Or you need more tapes! Thanks for the info. I am probably still a bit foggy on the concepts behind dumpcycle, runspercycle, and tapecycle. Questions: In my case, I _must_ use at least 6 tapes in order for amanda not to overwrite any of its level 0 backups? If I wanted to use only 2 tapes, I would need to set runspercycle to 2? tapecycle must always be = runspercycle? Are there any advantages to making tapecycle runspercycle? If I have tapecycle at 6, and define 7 tapes in the tapelist, Amanda cycles through all 7 tapes, with a level 0 at a minimum of every 6 runs (every 7 days, in my case)?
trouble on freebsd
Hello I am trying to get the Amanda client working on a FreeBSD4 box. I installed 2.4.2p1 (and also p2 in trying to resolve this). I run the dump, and get two different errors on two boxes: FAILED AND STRANGE DUMP DETAILS: /-- aragorn.sh /dev/da0s1a lev 0 FAILED [/usr/bin/tar returned 1] sendbackup: start [aragorn.shcorp.com:/dev/da0s1a level 0] sendbackup: info BACKUP=/usr/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/tar -f... - sendbackup: info end ? gtar: ./dev/rsa0.ctl: minor number too large; not dumped | Total bytes written: 186224640 sendbackup: error [/usr/bin/tar returned 1] \ /-- galadriel. /dev/ad0s1g lev 0 FAILED [data timeout] sendbackup: start [galadriel.shcorp.com:/dev/ad0s1g level 0] sendbackup: info BACKUP=/usr/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/tar -f... - sendbackup: info end ? sendbackup: index tee cannot write [Broken pipe] sendbackup: error [/usr/bin/tar got signal 13, index returned 1] \ I've tried various gtar versions, including 1.11.2, 1.13, and 1.13.19, but they all give me errors. Does anyone know how to fix this?
RE: Still a newbie...but getting somewhere...amlabel troubles
Hi Paul... I tried that, and I got bash:/root/.bashrc:Permission denied -Original Message- From: Bort, Paul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:50 PM To: 'Rebecca Pakish'; '[EMAIL PROTECTED]' Subject: RE: Still a newbie...but getting somewhere...amlabel troubles In the same directory as amanda.conf, try this: su -c amanda touch tapetype This will create a blank tapetype file that amanda can store info about tapes in. -Original Message- From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:46 PM To: '[EMAIL PROTECTED]' Subject: Still a newbie...but getting somewhere...amlabel troubles Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called tapelist that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c amlabel backup testtape01 bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
Re: Client Installationn on Solaris
On Wed, 29 Aug 2001 at 11:33am, chandra wrote I think I have stuffed up the installation of a client version of amanda on a sun sparc running solaris 2.5. The configure command I issued was ./configure --without server --with-user=amanda --with-group=sys. Somehow I ^ Is that a typo in the email, or is that the actual command? There should be a dash there... get the feeling this is incomplete. Can someone please verify that this is right or is there something I missed out when I issued that command. What errors are you getting? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: trouble on freebsd
On Wed, 29 Aug 2001 at 11:09am, Kurt Yoder wrote /-- aragorn.sh /dev/da0s1a lev 0 FAILED [/usr/bin/tar returned 1] sendbackup: start [aragorn.shcorp.com:/dev/da0s1a level 0] *snip* /-- galadriel. /dev/ad0s1g lev 0 FAILED [data timeout] sendbackup: start [galadriel.shcorp.com:/dev/ad0s1g level 0] If I'm not mistaken, you should use directory names (not the corresponding devices) when using tar. I've tried various gtar versions, including 1.11.2, 1.13, and 1.13.19, but they all give me errors. Does anyone know how to fix this? Stick with 1.13.19. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Still a newbie...but getting somewhere...amlabel troubles
I compiled amanda...tried rpm but something strange happened. (Can't remember what now) Actually when I checked my /etc/passwd file $HOME for amanda was set to /var/lib/amanda, so I changed it to /home/amanda. The entry in passwd now looks like this: amanda:x:33:6:Amanda user:/home/amanda:/bin/bash I had already changed the ownership on the amanda directory...in fact /usr/local/etc shows ownership to amanda and group ownership disk (group 6, to which amanda belongs) Actually I ran an $su amanda -c touch tapetype which did create a tapetype file in my /usr/local/etc/amanda/backup dir. Then I was able to run my $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking label, done. I now have a tapelist file in my /usr/local/etc/amanda/backup file...so it appears to have worked...but how do I get rid of this bash permission denied message??? -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 4:03 PM To: Rebecca Pakish Cc: '[EMAIL PROTECTED]' Subject: Re: Still a newbie...but getting somewhere...amlabel troubles On Tue, 28 Aug 2001 at 2:46pm, Rebecca Pakish wrote Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) Did you compile amanda or install the RPM? In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied This says that the $HOME of the user amanda specified in /etc/passwd is /root, but the amanda user does not have read access to that directory. I would fix this by giving amanda a different $HOME (like /home/amanda). rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied The file 'tapelist' is created after the first successful amlabel, which is why you don't have one yet. It lives in the same directory as the amanda.conf and disklist for the configuration -- in this case /usr/local/etc/amanda/backup. So, amanda must not have write permissions in that directory. The easiest way to fix that would be 'chown -R amanda /usr/local/etc/amanda', which will give the user amanda ownership of /usr/local/etc/amanda and all the files and directories inside it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Still a newbie...but getting somewhere...amlabel troubles
On Wed, 29 Aug 2001 at 10:49am, Rebecca Pakish wrote $su amanda -c touch tapetype which did create a tapetype file in my /usr/local/etc/amanda/backup dir. Then I was able to run my $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking label, done. I now have a tapelist file in my /usr/local/etc/amanda/backup file...so it appears to have worked...but how do I get rid of this bash permission denied message??? OK, I think I see what's going on. You're running that su as root, right? Well, it's not giving amanda (the user) its own environment, i.e. $HOME is still set to /root (root's home). So, the user amanda, in starting its shell to run the command, tries to parse $HOME/.bashrc, and can't, because it doesn't have permission. Try this: su - amanda -c amlabel backup testtape01 This will give amanda its environment. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: DDS2 auto-changer
I'm sending this message so that it will go in the archives to help others who may have questions similar to Dave and mine. Date: Tue, 28 Aug 2001 19:24:09 -0700 From: Dave Close [EMAIL PROTECTED] After I wrote to you, I found several on-line references which helped clarify things a bit. Although one of them repeated that idea that the drive would automatically step to subsequent tapes, the others were in agreement on a different interpretation. Some of these docs were software manuals from companies which list the drive as one of the ones they support, so I'm guessing they know. The consensus seems to be that the drive goes into sequential mode when you manually select a slot. It stays in that mode until you send any SCSI command except UNLOAD or reach the end of the cartridge. You can start with any slot, not just #1. Moving to the next slot requires the software to send an UNLOAD command; it is not fully automatic. When the drive gets UNLOAD while in sequential mode, it both unloads the current tape and loads the one from the next slot. Loading the next one could be construed as automatic, since you didn't explicitly ask for that, and may be the source of the confusion in the documentation. As I read this, the drive does not behave as if the tapes were four or more times their actual size. The software must be aware when the end of a tape is reached and take some action to load the next tape. So Seagate is deliberately or incompetently misleading us. If this agrees with your observations, feel free to relay my comments to the discussion group (of which I am not a member). -- Dave Close, Compata, Costa Mesa CA +1 714 434 7359 [EMAIL PROTECTED] [EMAIL PROTECTED] The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in; we're computer professionals. We cause accidents. -- Nathaniel Borenstein
Re: trouble on freebsd
Hello, Kurt Yoder [EMAIL PROTECTED] wrote: I am trying to get the Amanda client working on a FreeBSD4 box. [...] FAILED AND STRANGE DUMP DETAILS: /-- aragorn.sh /dev/da0s1a lev 0 FAILED [/usr/bin/tar returned 1] sendbackup: start [aragorn.shcorp.com:/dev/da0s1a level 0] sendbackup: info BACKUP=/usr/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/tar -f... - sendbackup: info end ? gtar: ./dev/rsa0.ctl: minor number too large; not dumped | Total bytes written: 186224640 sendbackup: error [/usr/bin/tar returned 1] \ I don't think you are using GNU tar here. I get that error when using the system tar (/usr/bin/tar -- as reported above), but not GNU tar 1.13.19 as installed by the port (/usr/local/bin/gtar). Kinda funny that GNU tar knows more about the large device numbers than the system tar! Anyway, you'll need to make sure you configure your clients with the --with-gnutar=/usr/local/bin/gtar option. /-- galadriel. /dev/ad0s1g lev 0 FAILED [data timeout] sendbackup: start [galadriel.shcorp.com:/dev/ad0s1g level 0] sendbackup: info BACKUP=/usr/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/tar -f... - sendbackup: info end ? sendbackup: index tee cannot write [Broken pipe] sendbackup: error [/usr/bin/tar got signal 13, index returned 1] \ This one is easy... backups run with tar take a long time, and this one is taking longer than Amanda is waiting for it. You can use the dtimeout setting in your amanda.conf file to make Amanda wait longer. There are comments in the example amanda.conf file about this. Also, you'll want to reconfigure this host to use GNU tar. You might also consider using dump to backup your systems. Both estimates and dumps are much, much quicker on FreeBSD when dump is used rather than tar. If there are parts of the filesystem that you don't want backed up, creative use of the chflags nodump command can help replace the exclusion options of tar. I hope this helps, -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
Re: reading tapes
Hello, Dave Reeves [EMAIL PROTECTED] wrote: [...] I guess I want to see what is on the second tape to see for sure if anything was dumped to it and figure out how to get amanda to write to the second tape. BTW, the entire dump is about 26 gigs, the tapes are 20 gigs. There's all sorts of ways to look at what's on the tape. One way is to put the tape in the drive, make sure it's rewound, and then do something like this: % amrestore /dev/nrsa0 no-such-host Replace the device name as appropriate, of course. Assuming that you don't have a host named no-such-host, this will cause amrestore to scan the entire tape looking for a non-existent file. As it goes merrily on its way, it'll print out interesting stuff, including a list of the files that are actually on the tape. Something like this: amrestore: 0: skipping start of tape: date 20010829 label DLT000 amrestore: 1: skipping urchin.wossname.net._.20010829.1 amrestore: 2: skipping minime.wossname.net._.20010829.1 [etc.] amrestore: 24: skipping akira.wossname.net._usr_src-all.20010829.1 amrestore: 25: skipping akira.wossname.net._usr_local.20010829.1 amrestore: 26: reached end of tape: date 20010829 If any scary errors are reported, you can probably figure that Amanda won't be able to use the tape for restores. Another way is to use the dd command. You can look at the various Amanda headers on the tape, or even pull the files back onto disk. Here's the kind of thing I do: mt rewind dd if=/dev/nrsa0 bs=32k # read the Amanda tape label dd if=/dev/nrsa0 bs=32k count=1 # read the header for the first image mt fsf 1# skip the rest of the first image dd if=/dev/nrsa0 bs=32k count=1 # read the header for the second image dd if=/dev/nrsa0 of=/tmp/bkup.img bs=32k # read the second image into a file dd if=/dev/nrsa0 of=/dev/null bs=32k# read and discard the entire third image # just tests to make sure image is readable dd # Keep on going through the tape Again, scary errors are bad. Hope this helps, -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
RE: Still a newbie...but getting somewhere...amlabel troubles
Sorry about the preceeding message, I hit the wrong button. On 29 Aug 2001, at 10:29, Rebecca Pakish wrote: Hi Paul... I tried that, and I got bash:/root/.bashrc:Permission denied This probably means that the home directory of the amanda user is /root, where he has no read/write permission. Try to change to another (/home/amanda for instance) in /etc/passwd. Don't forget to create the directory if it doesn't exist and set the permission correctly. As for the couldn't write tapelist: Permission denied message, it probably is also a permission problem : be sure that the directory /usr/local/etc/amanda and all the subdirectories belong to amanda You can do a chown -R amanda amanda as root in the directory /usr/local/etc to be sure. Raoul -Original Message- From: Bort, Paul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:50 PM To: 'Rebecca Pakish'; '[EMAIL PROTECTED]' Subject: RE: Still a newbie...but getting somewhere...amlabel troubles In the same directory as amanda.conf, try this: su -c amanda touch tapetype This will create a blank tapetype file that amanda can store info about tapes in. -Original Message- From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:46 PM To: '[EMAIL PROTECTED]' Subject: Still a newbie...but getting somewhere...amlabel troubles [snip] What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied
RE: Still a newbie...but getting somewhere...amlabel troubles
On 29 Aug 2001, at 10:29, Rebecca Pakish wrote: Hi Paul... I tried that, and I got bash:/root/.bashrc:Permission denied -Original Message- From: Bort, Paul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:50 PM To: 'Rebecca Pakish'; '[EMAIL PROTECTED]' Subject: RE: Still a newbie...but getting somewhere...amlabel troubles In the same directory as amanda.conf, try this: su -c amanda touch tapetype This will create a blank tapetype file that amanda can store info about tapes in. -Original Message- From: Rebecca Pakish [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 3:46 PM To: '[EMAIL PROTECTED]' Subject: Still a newbie...but getting somewhere...amlabel troubles Hi all... Thank you for all of your help on the ./tapetype issue. I learned a lot about my drive from the Seagate site (they have excellent documentation as far as I'm concerned) got my hardware compression turned off. Been working on the amanda.conf file, feel like I'm prepared to label my first tape and dump something! Again, running RH 7.1 on a Dell 333 with a SCSI Seagate external and just a 90mm tape for starters. (Had to download the mt command from the rpm site, but everything seems to be effectively communicating) In amanda.conf: labelstr ^testtape[0-9][0-9] (**amanda.conf is in /usr/local/etc/amanda/backup**) What's happening... $su amanda -c amlabel backup testtape01 bash: /root/.bashrc: Permission denied rewinding, reading label, not an amanda tape rewinding, writing label testape01, checking labelamlabel: couldn't write tapelist: Permission denied And then I looked for the file called tapelist that the amlabel man page said it would write to, and I couldn't find it to change it's permissions. When I went back to re-execute the amlabel command so I could write down the error, this is what happens: $su amanda -c amlabel backup testtape01 bash: /root.bashrc: Permission denied rewinding, reading label testtape01 rewinding, writing label testtape01, checking labelamlabel: couldn't write tapelist: Permission denied Which, I have to admit, for a girl who just learned how to tar on Friday and rpm yesterday, I'm pretty jacked to see that it read the label as testtape01 that second time! But of course, it still isn't right. oops. Can someone please help point me in the right direction? Thanks!! Rebecca
AIX 4.3.3 and MNTTAB
I have seen several threads describing this problem. But they have all ended without resolution. Of course, I have now run into this problem. I am using the C for AIX compiler. ./configure seems to recognize I have an mntent.h and no mnttab.h and makes allowances. I am currently on my Linux system and this mntent.h has a constant #define MNTTAB _PATH_MNTTAB pointing back to paths.h as a deprecated alias. There is no mention of MNTTAB in mntent.h in AIX. I am planning to wander back to my AIX machine (about 20 miles away and inside a firewall) and try to add this. But, does anyone know if this is the AIX 4.3.3 resolution? Rick
Compiling Amanda on AIX 4.3.3 (was: AIX 4.3.3 and MNTTAB)
Rick, For what it's worth, I just used gcc and other GNU tools such as automake, autoconf, etc. Amanda compiled and works fine using these tools. You can get them from IBM at the following address: http://www-1.ibm.com/servers/aix/products/aixos/linux/download.html Anthony Valentine -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 29, 2001 9:37 AM To: [EMAIL PROTECTED] Subject: AIX 4.3.3 and MNTTAB I have seen several threads describing this problem. But they have all ended without resolution. Of course, I have now run into this problem. I am using the C for AIX compiler. ./configure seems to recognize I have an mntent.h and no mnttab.h and makes allowances. I am currently on my Linux system and this mntent.h has a constant #define MNTTAB _PATH_MNTTAB pointing back to paths.h as a deprecated alias. There is no mention of MNTTAB in mntent.h in AIX. I am planning to wander back to my AIX machine (about 20 miles away and inside a firewall) and try to add this. But, does anyone know if this is the AIX 4.3.3 resolution? Rick
Another Question
Nobody answered my last question on reading indices, but I
eventually determined that the tapelist file had become corrupt, which
got me four weeks' worth of indices that I hadn't had before!
Anyway, today my problem is that amflush is failing. I forgot
to change a tape last night, and dumps happened to the holding disk --
no problem there. I tried to run amflush, though, and it failed on
several filesystems. I am guessing it's a failure of the files on the
holding disk instead of the tape (as the tape does have good data!).
What can cause this sort of thing?
Here's the amflush report:
The dumps were flushed to tape DailySet159.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
bertha /usr2 lev 1 FAILED [input: Can't read data: : Input/output error]
us /export/home/us0 lev 3 FAILED [input: Can't read data: :
+Input/output error]
us /export/home/us1 lev 4 FAILED [input: Can't read data: :
+Input/output error]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:14
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:13 0:00 0:13
Tape Size (meg) 2198.90.0 2198.9
Tape Used (%) 16.10.0 16.1 (level:#disks ...)
Filesystems Taped 2 0 2 (1:1 2:1)
Avg Tp Write Rate (k/s) 2873.5-- 2873.5
^L
NOTES:
amflush: /home/amanda/20010829/bertha._usr2.1: taper error, leaving file on disk
amflush: /home/amanda/20010829/us._export_home_us0.3: taper error, leaving file on
disk
amflush: /home/amanda/20010829/us._export_home_us1.4: taper error, leaving file on
disk
amflush: Could not rmdir /home/amanda/20010829. Check for cruft.
taper: tape DailySet159 kb 2292256 fm 5 [OK]
^L
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
bertha /usr2 1 FAILED ---
us -t/home/us0 3 FAILED ---
us -t/home/us1 4 FAILED ---
us -t/home/us2 2 27876472240032 80.4 N/A N/A 12:582880.9
us /var/mail 1 43807 11648 26.6 N/A N/A0:061930.9
(brought to you by Amanda version 2.4.2p2)
Any response would be appreciated.
-- Lorrie
Compiling amanda on an (ugh) Windows box?
Does anyone know of a decent compiler for windows thats not a bank breaker? I'd like to see if its buildable for the general run of W95 and W98 machines. And has anyone made amanda work as client on a windows box other than via samba? In other words, am I just spinning my wheels to even think about it? Cheers, Gene
Re: Another Question
On Wed, 29 Aug 2001 at 1:57pm, Lorrie Wood wrote no problem there. I tried to run amflush, though, and it failed on several filesystems. I am guessing it's a failure of the files on the holding disk instead of the tape (as the tape does have good data!). Don't be so sure... FAILURE AND STRANGE DUMP SUMMARY: bertha /usr2 lev 1 FAILED [input: Can't read data: : Input/output error] us /export/home/us0 lev 3 FAILED [input: Can't read data: : +Input/output error] us /export/home/us1 lev 4 FAILED [input: Can't read data: : +Input/output error] *snip* NOTES: amflush: /home/amanda/20010829/bertha._usr2.1: taper error, leaving file on disk amflush: /home/amanda/20010829/us._export_home_us0.3: taper error, leaving file on disk amflush: /home/amanda/20010829/us._export_home_us1.4: taper error, leaving file on disk amflush: Could not rmdir /home/amanda/20010829. Check for cruft. taper: tape DailySet159 kb 2292256 fm 5 [OK] taper ran into an Input/output error trying to put those disk images onto tape. In reality, taper is just telling you what the OS told it. Check your system logs for related messages -- they should tell you what type of Input/output error occurred. I've seen old tape drives/tapes/combos thereof which will write random amounts of data (sometimes a whole night's worth, sometimes not) before giving such errors. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Compiling amanda on an (ugh) Windows box?
On Wed, 29 Aug 2001 at 5:24pm, Gene Heskett wrote Does anyone know of a decent compiler for windows thats not a bank breaker? I'd like to see if its buildable for the general run of W95 and W98 machines. And has anyone made amanda work as client on a windows box other than via samba? In other words, am I just spinning my wheels to even think about it? ISTR that people have gotten inetd running under cygwin. If you can get that going, plus tar (probably included in the distro), plus amandad, you may have a shot. I have no idea if amanda will compile in cygwin. Of course, I may be recalling for NT/2K, and not 95/98, but who knows. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Another Question
On Wed, Aug 29, 2001 at 06:04:51PM -0400, Joshua Baker-LePain wrote: On Wed, 29 Aug 2001 at 1:57pm, Lorrie Wood wrote no problem there. I tried to run amflush, though, and it failed on several filesystems. I am guessing it's a failure of the files on the holding disk instead of the tape (as the tape does have good data!). Don't be so sure... But I do restores from amanda stuff all the time -- the last two I/O errors were in flush reports, not dump reports. Hm. taper ran into an Input/output error trying to put those disk images onto tape. In reality, taper is just telling you what the OS told it. Check your system logs for related messages -- they should tell you what type of Input/output error occurred. I don't see it in the logs of either the server or the client. Moreover, an error *reading* data would seem to point to the dump file, wouldn't it? I've seen old tape drives/tapes/combos thereof which will write random amounts of data (sometimes a whole night's worth, sometimes not) before giving such errors. But it backs up (and restores!) consistently -- the only problem is whenit has to dump to disk, and I have to flush from disk. I care about this, as I'll soon be doing some large dumps on Friday nights, which will have to be held there until I get in Monday morning, and, well, they won't be any good to me if they're corrupt... -- Lorrie
Re: Another Question
Check your system logs. If you think there's an I/O error reading the dump file, I'd suggest dd if=/your/dump/file of=/dev/null which should elicit a similar error while trying to read your whole file. I'd also suggest your favorite disk utility. On Linux that'd be badblocks which can be asked to read every block on a partition, counting which ones it runs into difficulty with. I'd expect most Unix-like OSs have some such utility. If you confirm disk errors on your dump disk, run don't walk to your hard drive vendor for a new hard drive. Your data is no doubt worth a whole lot more than you'd pay for a hard drive!! On Wed, Aug 29, 2001 at 03:23:49PM -0700, Lorrie Wood wrote: On Wed, Aug 29, 2001 at 06:04:51PM -0400, Joshua Baker-LePain wrote: On Wed, 29 Aug 2001 at 1:57pm, Lorrie Wood wrote no problem there. I tried to run amflush, though, and it failed on several filesystems. I am guessing it's a failure of the files on the holding disk instead of the tape (as the tape does have good data!). Don't be so sure... But I do restores from amanda stuff all the time -- the last two I/O errors were in flush reports, not dump reports. Hm. taper ran into an Input/output error trying to put those disk images onto tape. In reality, taper is just telling you what the OS told it. Check your system logs for related messages -- they should tell you what type of Input/output error occurred. I don't see it in the logs of either the server or the client. Moreover, an error *reading* data would seem to point to the dump file, wouldn't it? I've seen old tape drives/tapes/combos thereof which will write random amounts of data (sometimes a whole night's worth, sometimes not) before giving such errors. But it backs up (and restores!) consistently -- the only problem is whenit has to dump to disk, and I have to flush from disk. I care about this, as I'll soon be doing some large dumps on Friday nights, which will have to be held there until I get in Monday morning, and, well, they won't be any good to me if they're corrupt... -- Lorrie -- Dan Wilder
Re: Another Question
Hello, [EMAIL PROTECTED] said: [...] Anyway, today my problem is that amflush is failing. I forgot to change a tape last night, and dumps happened to the holding disk -- no problem there. I tried to run amflush, though, and it failed on several filesystems. I am guessing it's a failure of the files on the holding disk instead of the tape (as the tape does have good data!). What can cause this sort of thing? I had some similar trouble once when my holding disk went bad. You might try reading each file from the disk in its entirety. For example: dd if=/home/amanda/20010829/bertha._usr2.1 of=/dev/null bs=32k Check that the records in/out that dd reports matches the file size. If that works for all of the images and dd doesn't report any IO errors, then I guess the tape is what's left to look at. You might try running amflush again onto a different tape. -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
