disk offline?
Hi, so my amanda setup is coming along pretty nicely... i added two clients to my setup yesterday though, and there are some errors that came up in my email... i don't really understand them: FAILURE AND STRANGE DUMP SUMMARY: devdb.tons /dev/ida/c0d0p2 lev 0 FAILED [disk /dev/ida/c0d0p2 offline on devdb.tonservices.com?] gatorade.t /dev/sda6 lev 0 STRANGE Ok, the whole /dev/ida/c0d0p2 thing is a word device i will admit, but it's definitely not offline... not sure what's going on there... here's the STRANGE stuff: FAILED AND STRANGE DUMP DETAILS: /-- gatorade.t /dev/sda6 lev 0 STRANGE sendbackup: start [gatorade.tonservices.com:/dev/sda6 level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end ? gtar: ./ton/spool/doc_send/fax/oldstuff/064106020107: Warning: Cannot st at: No such file or directory | gtar: ./tmp/.font-unix/fs-1: socket ignored ? gtar: ./ton/spool/doc_send/fax/oldstuff/064106020107/01.tif: Warning: Ca nnot stat: No such file or directory | gtar: ./var/lib/mysql/mysql.sock: socket ignored | Total bytes written: 11511255040 (11GB, 8.7MB/s) sendbackup: size 11241460 sendbackup: end ok, so i guess tar probably has problems w/ sockets? (that isn't so big of a deal), what is a problem is that it shouldn't even be backing up anything in /tmp/ or oldstuff (here's my exclude file): ./tmp/* ./proc/* ./dev/* *oldstuff* ./mnt/* ./opt/naroot/* ./var/tmp/* ./var/www/* ./sys/* there's another thread on the whole amanda ignoring excludes going on right now, but it doesn't seem like any definite conclusion has been reached. is this a bug, or do i just have a badly formed exclude file? Thanks a lot, Cameron Matheson __ Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html
Re: disk offline?
Cameron Matheson wrote: FAILURE AND STRANGE DUMP SUMMARY: devdb.tons /dev/ida/c0d0p2 lev 0 FAILED [disk /dev/ida/c0d0p2 offline on devdb.tonservices.com?] gatorade.t /dev/sda6 lev 0 STRANGE Ok, the whole /dev/ida/c0d0p2 thing is a word device i will admit, but it's definitely not offline... Does this setup pass amcheck? Could you have a look in devdb.tons' /tmp/amanda/sendbackup.* file whether there's something suspicious going on? It's most probably either a typo or a permissions problem. Are you using GNUTAR or DUMP? In case of GNUTAR, can you try giving the mountpoint instead of the device file, if my first suggestions don't help? FAILED AND STRANGE DUMP DETAILS: /-- gatorade.t /dev/sda6 lev 0 STRANGE sendbackup: start [gatorade.tonservices.com:/dev/sda6 level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end ? gtar: ./ton/spool/doc_send/fax/oldstuff/064106020107: Warning: Cannot st at: No such file or directory | gtar: ./tmp/.font-unix/fs-1: socket ignored ? gtar: ./ton/spool/doc_send/fax/oldstuff/064106020107/01.tif: Warning: Ca nnot stat: No such file or directory | gtar: ./var/lib/mysql/mysql.sock: socket ignored | Total bytes written: 11511255040 (11GB, 8.7MB/s) sendbackup: size 11241460 sendbackup: end ok, so i guess tar probably has problems w/ sockets? Sockets get routinely ignored by tar, nothing to worry about. The `Cannot stat' errors in the spool directory are certainly harmless, just a file that disappeared between the moment tar constructed its list of files to backup, and the moment it wanted to actually read them. (that isn't so big of a deal), what is a problem is that it shouldn't even be backing up anything in /tmp/ or oldstuff (here's my exclude file): ./tmp/* ./proc/* ./dev/* *oldstuff* ./mnt/* ./opt/naroot/* ./var/tmp/* ./var/www/* ./sys/* there's another thread on the whole amanda ignoring excludes going on right now, but it doesn't seem like any definite conclusion has been reached. is this a bug, or do i just have a badly formed exclude file? Actually, there is no known problem whatsoever with exclude lists. The other thread that you allude to, will most probably just debug the exclude file's syntax. Same thing for you, are you sure that your exclude file is correctly taken into account? Again, the files in /tmp/amanda/ on the client will tell you that. You will notably find the complete command line that amanda uses for tar, in one of these files. It doesn't hurt to try that line and see whether it fails; most probably the solution will pop out immediately if you try that. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: disk offline?
Cameron Matheson wrote: hmm, there is no sendbackup file... i'm assuming it never got that file. i did look around in a few of the other files, and the problem seems to be here at how it's running tar: /bin/tar --create --file /dev/null --directory /dev/ida/c0d0p2 --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/devdb.tonser vices.com_dev_ida_c0d0p2_0.new --sparse --ignore-failed-read --totals . --directory /dev/ida/c0d0p2!! i'm not sure why that is... here's the entry from my disklist file: devdb.tonservices.com /dev/ida/c0d0p2 root-tar it's similar to my other clients which are all working fine... why would it be sending this tar command? (the other clients are all having '/' be their directory) Actually, I thought that you could give either a device name or a directory, and amanda would convert either one to whatever is needed for your dump program (device for DUMP, path for GNUTAR). Apparently, this doesn't work out in your case; I remember there having been a bug some time ago, but I can't recall the specifics. (Anybody remember more detail here?) Anyway, if using the path instead of the device is fine with you, I'm pretty sure that would work. Are you using GNUTAR or DUMP? In case of GNUTAR, can you try giving the mountpoint instead of the device file, if my first suggestions don't help? hmmm, i never even thought about that... does that mean that instead of specifying the device, i can just type '/' and it will back up everything (except for the stuff in excludes)? Almost, yes. Note the `--one-file-system' option to tar above: tar will stay within the same mounted filesystem, heeding excludes obviously. Barring an eventual bug in amanda, use whatever notation you are more comfortable with; to me, that would be directories, for other, that might be devices. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: disk offline?
--On June 2, 2005 12:05:58 PM -0700 Cameron Matheson [EMAIL PROTECTED] wrote: devdb.tonservices.com /dev/ida/c0d0p2 root-tar it's similar to my other clients which are all working fine... why would it be sending this tar command? (the other clients are all having '/' be their directory) Whenusing tar reference MOUNTED filesystems not raw disk devices. / is a mounted file system, the above is pretty clearly not, it should be like /var, /home, /usr, or somesuch. You can't dump an unmounted filesystem or raw device with tar.
Re: disk offline?
On Thu, Jun 02, 2005 at 09:23:34PM +0200, Alexander Jolk wrote: Cameron Matheson wrote: it's similar to my other clients which are all working fine... why would it be sending this tar command? (the other clients are all having '/' be their directory) Actually, I thought that you could give either a device name or a directory, and amanda would convert either one to whatever is needed for your dump program (device for DUMP, path for GNUTAR). Apparently, this doesn't work out in your case; I remember there having been a bug some time ago, but I can't recall the specifics. (Anybody remember more detail here?) Not the details of the bug. What I was wondering was about /etc/fstab. The translation between device and mounted file system is done, I think, by using the fstab file. Recent practice in linux (at least recent to me) is to use some symbolic tokens in fstab. I see one of my laptop fedora entries is: LABEL=//ext3 defaults1 1 From that, I've no idea what disk device contains /. Probably amanda doesn't either. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: disk offline?
Hey, you're exactly right... that box (i'm not even sure what distro it's running... mandrake?) is also using that weird naming scheme (i actually had to check mtab to see what the root really was). that seems kind of lame to do it by label instead of device file, but i guess that's the way it goes. thanks for the info, Cameron Matheson --- Jon LaBadie [EMAIL PROTECTED] wrote: Not the details of the bug. What I was wondering was about /etc/fstab. The translation between device and mounted file system is done, I think, by using the fstab file. Recent practice in linux (at least recent to me) is to use some symbolic tokens in fstab. I see one of my laptop fedora entries is: LABEL=//ext3 defaults1 1 From that, I've no idea what disk device contains /. Probably amanda doesn't either. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: failure and strange dump summary -- disk offline
Does anyone have any more suggestions I can look into for resolving my sda3 disk? amcheck does not report any problems. my amanda user is part of the disk group /dev/sda1 performs without missing a beat, /dev/sda3 continuously reports /dev/sda3 lev 0 FAILED [disk /dev/sda3 offline on mn-py-linuxsvr?] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - mn-py-linuxs /dev/sda3 0 FAILED --- -Original Message- From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED] Sent: Thursday, October 28, 2004 6:46 PM To: Brian Tima Subject: Re: failure and strange dump summary Hi, Brian, on Freitag, 29. Oktober 2004 at 01:33 you wrote to amanda-users: BT I've been messing with AMANDA now for a couple months, I keep putting BT off trying to resolve my issues. But once again, here I am. BT Attempting BT to inquire if anyone has some direction for me on what I must do to BT correct my disk being offline? What does amcheck report? Is /dev/sda3 readable for the AMANDA-user? What does ll /dev/sda[13] tell you? -- best regards, Stefan G. Weichinger
Re: failure and strange dump summary -- disk offline
Hi, Brian Tima, on Freitag, 29. Oktober 2004 at 17:20 you wrote to amanda-users: BT Does anyone have any more suggestions I can look into for resolving my sda3 BT disk? BT amcheck does not report any problems. BT my amanda user is part of the disk group BT /dev/sda1 BT performs without missing a beat, /dev/sda3 BT continuously reports /dev/sda3 lev 0 FAILED [disk /dev/sda3 offline on BT mn-py-linuxsvr?] Look up the logfiles (/tmp/amanda, /var/adm/amanda) Did you configure and make AMANDA as AMANDA-user? Installed it as root? What does amadmin yourconf version say? -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: failure and strange dump summary -- disk offline
Brian Tima wrote: Does anyone have any more suggestions I can look into for resolving my sda3 disk? What filesystem is sda? ext2 reiserfs? ... What is in the debug file on the client: /tmp/amanda/*.debug concerning this DLE ? (I thought someone already asked, but I never saw the answer.) -- 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 * ***
RE: failure and strange dump summary -- disk offline
I don't understand what you are asking by All the ones relevant to /dev/sda3 ? I've tried with DUMP and GNUTAR, currently configured to run gnutar. are any switches needed in the grep /dev/sda3 command ? I have cleared /tmp/amanda and running it now -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens Sent: Friday, October 29, 2004 10:56 AM To: Brian Tima Cc: Amanda Mailing List Subject: Re: failure and strange dump summary -- disk offline Brian Tima wrote: File system is ext3 Which debug file do I check? Here are the files showing in the directory /tmp/amanda All the ones relevant to /dev/sda3 ? You never posted (afaik) which program you used to dump the filesystem (dump or gnutar). Do a grep of /dev/sda3 or the mountpoint for gnutar in the files. Another easy one: the middle numbers are datatime stamps. If that is still too much work, remove all those files in /tmp/amanda, then run it once, and look through all files that just got created. Remember ON THE CLIENT, not on the amanda server. -- 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 * ***
RE: failure and strange dump summary -- disk offline
--On Friday, October 29, 2004 12:06:07 -0500 Brian Tima [EMAIL PROTECTED] wrote: I don't understand what you are asking by All the ones relevant to /dev/sda3 ? I've tried with DUMP and GNUTAR, currently configured to run gnutar. Tar deals with filesystems, not devices, so you need to either use dump on /dev/sda3 or use tar on the path where it it is mounted. Even with tar on a device you should still get a tar image, it just won't be what your expecting, so you still have a problem. . are any switches needed in the grep /dev/sda3 command ? I have cleared /tmp/amanda and running it now Let us know what's in /tmp/amanda on the client when it's done. Frank -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Bijnens Sent: Friday, October 29, 2004 10:56 AM To: Brian Tima Cc: Amanda Mailing List Subject: Re: failure and strange dump summary -- disk offline Brian Tima wrote: File system is ext3 Which debug file do I check? Here are the files showing in the directory /tmp/amanda All the ones relevant to /dev/sda3 ? You never posted (afaik) which program you used to dump the filesystem (dump or gnutar). Do a grep of /dev/sda3 or the mountpoint for gnutar in the files. Another easy one: the middle numbers are datatime stamps. If that is still too much work, remove all those files in /tmp/amanda, then run it once, and look through all files that just got created. Remember ON THE CLIENT, not on the amanda server. -- 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 * *** -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: disk offline error
On Mon, May 31, 2004 at 09:14:16PM -0700, gen2 wrote: /dev/sda9 is NOT a mount point, its a descriptor only and will probably fail forever. now, if that disk is mounted someplace, as in /mnt/sda9 on the machine whose alias is node1, and it is mounted when amdump runs, it should work like a champ. Ok, what I'm experiencing lends that a lot of credence, but what sent me off in this direction was (from the amanda distribution, example disklist entries) # Dump Joe's NetBSD machine, with the mounted MS-DOS partition dumped # using tar. #joespc wd0a comp-root #joespc wd0e comp-user #joespc /msdos comp-user-tar which seems to imply that it's possible to back up unmounted partitions, and that would be really great! I've always been under the impression that this was amanda-possible somehow, but never have been able to make it happen. Seems like this would be the way to back up a partition regardless of formatting (like an HFS+ or NT part, which is really what I'm after). If the program you tell amanda to use for the backup is a version of tar, then it can only backup files and directories. That is a property of tar, not amanda. And of course, for there to be files and directories, the partition must be mounted. If instead you tell amanda to use a version of dump, those programs generally work at the device level (even when told to work on a mount point) and should be able to backup umounted partitions. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: *OS X* disk offline error
That makes perfect sense, thanks. Basically, whatever version of dump lives on the target host is what defines capabilities in this regard. So still, I'd be limited to, say, ext2/3 filesystems if I tried to use linux dump. Unfortunately this works against solving my problem! I'm trying to use amanda to back up mostly linux and bsd, which works great...but also have some winXP boxes (which I know I can backup using amanda/samba) and some OS X units. New question, same error: I've got xtar running on osx boxes, and it works well with amanda AFAICT. The only problem is that I get the disk ... offline error when trying to backup any files on mounted volumes (non-root drives). osx1 /Users standard Works fine osx1 /Volumes/hfs-mounted-part standard Gives the disk offline error (the hfs-mounted-part is a mounted/functioning hfs or hfs+ partition from an attached drive). The mounted external volume contains a mac OS9 partition, so I'm hoping to sweep all the backups using just amanda (lofty goal, that!! But so nice if it would work...) Thanks! On Tuesday 01 June 2004 07:26 am, Jon LaBadie wrote: Seems like this would be the way to back up a partition regardless of formatting (like an HFS+ or NT part, which is really what I'm after). If the program you tell amanda to use for the backup is a version of tar, then it can only backup files and directories. That is a property of tar, not amanda. And of course, for there to be files and directories, the partition must be mounted. If instead you tell amanda to use a version of dump, those programs generally work at the device level (even when told to work on a mount point) and should be able to backup umounted partitions.
Re: disk offline error
On Tue, Jun 01, 2004 at 10:26:57AM -0400, Jon LaBadie wrote: If [...] you tell amanda to use a version of dump, those programs generally work at the device level (even when told to work on a mount point) and should be able to backup umounted partitions. To add a bit more detail, dump does this by understanding the file-system data structures, just about as intimately as the kernel file-system code does. Every file-system type needs its own specific pair of dump and restore programs if you want to back up unmounted partitions. Which is why using dump instead of gtar does *not* get you this: On Mon, May 31, 2004 at 09:14:16PM -0700, gen2 wrote: Seems like this would be the way to back up a partition regardless of formatting (like an HFS+ or NT part, which is really what I'm after). -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
disk offline error
Hi all, I have a very functional amanda 2.4.3 LAN backup system that I'm having one problem with: I can't seem to back up any partitions, only directories and files. If I use disklist specs like this node1 /home standard I get a proper backup, but if I use node1 /dev/sda9 standard I get an error saying that sda9 is offline. But it isn't, so I figured there must be a permissions problem, but amanda is in the disk group, and that device node is in the disk group as well, with proper rw perms. I also tried node1 /dev/scsi/host1/bus0/target1/lun0/part9 standard also to no good end. Any ideas/clues? How can I verify the permissions are working on the node1 side beyond checking with ls -la? Thanks!
Re: disk offline error
/dev/sda9 is NOT a mount point, its a descriptor only and will probably fail forever. now, if that disk is mounted someplace, as in /mnt/sda9 on the machine whose alias is node1, and it is mounted when amdump runs, it should work like a champ. Ok, what I'm experiencing lends that a lot of credence, but what sent me off in this direction was (from the amanda distribution, example disklist entries) # Dump Joe's NetBSD machine, with the mounted MS-DOS partition dumped # using tar. #joespc wd0a comp-root #joespc wd0e comp-user #joespc /msdos comp-user-tar which seems to imply that it's possible to back up unmounted partitions, and that would be really great! I've always been under the impression that this was amanda-possible somehow, but never have been able to make it happen. Seems like this would be the way to back up a partition regardless of formatting (like an HFS+ or NT part, which is really what I'm after).
disk offline ?
Hi Group ! Maybe anyone has a hint for me ? We have about 30 Servers, all UNIX. They are all backed up with amanda, which worked very good, until some problems occured. I defined a TestSet an tried to put in a new host. But I don´t get it to work. I want to do a dump of the following partitions, which are really partitions on the target-host. -snip disklist daisy / comp-hd-dump daisy /boot comp-hd-dump daisy /optcomp-hd-dump daisy /usrcomp-hd-dump -/snip If I put comp-hd-tar in here, all works fine ... !? -snip report FAILURE AND STRANGE DUMP SUMMARY: daisy /usr lev 0 FAILED [disk /usr offline on daisy?] daisy /opt lev 0 FAILED [disk /opt offline on daisy?] daisy /lev 0 FAILED [disk / offline on daisy?] ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - daisy / 0 FAILED --- daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 daisy /opt0 FAILED --- daisy /usr0 FAILED --- /snip Why does /boot work ??? Ups, just saw it worked only the first time ... Now its the same message ... And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? Last Backup this night Were great anyone had a tip ! ...olli
Re: disk offline ?
--On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon [EMAIL PROTECTED] wrote: Hi Group ! Maybe anyone has a hint for me ? We have about 30 Servers, all UNIX. They are all backed up with amanda, which worked very good, until some problems occured. I defined a TestSet an tried to put in a new host. But I don´t get it to work. I want to do a dump of the following partitions, which are really partitions on the target-host. -snip disklist daisy / comp-hd-dump daisy /boot comp-hd-dump daisy /optcomp-hd-dump daisy /usrcomp-hd-dump -/snip If I put comp-hd-tar in here, all works fine ... !? -snip report FAILURE AND STRANGE DUMP SUMMARY: daisy /usr lev 0 FAILED [disk /usr offline on daisy?] daisy /opt lev 0 FAILED [disk /opt offline on daisy?] daisy /lev 0 FAILED [disk / offline on daisy?] Disk offline messages are generally a result of permissions problems (if the disk were really offline you would have much bigger problems). Make sure your backup user is part of the correct group to have access to the disk. Try to 'su - backupuser' and check if you can see those disks. Tar works because Aamnda uses a suid runtar wrapper script that runs tar as root (although it isn't used by amcheck, so you would still get errors from amcheck even though amdump would work). Frank ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - daisy / 0 FAILED --- daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 daisy /opt0 FAILED --- daisy /usr0 FAILED --- /snip Why does /boot work ??? Ups, just saw it worked only the first time ... Now its the same message ... And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? Last Backup this night Were great anyone had a tip ! ...olli -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: disk offline ?
I can su to amanda and chdir to usr and everything else thats failling ? Is it maybe because of the filesystem xfs on the target-machine ? I think amanda wants to do a xfsdump there, right ? I tried to run it as amanda and got it complaining to be root to run ... !? Thanks in advance ...olli Am Do, 2004-01-08 um 16.39 schrieb Frank Smith: --On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon [EMAIL PROTECTED] wrote: Hi Group ! Maybe anyone has a hint for me ? We have about 30 Servers, all UNIX. They are all backed up with amanda, which worked very good, until some problems occured. I defined a TestSet an tried to put in a new host. But I don´t get it to work. I want to do a dump of the following partitions, which are really partitions on the target-host. -snip disklist daisy / comp-hd-dump daisy /boot comp-hd-dump daisy /optcomp-hd-dump daisy /usrcomp-hd-dump -/snip If I put comp-hd-tar in here, all works fine ... !? -snip report FAILURE AND STRANGE DUMP SUMMARY: daisy /usr lev 0 FAILED [disk /usr offline on daisy?] daisy /opt lev 0 FAILED [disk /opt offline on daisy?] daisy /lev 0 FAILED [disk / offline on daisy?] Disk offline messages are generally a result of permissions problems (if the disk were really offline you would have much bigger problems). Make sure your backup user is part of the correct group to have access to the disk. Try to 'su - backupuser' and check if you can see those disks. Tar works because Aamnda uses a suid runtar wrapper script that runs tar as root (although it isn't used by amcheck, so you would still get errors from amcheck even though amdump would work). Frank ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - daisy / 0 FAILED --- daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 daisy /opt0 FAILED --- daisy /usr0 FAILED --- /snip Why does /boot work ??? Ups, just saw it worked only the first time ... Now its the same message ... And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? Last Backup this night Were great anyone had a tip ! ...olli
Re: disk offline ?
--On Thursday, January 08, 2004 17:21:48 +0100 Oliver Simon [EMAIL PROTECTED] wrote: I can su to amanda and chdir to usr and everything else thats failling ? Is it maybe because of the filesystem xfs on the target-machine ? I think amanda wants to do a xfsdump there, right ? I tried to run it as amanda and got it complaining to be root to run ... !? You must use the right version of dump for the filesystem. Was Amanda built with support for xfsdump ? Are the disks on all your clients xfs or just on the one new client? If you have a mixture of filesystem types, I'm not sure how you configure multiple flavors of dump in one setup, hopefully someone else here has done it and will say how. Frank Thanks in advance ...olli Am Do, 2004-01-08 um 16.39 schrieb Frank Smith: --On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon [EMAIL PROTECTED] wrote: Hi Group ! Maybe anyone has a hint for me ? We have about 30 Servers, all UNIX. They are all backed up with amanda, which worked very good, until some problems occured. I defined a TestSet an tried to put in a new host. But I don´t get it to work. I want to do a dump of the following partitions, which are really partitions on the target-host. -snip disklist daisy / comp-hd-dump daisy /boot comp-hd-dump daisy /optcomp-hd-dump daisy /usrcomp-hd-dump -/snip If I put comp-hd-tar in here, all works fine ... !? -snip report FAILURE AND STRANGE DUMP SUMMARY: daisy /usr lev 0 FAILED [disk /usr offline on daisy?] daisy /opt lev 0 FAILED [disk /opt offline on daisy?] daisy /lev 0 FAILED [disk / offline on daisy?] Disk offline messages are generally a result of permissions problems (if the disk were really offline you would have much bigger problems). Make sure your backup user is part of the correct group to have access to the disk. Try to 'su - backupuser' and check if you can see those disks. Tar works because Aamnda uses a suid runtar wrapper script that runs tar as root (although it isn't used by amcheck, so you would still get errors from amcheck even though amdump would work). Frank ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - daisy / 0 FAILED --- daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 daisy /opt0 FAILED --- daisy /usr0 FAILED --- /snip Why does /boot work ??? Ups, just saw it worked only the first time ... Now its the same message ... And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? Last Backup this night Were great anyone had a tip ! ...olli -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: disk offline ?
Hello again ... Am Do, 2004-01-08 um 17.37 schrieb Frank Smith: --On Thursday, January 08, 2004 17:21:48 +0100 Oliver Simon [EMAIL PROTECTED] wrote: I can su to amanda and chdir to usr and everything else thats failling ? Is it maybe because of the filesystem xfs on the target-machine ? I think amanda wants to do a xfsdump there, right ? I tried to run it as amanda and got it complaining to be root to run ... !? You must use the right version of dump for the filesystem. Was Amanda built with support for xfsdump ? Yes, we have about 15 (SuSI´s/SLES/SLOX) hosts running with xfs. No problem there. Are the disks on all your clients xfs or just on the one new client? The rest is 10 Solaris (ufs) and some other linux´ (redhat ext3). If you have a mixture of filesystem types, I'm not sure how you configure multiple flavors of dump in one setup, hopefully someone else here has done it and will say how. Thought, amanda examines it itself, and takes the correct version (dump/xfsdump) from the clients ?? Frank ...olli Thanks in advance ...olli Am Do, 2004-01-08 um 16.39 schrieb Frank Smith: --On Thursday, January 08, 2004 15:51:21 +0100 Oliver Simon [EMAIL PROTECTED] wrote: Hi Group ! Maybe anyone has a hint for me ? We have about 30 Servers, all UNIX. They are all backed up with amanda, which worked very good, until some problems occured. I defined a TestSet an tried to put in a new host. But I don´t get it to work. I want to do a dump of the following partitions, which are really partitions on the target-host. -snip disklist daisy / comp-hd-dump daisy /boot comp-hd-dump daisy /optcomp-hd-dump daisy /usrcomp-hd-dump -/snip If I put comp-hd-tar in here, all works fine ... !? -snip report FAILURE AND STRANGE DUMP SUMMARY: daisy /usr lev 0 FAILED [disk /usr offline on daisy?] daisy /opt lev 0 FAILED [disk /opt offline on daisy?] daisy /lev 0 FAILED [disk / offline on daisy?] Disk offline messages are generally a result of permissions problems (if the disk were really offline you would have much bigger problems). Make sure your backup user is part of the correct group to have access to the disk. Try to 'su - backupuser' and check if you can see those disks. Tar works because Aamnda uses a suid runtar wrapper script that runs tar as root (although it isn't used by amcheck, so you would still get errors from amcheck even though amdump would work). Frank ... DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - daisy / 0 FAILED --- daisy /boot 06410 5472 85.4 0:023511.7 0:023484.9 daisy /opt0 FAILED --- daisy /usr0 FAILED --- /snip Why does /boot work ??? Ups, just saw it worked only the first time ... Now its the same message ... And, does comp-hd-tar eat more cpu ? I would think so, or am I false ? Last Backup this night Were great anyone had a tip ! ...olli
disk offline on remote server
Dear All. I have some strange report on Amanda starting after no change on Amanda or at least I dont know what is Changed. I receive disk offline ?. only for remote servers. ServerName /etc/ lev 0 FAILED [disk /etc/ offline on ServerName?] I think every thing was fine for remote server and we hadnt any change Or possibly this occurs after recent compile. Amcheck doesnt report anything strange every thing is normal And amcheck shows every thing is fine. However I tried all Amanda ports all are available and listening for incoming port! Any help really appreciated. Best regards Mohammad
Re: disk offline on remote server
--On Friday, November 07, 2003 00:01:08 + Mohammad Meskarian [EMAIL PROTECTED] wrote: Dear All. I have some strange report on Amanda starting after no change on Amanda or at least I don't know what is Changed. I receive disk offline ?. only for remote servers. ServerName /etc/ lev 0 FAILED [disk /etc/ offline on ServerName?] I think every thing was fine for remote server and we hadn't any change Or possibly this occurs after recent compile. Amcheck doesn't report anything strange every thing is normal And amcheck shows every thing is fine. However I tried all Amanda ports all are available and listening for incoming port! I would suspect you lost the setuid bits on the various Amanda programs that need them (rundump, runtar, dumper, etc.). Frank Any help really appreciated. Best regards Mohammad -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
New prob: Disk Offline? error
OK, I am running my first dump. amcheck returns 0 errors now, but heres a new problem I need help with. Can anybody tell me why I am getting these errors? The only clue I have is that /boot was not mounted. Thanks Again!! snip planner: time 5.802: got result for host client01 disk /samba: 0 - -1K, -1 - -1K, -1 - -1K planner: time 5.803: got result for host client01 disk /home: 0 - -1K, -1 - -1K, -1 - -1K planner: time 5.803: got result for host client01 disk /var: 0 - -1K, -1 - -1K, -1 - -1K planner: time 5.803: got result for host client01 disk /: 0 - -1K, -1 - -1K, -1 - -1K planner: time 5.803: got result for host client01 disk /boot: 0 - 3538K, -1 - -1K, -1 - -1K planner: time 5.803: getting estimates took 5.796 secs FAILED QUEUE: 0: client01 /samba 1: client01 /home 2: client01 /var 3: client01 / DONE QUEUE: 0: client01 /boot ANALYZING ESTIMATES... pondering client01:/boot... next_level0 -12297 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 3538 total size 3715 total_lev0 3538 balanced-lev0size 176 planner: FAILED client01 /samba 20030901 0 [disk /samba offline on rid96pdc?] planner: FAILED client01 /home 20030901 0 [disk /home offline on rid96pdc?] planner: FAILED client01 /var 20030901 0 [disk /var offline on rid96pdc?] planner: FAILED client01 / 20030901 0 [disk / offline on rid96pdc?] --- Scott Phelps
disk offline?
I have not been able to backup anything on my local system. AMANDA reports that it thinks the disk is offline. Where should I start looking to find out what is wrong?
Re: disk offline?
On Tuesday 12 August 2003 11:53, LaValley, Brian E wrote: I have not been able to backup anything on my local system. AMANDA reports that it thinks the disk is offline. Where should I start looking to find out what is wrong? Start in the disklist and get rid of any localhost entries, use only FQDN's there. Make sure your /etc/hosts file is complete, including a direct translation of the servers FQDN to the servers IP address. And make sure the .amandahosts file is correct, including perms, which for security should be 0600. Amanda will read it with more permissive perms ok, but you don't exactly want half the planet reading that. Then make sure the amanda related files in /etc/xinetd.d are correct. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: disk offline?
--On Tuesday, August 12, 2003 11:53:59 -0400 LaValley, Brian E [EMAIL PROTECTED] wrote: I have not been able to backup anything on my local system. AMANDA reports that it thinks the disk is offline. Where should I start looking to find out what is wrong? Make sure you're not trying to back up the raw device with tar. su - to your backup user and see if you can acces the device. Some (RedHat?) machines had problems mapping paths to device names if the fstab used labels for partitions. If none of those help, try posting your OS, Amanda version, disklist and dumptype entry for the problem disk. Frank
AMANDA Disk Offline Error
I am using Red Hat Linux on Power PC. I wanted to BACKUP my SYSTEM IMAGE with AMANDA (version 2.4.2p2) and got following error message wonder why! FAIL planner my_host_name hdk1 0 [disk hdk1 offline on my_local_host?] Any hints/tips or related information is appreciated! Thanks! _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
disk offline error
I am using Red Hat Linux on Power PC. I wanted to BACKUP my SYSTEM IMAGE with AMANDA (version 2.4.2p2) and got following error message wonder why! FAIL planner my_host_name hdk1 0 [disk hdk1 offline on my_local_host?] Any hints/tips or related information is appreciated! Thanks! _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
Re: strange disk offline error
On Wed, Jul 23, 2003 at 10:57:31AM -0400, Kurt Yoder wrote: Looking more closely in /tmp/amanda/sendsize...debug, I see something strange: [...] sendsize[7578]: time 0.137: Usage: dump [-?CDVcgl -L[v] -a[v] -f[v] -h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s) On Solaris 7: % dump Usage: dump [-agcd:fhln:oprstvCDLT:V?] file(s) ... % which dump /usr/ccs/bin/dump % ufsdump Usage: ufsdump [0123456789fustdWwnDCcbavloS [argument]] filesystem dump is for displaying ELF files in human-readable format. The backup program we all know and love is called ufsdump. SCO might be similar. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: strange disk offline error
On Fri, Jul 25, 2003 at 02:37:43PM -0400, Kurt Yoder wrote: sendsize[505]: time 0.054: error [cannot find user backup in passwd file] This message is a bit misleading. It really means: `getpwnam(backup) was unsuccessful'. Perhaps getpwnam() searched /etc/passwd, but perhaps it tried to use NIS or some SCOish mechanism. So there might be other things to look at beyond /etc/passwd and its symlink target. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: strange disk offline error
So it looks like this has something to do with me compiling this on SCO. I've asked my local knowledgeable SCO guy and he gave me an explanation that I don't understand but perhaps one of the coders would. Should I direct this thread to amanda-hackers instead? Kurt Yoder said: More information about this problem: Looking more closely in /tmp/amanda/sendsize...debug, I see something strange: sendsize[7578]: time 0.020: calculating for amname '/', dirname '/', spindle -1 sendsize[7578]: time 0.020: getting size via dump for / level 0 sendsize[7578]: time 0.020: calculating for device '/' with '' sendsize[7578]: time 0.022: running /bin/dump 0Esf 1048576 - / sendsize[7578]: time 0.023: running /usr/local/libexec/killpgrp sendsize[7578]: time 0.137: Usage: dump [-?CDVcgl -L[v] -a[v] -f[v] -h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s) ... sendsize[7578]: time 0.138: . sendsize[7578]: estimate time for / level 0: 0.116 sendsize[7578]: no size line match in /bin/dump output for / sendsize[7578]: . sendsize[7578]: estimate size for / level 0: -1 KB sendsize[7578]: time 0.138: asking killpgrp to terminate sendsize[7578]: time 1.149: done with amname '/', dirname '/', spindle -1 Notice line 6 Usage: message. Perhaps dump is not acting the way amanda expects? Is this my problem? I had trouble getting gnu tar to compile, but maybe I should try again so I can use it instead of dump. -- Kurt Yoder Sport Health network administrator
Re: strange disk offline error
So I'm still getting the disk offline error, and seeing this in my /tmp/amanda/sendsize...debug: sendsize: debug 1 pid 502 ruid 19 euid 19: start at Fri Jul 25 14:24:16 2003 sendsize: version 2.4.4 sendsize[502]: time 0.026: waiting for any estimate child sendsize[505]: time 0.026: calculating for amname '/', dirname '/', spindle -1 sendsize[505]: time 0.026: getting size via gnutar for / level 0 sendsize[505]: time 0.042: spawning /usr/local/libexec/runtar in pipeline sendsize[505]: argument list: /usr/local/bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/db.shcorp.com__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._.20030725142416.exclude . sendsize[505]: time 0.054: error [cannot find user backup in passwd file] sendsize[505]: time 0.056: sendsize[505]: time 0.057: . sendsize[505]: estimate time for / level 0: 0.015 sendsize[505]: no size line match in /usr/local/bin/tar output for / sendsize[505]: . sendsize[505]: estimate size for / level 0: -1 KB sendsize[505]: time 0.057: waiting for /usr/local/bin/tar / child sendsize[505]: time 0.160: after /usr/local/bin/tar / wait sendsize[505]: time 0.160: done with amname '/', dirname '/', spindle -1 sendsize[502]: time 0.160: child 505 terminated normally sendsize: time 0.160: pid 502 finish time Fri Jul 25 14:24:16 2003 I'm pretty certain my problem has to do with the cannot find user backup in passwd file. But this makes no sense. I can su - backup and then view /etc/passwd. The user backup is definitely in it. Any ideas for what's causing this? -- Kurt Yoder Sport Health network administrator
Re: strange disk offline error
Joshua Baker-LePain said: snipped Yup, that's definitely the problem. Is amanda picking the right dump for your filesystem? You can tell by the output of ./configure (it might also be in the amandad*debug files -- I'm not sure). tar is nice for being so cross platform. If you can get that to go, it might be your better option. OK, I got gnu tar 1.13 compiled and working. However, I still get the disk offline error. Now in /tmp/amanda/sendsize... I see this which doesn't look good either: sendsize: debug 1 pid 15490 ruid 19 euid 19: start at Thu Jul 24 00:30:05 2003 sendsize: version 2.4.4 sendsize[15490]: time 0.009: waiting for any estimate child sendsize[15492]: time 0.009: calculating for amname '/', dirname '/', spindle -1sendsize[15492]: time 0.015: getting size via gnutar for / level 0 sendsize[15492]: time 0.016: spawning /usr/local/libexec/runtar in pipeline sendsize[15492]: argument list: /usr/local/bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/db.shcorp.com__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._.20030724003005.exclude . sendsize[15492]: time 0.028: error [cannot find user backup in passwd file] sendsize[15492]: time 0.059: sendsize[15492]: time 0.060: . sendsize[15492]: estimate time for / level 0: 0.044 sendsize[15492]: no size line match in /usr/local/bin/tar output for / sendsize[15492]: . sendsize[15492]: estimate size for / level 0: -1 KB sendsize[15492]: time 0.061: waiting for /usr/local/bin/tar / child sendsize[15492]: time 0.061: after /usr/local/bin/tar / wait sendsize[15492]: time 0.061: done with amname '/', dirname '/', spindle -1 sendsize[15490]: time 0.061: child 15492 terminated normally Again I see cannot find user backup in passwd file. In looking at /etc, I noticed the passwd file is actually a symlink to a passwd file in another directory (For anyone who has SCO, why in GOD'S NAME do they do this symlink BS for everything? It is horrible!). Is this the only problem that's stopping me here, or is there anything else that needs fixing? -- Kurt Yoder Sport Health network administrator
Re: strange disk offline error
On Thu, 24 Jul 2003 at 10:26am, Kurt Yoder wrote tar is nice for being so cross platform. If you can get that to go, it might be your better option. OK, I got gnu tar 1.13 compiled and working. However, I still get the disk offline error. Now in /tmp/amanda/sendsize... I see this which doesn't look good either: tar 1.13 is Bad. Grab 1.13.25 from alpha.gnu.org. sendsize[15492]: time 0.028: error [cannot find user backup in passwd file] sendsize[15492]: time 0.059: sendsize[15492]: time 0.060: . sendsize[15492]: estimate time for / level 0: 0.044 sendsize[15492]: no size line match in /usr/local/bin/tar output for / Again I see cannot find user backup in passwd file. In looking at /etc, I noticed the passwd file is actually a symlink to a passwd file in another directory (For anyone who has SCO, why in GOD'S NAME do they do this symlink BS for everything? It is horrible!). Is this the only problem that's stopping me here, or is there anything else that needs fixing? I'm guessing that if you fix access to /etc/passwd, you'll be a lot closer to making this work. What are the owner and permissions on what /etc/passwd points to (and yes, that is brain dead)? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: strange disk offline error
On Thu, Jul 24, 2003 at 10:26:30AM -0400, Kurt Yoder wrote: Again I see cannot find user backup in passwd file. In looking at /etc, I noticed the passwd file is actually a symlink to a passwd file in another directory (For anyone who has SCO, why in GOD'S NAME do they do this symlink BS for everything? It is horrible!). Is this the only problem that's stopping me here, or is there anything else that needs fixing? Not sure about your passwd problem, but this earlier line needs work. OK, I got gnu tar 1.13 compiled and working. However, I still get 1.13 is a known BAD version of gnutar for amanda. Get 1.13.19 or 1.13.25. Sorry I forget the url, but it is something like ftp://alpha.gnu.org. Check the archives, it is mentioned regularly. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: strange disk offline error
On Thursday 24 July 2003 10:26, Kurt Yoder wrote: Joshua Baker-LePain said: snipped Yup, that's definitely the problem. Is amanda picking the right dump for your filesystem? You can tell by the output of ./configure (it might also be in the amandad*debug files -- I'm not sure). tar is nice for being so cross platform. If you can get that to go, it might be your better option. OK, I got gnu tar 1.13 compiled and working. I certainly hope that version above is a typo. 1.13 is broken, you need 1.13-25, getting it from alpha.gnu.org. However, I still get the disk offline error. Now in /tmp/amanda/sendsize... I see this which doesn't look good either: sendsize: debug 1 pid 15490 ruid 19 euid 19: start at Thu Jul 24 00:30:05 2003 sendsize: version 2.4.4 sendsize[15490]: time 0.009: waiting for any estimate child sendsize[15492]: time 0.009: calculating for amname '/', dirname '/', spindle -1sendsize[15492]: time 0.015: getting size via gnutar for / level 0 sendsize[15492]: time 0.016: spawning /usr/local/libexec/runtar in pipeline sendsize[15492]: argument list: /usr/local/bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/db.shcorp.com__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._.20030724003005.exclude . sendsize[15492]: time 0.028: error [cannot find user backup in passwd file] sendsize[15492]: time 0.059: sendsize[15492]: time 0.060: . sendsize[15492]: estimate time for / level 0: 0.044 sendsize[15492]: no size line match in /usr/local/bin/tar output for / sendsize[15492]: . sendsize[15492]: estimate size for / level 0: -1 KB sendsize[15492]: time 0.061: waiting for /usr/local/bin/tar / child sendsize[15492]: time 0.061: after /usr/local/bin/tar / wait sendsize[15492]: time 0.061: done with amname '/', dirname '/', spindle -1 sendsize[15490]: time 0.061: child 15492 terminated normally Again I see cannot find user backup in passwd file. In looking at /etc, I noticed the passwd file is actually a symlink to a passwd file in another directory (For anyone who has SCO, why in GOD'S NAME do they do this symlink BS for everything? It is horrible!). Is this the only problem that's stopping me here, or is there anything else that needs fixing? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: strange disk offline error
More information about this problem: Looking more closely in /tmp/amanda/sendsize...debug, I see something strange: sendsize[7578]: time 0.020: calculating for amname '/', dirname '/', spindle -1 sendsize[7578]: time 0.020: getting size via dump for / level 0 sendsize[7578]: time 0.020: calculating for device '/' with '' sendsize[7578]: time 0.022: running /bin/dump 0Esf 1048576 - / sendsize[7578]: time 0.023: running /usr/local/libexec/killpgrp sendsize[7578]: time 0.137: Usage: dump [-?CDVcgl -L[v] -a[v] -f[v] -h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s) ... sendsize[7578]: time 0.138: . sendsize[7578]: estimate time for / level 0: 0.116 sendsize[7578]: no size line match in /bin/dump output for / sendsize[7578]: . sendsize[7578]: estimate size for / level 0: -1 KB sendsize[7578]: time 0.138: asking killpgrp to terminate sendsize[7578]: time 1.149: done with amname '/', dirname '/', spindle -1 Notice line 6 Usage: message. Perhaps dump is not acting the way amanda expects? Is this my problem? I had trouble getting gnu tar to compile, but maybe I should try again so I can use it instead of dump. -- Kurt Yoder Sport Health network administrator
Re: strange disk offline error
Kurt Yoder wrote: Weird errors here. The root user is definitely in the passwd file. Could this be part of the problem? Thanks for any ideas on fixing this... Maybe a silly question, but, can your amanda backup user read the passwd file on that system? Marc
Re: strange disk offline error
On Wed, 23 Jul 2003 at 10:57am, Kurt Yoder wrote sendsize[7578]: time 0.020: calculating for amname '/', dirname '/', spindle -1 sendsize[7578]: time 0.020: getting size via dump for / level 0 sendsize[7578]: time 0.020: calculating for device '/' with '' sendsize[7578]: time 0.022: running /bin/dump 0Esf 1048576 - / sendsize[7578]: time 0.023: running /usr/local/libexec/killpgrp sendsize[7578]: time 0.137: Usage: dump [-?CDVcgl -L[v] -a[v] -f[v] -h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s) .. *snip* Notice line 6 Usage: message. Perhaps dump is not acting the way amanda expects? Is this my problem? I had trouble getting gnu tar to compile, but maybe I should try again so I can use it instead of dump. Yup, that's definitely the problem. Is amanda picking the right dump for your filesystem? You can tell by the output of ./configure (it might also be in the amandad*debug files -- I'm not sure). tar is nice for being so cross platform. If you can get that to go, it might be your better option. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
strange disk offline error
(That previous message should have had this subject; sorry, mail client troubles) Hello list I just compiled amanda on a SCO Unix machine (uname -a shows SCO_SV shcorp 3.2 5.0.6 i386) and tried to follow instructions to install it, instructing amanda to back up both of its disks. Everything appears successful, and the machine passes amcheck tests. When I run amdump at night, my other linux, freebsd, and windows machines dump successfully. However on my SCO machine, I get the message: shcorp.shc /stand lev FAILED [disk /stand offline on shcorp.shcorp.com?] shcorp.shc / lev FAILED [disk / offline on shcorp.shcorp.com?] I've looked in google, and found the following suggestions: (from faq-o-matic, http://amanda.sourceforge.net/fom-serve/cache/10.html) is disk really offline? Answer appears to be no. After all, I'm using this machine throughout the day. So I'd assume it should be available for backup, since no-one touches the machine at night. filesystem error? Well, I suppose there *could* be. But the fact that it happens on both disks seems to indicate that this is not the problem. (I also installed the same compiled version on a separate sco machine, and it does the exact same thing). filesystem too large? Does not seem to be. /stand is only 15 megabytes, but still fails. conflicting user name? Doesn't seem to be it. I configured with user backup. This only shows up once in the passwd file, and this box does not have any external sources for authentication (no nis, ldap, etc) don't have dump installed? This isn't it. I compiled by hand, and the config.log shows that amanda found the dump program. I suppose it could conceivably be something that amanda doesn't like about SCO's dump program though. How can I check if this might be the problem? (from an archived post: http://groups.yahoo.com/group/amanda-users/message/40200) permissions on /etc/fstab ok? On SCO, the file seems to be /etc/mnttab. It is unix mode 644, so this shouldn't be a problem. So, I looked at the logs in /tmp/amanda. For the last failed dump, I see these logs: -rw--- 1 root backup 231 Jul 22 00:30 killpgrp.20030722043007.debug -rw--- 1 root backup 231 Jul 22 00:30 killpgrp.20030722043009.debug -rw--- 1 root sys 2108 Jul 22 00:30 sendsize.20030722003007.debug -rw--- 1 root sys 2275 Jul 22 00:30 amandad.20030722003005.debug (strange that these are owned by root instead of backup; is this a problem?) sendsize ends with sendsize[1383]: time 2.300: child 1388 terminated normally sendsize: time 2.300: pid 1383 finish time Tue Jul 22 00:30:10 2003 Looks ok to me amandad ends with amandad: time 4.281: got packet: Amanda 2.4 ACK HANDLE 00E-00A00608 SEQ 1058848217 amandad: time 4.281: pid 1382 finish time Tue Jul 22 00:30:10 2003 seems fine, or? first killpgrp killpgrp: debug 1 pid 1386 ruid 19 euid 0: start at Tue Jul 22 04:30:07 2003 /usr/local/libexec/killpgrp: version 2.4.4 killpgrp: error [cannot find user root in passwd file] killpgrp: pid 1386 finish time Tue Jul 22 04:30:07 2003 second killpgrp killpgrp: debug 1 pid 1389 ruid 19 euid 0: start at Tue Jul 22 04:30:09 2003 /usr/local/libexec/killpgrp: version 2.4.4 killpgrp: error [cannot find user root in passwd file] killpgrp: pid 1389 finish time Tue Jul 22 04:30:09 2003 Weird errors here. The root user is definitely in the passwd file. Could this be part of the problem? Thanks for any ideas on fixing this... -- Kurt Yoder Sport Health network administrator
Re: One (of six) partitions returning disk offline
On Wed, 20 Nov 2002 at 4:10pm, Jay Lessert wrote selfcheck: device sda6 selfcheck: could not access sda6 (sda6): No such file or directory I'm not a Linux guy, but this is the one where Linux does not have a conventional entry for / in /etc/fstab, right? Nope. / has an entry in fstab just like everybody else. So if you're using tar, amanda cannot do the reverse-lookup from device name to mount-point (directory path). Solution is to use directory names in disklist, not device names. Much easier to read, anyway. Actually, it's a bug in amanda-2.4.2p2, fixed by the advfs.patch and/or 2.4.3. Even with directory names in the disklist, you'll hit this. It's probably unfortunate that example/disklist uses device name syntax, n'est pas? This I'll agree with. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: One (of six) partitions returning disk offline
On Thu, Nov 21, 2002 at 09:46:36AM -0500, Joshua Baker-LePain wrote: Nope. / has an entry in fstab just like everybody else. Well, not *just* like *everybody* else: :-) Solaris: #devicedevice mount FS fsckmount mount #to mount to fsck point typepassat boot options /dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no logging /dev/dsk/c1t3d0s7 /dev/rdsk/c1t3d0s7 /local ufs 2 yes logging Linux: LABEL=/ / ext3defaults1 1 LABEL=/local/local ext3defaults1 2 But you're right, I was wrong, sorry for the misinformation. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: disk offline
On Tue, 29 Oct 2002 at 2:39pm, Chad Morland wrote backup. /backup lev 0 FAILED [disk /backup offline on backup.domain.com?] (I have also tried using the device [/dev/vinum/striped]) *snip* My backup partition is a 430G striped vinum partition on FreeBSD. I have followed everything that is in the FAQ on this subject but nothing seems to be solving it. Anyone have any ideas on how to solve this? What's in /tmp/amandad*debug and /tmp/sendsize*debug on backup? Can you access the device *as the amanda user*? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: disk offline
Error from sendsize*debug: runtar: error [must be invoked by operator] However, amanda is in my operator group. torbackup# id amanda uid=1000(amanda) gid=1000(amanda) groups=1000(amanda), 5(operator) And the from amandad*.debug: cut (Environment variables cut out) Amanda 2.4 REQ HANDLE 000-00360708 SEQ 1035907903 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; sending nack: Amanda 2.4 NAK HANDLE 000-00360708 SEQ 1035907903 ERROR unknown service: noop /cut -CM - Original Message - From: Joshua Baker-LePain [EMAIL PROTECTED] To: Chad Morland [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 29, 2002 3:08 PM Subject: Re: disk offline On Tue, 29 Oct 2002 at 2:39pm, Chad Morland wrote backup. /backup lev 0 FAILED [disk /backup offline on backup.domain.com?] (I have also tried using the device [/dev/vinum/striped]) *snip* My backup partition is a 430G striped vinum partition on FreeBSD. I have followed everything that is in the FAQ on this subject but nothing seems to be solving it. Anyone have any ideas on how to solve this? What's in /tmp/amandad*debug and /tmp/sendsize*debug on backup? Can you access the device *as the amanda user*? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: disk offline
On Tue, 29 Oct 2002 at 3:20pm, Chad Morland wrote Error from sendsize*debug: runtar: error [must be invoked by operator] However, amanda is in my operator group. torbackup# id amanda uid=1000(amanda) gid=1000(amanda) groups=1000(amanda), 5(operator) Are you using inetd or xinetd? If it's xinetd, you need groups = yes in your amanda service file to pick up secondary groups. When you configured and compiled amanda, what USER and GROUP did you define? You did 'make install' as root, right? And the from amandad*.debug: cut (Environment variables cut out) Amanda 2.4 REQ HANDLE 000-00360708 SEQ 1035907903 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; sending nack: Amanda 2.4 NAK HANDLE 000-00360708 SEQ 1035907903 ERROR unknown service: noop This is a result of running 2.4.3 on the server but not on this client (I think). It's not a problem in itself. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
DIsk offline error with LVM snapshot volumes
Hello, I have several logical volumes which I want to backup with AMANDA. To make a proper backup, I create snapshot volumes before I start the backup. Now, trying to backup these snapshot volumes, AMANDA reports 'disk offline'. If I try to backup the nomal volumes, everything works fine I use Suse 8.0, tar 1.13.25, AMANDA 2.4.2p2. Any experience with that issue ? Regards Patrick
Disk offline
I have just installed 2.4.2p2 on a few redhat 7.0 servers. All work great except 1. I get the following report after backup. FAILURE AND STRANGE DUMP SUMMARY: gator20.tr /home lev 0 FAILED [disk /var offline on gator20.triparish.net?] I get this on all directories on this server. The other servers backup fine. I have reinstalled both the backup server and all clients. I went over all the permissions and they are identical on all the client machines. Amcheck reports no errors and is happy. I upgraded tar to 1.13.25-1. I am at a total loss any help greatly appreciated. Thank you, Lewey Taylor Computer Sales Services, Inc. (985) 879-3219
Please help: disk offline? error for HP-UX 11.0...
Please help me out, folks -- tried a bunch of things, I really do not know how to proceed.. Can not get amanda (2.4.2p2) to work for HP C160 running UX11.0 Amcheck runs through fine. But then dump gives me zip /zi2 lev 0 FAILED [disk /zi2 offline on zip?] Dumps are not that big - under 10GB, while I am using 20GB DLT tape. Some previous info in the amanda archive suggests checking the raw device filepermissions -- i have set all that correctly I believe. So, what else am I doing wrong?.. All your help will be greatly appreciated. - Oleg
RE: disk offline - runtar as root
I guess it must be a check thats compiled in? Try recompiling, if I remember (its been a while...) its something like --with-amanda-user=amanda [or whichever user you are using] --with-amanda-group=sys [in your case] Best to check this in the docs though! -Original Message- From: Jonathan Murray [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 18:25 To: Spicer, Kevin Cc: [EMAIL PROTECTED] Subject: Re: disk offline - runtar as root borzoi 63# pwd /usr/freeware/libexec -rwsr-x---1 root sys21876 May 31 17:36 runtar /etc/group: borzoi 6% cat /etc/group sys::0:root,bin,sys,adm,amanda root::0:root daemon::1:root,daemon bin::2:root,bin,daemon adm::3:root,adm,daemon mail::4:root uucp::5:uucp rje::8: lp:*:9: nuucp::10:nuucp user::20:amanda CMWlogin::994: other::995: demos:*:997: guest:*:998: nobody:*:60001: runtar attempt as user amanda: borzoi 8% whoami amanda borzoi 7% ./runtar runtar: error [must be invoked by root] How do did you get runtar: error [must be invoked by amanda] ? thank you, -Jonathan Murray Spicer, Kevin wrote: cd /usr/local/libexec chown root:amanda runtar chmod 4750 runtar assuming runtar is in usr/local/libexec and that the amanda user is in the amanda group... But... I suspect that you haven't got runtar in the right group (or the amanda user in the right group) as your message suggests runtar is generating the error. When try to invoke runtar on my system (as myself) I get runtar: error [must be invoked by amanda] I don't know whether this check is hardwired in at compile time - in which case you may need to recompile? -Original Message- From: Jonathan Murray [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 15:25 To: Jonathan Murray Cc: [EMAIL PROTECTED] Subject: disk offline - runtar as root It appears that the client isn't running runtar as root. Does anyone know how to force the client to run runtar as root? Thanks, Jonathan Murray from report: FAILURE AND STRANGE DUMP SUMMARY: borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 offline on borzoi?] borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 offline on borzoi?] on client: calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 sendsize: missing exclude list file /usr/local/lib/amanda/exclude.gtar discarded sendsize: spawning /usr/freeware/libexec/runtar in pipeline sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory /borzoi --one-file-system --listed-incremental /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse --ignore-failed-read --totals . runtar: error [must be invoked by root]
disk offline - runtar as root
It appears that the client isn't running runtar as root. Does anyone know how to force the client to run runtar as root? Thanks, Jonathan Murray from report: FAILURE AND STRANGE DUMP SUMMARY: borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 offline on borzoi?] borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 offline on borzoi?] on client: calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 sendsize: missing exclude list file /usr/local/lib/amanda/exclude.gtar discarded sendsize: spawning /usr/freeware/libexec/runtar in pipeline sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory /borzoi --one-file-system --listed-incremental /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse --ignore-failed-read --totals . runtar: error [must be invoked by root]
RE: disk offline - runtar as root
cd /usr/local/libexec chown root:amanda runtar chmod 4750 runtar assuming runtar is in usr/local/libexec and that the amanda user is in the amanda group... But... I suspect that you haven't got runtar in the right group (or the amanda user in the right group) as your message suggests runtar is generating the error. When try to invoke runtar on my system (as myself) I get runtar: error [must be invoked by amanda] I don't know whether this check is hardwired in at compile time - in which case you may need to recompile? -Original Message- From: Jonathan Murray [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 15:25 To: Jonathan Murray Cc: [EMAIL PROTECTED] Subject: disk offline - runtar as root It appears that the client isn't running runtar as root. Does anyone know how to force the client to run runtar as root? Thanks, Jonathan Murray from report: FAILURE AND STRANGE DUMP SUMMARY: borzoi /dev/dsk/dks0d2s7 lev 0 FAILED [disk /dev/dsk/dks0d2s7 offline on borzoi?] borzoi /dev/dsk/dks0d1s0 lev 0 FAILED [disk /dev/dsk/dks0d1s0 offline on borzoi?] on client: calculating for amname '/dev/dsk/dks0d2s7', dirname '/borzoi' sendsize: getting size via gnutar for /dev/dsk/dks0d2s7 level 0 sendsize: missing exclude list file /usr/local/lib/amanda/exclude.gtar discarded sendsize: spawning /usr/freeware/libexec/runtar in pipeline sendsize: argument list: /usr/freeware/bin/tar --create --file /dev/null --directory /borzoi --one-file-system --listed-incremental /var/amanda/gnutar-lists/borzoi_dev_dsk_dks0d2s7_0.new --sparse --ignore-failed-read --totals . runtar: error [must be invoked by root]
Re: disk offline error
Hi! Recently had a drive fail on a RAID I am backing up. Since replacing the drive and re-building the RAID, amanda has been failing on all of the partitions on this computer. The error I see in the amanda report is the following: hostname /dev/da0s1f lev 0 FAILED [disk /dev/da0s1f offline on hostname?] Does the amanda user have permissions to read /dev/da0s1* ? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Life would be easier if I had the source code.
disk offline error
Hi... Running the version of amanda-client from the freebsd ports collection on freebsd-stable i386. Recently had a drive fail on a RAID I am backing up. Since replacing the drive and re-building the RAID, amanda has been failing on all of the partitions on this computer. The error I see in the amanda report is the following: hostname /dev/da0s1f lev 0 FAILED [disk /dev/da0s1f offline on hostname?] hostname /dev/da0s1h lev 0 FAILED [disk /dev/da0s1h offline on hostname?] hostname /dev/da0s1e lev 0 FAILED [disk /dev/da0s1e offline on hostname?] hostname /dev/da0s1a lev 0 FAILED [disk /dev/da0s1a offline on hostname?] If I look in the log I see: FAIL planner hostname /dev/da0s1f 0 [disk /dev/da0s1f offline on hostname?] FAIL planner hostname /dev/da0s1h 0 [disk /dev/da0s1h offline on hostname?] FAIL planner hostname /dev/da0s1e 0 [disk /dev/da0s1e offline on hostname?] FAIL planner hostname /dev/da0s1a 0 [disk /dev/da0s1a offline on hostname?] And in the dumplog: setting up estimates for hostname:/dev/da0s1a hostname:/dev/da0s1a overdue 11825 days for level 0 setup_estimate: hostname:/dev/da0s1a: command 0, options: last_level -1 next_level0 -11825 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates for hostname:/dev/da0s1e hostname:/dev/da0s1e overdue 11825 days for level 0 setup_estimate: hostname:/dev/da0s1e: command 0, options: last_level -1 next_level0 -11825 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates for hostname:/dev/da0s1h hostname:/dev/da0s1h overdue 11825 days for level 0 setup_estimate: hostname:/dev/da0s1h: command 0, options: last_level -1 next_level0 -11825 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates for hostname:/dev/da0s1f hostname:/dev/da0s1f overdue 11825 days for level 0 setup_estimate: hostname:/dev/da0s1f: command 0, options: last_level -1 next_level0 -11825 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) -- Erik Ellestad Programmer/Analyst Cohen Group, UCSF 513 Parnassus Avenue, HSE 1285 San Francisco, CA 94143 ph: 415-476-6987fax: 415-476-6515 cell: 415-271-0588
disk offline
I would expect this to be a frequently asked question, but after looking
through Google, I didn't see much specifically on it, so...
My amdump email report starts out:
These dumps were to tape daily001.
The next tape Amanda expects to use is: daily001.
FAILURE AND STRANGE DUMP SUMMARY:
client.agic. /usr lev 0 FAILED [disk /usr offline on client.agic.ne.jp?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk client.agic.ne.jp:/usr.
driver: WARNING: got empty schedule from planner
taper: tape daily001 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
client.agic.ne /usr0 FAILED ---
(brought to you by Amanda version 2.4.2p2)
I'm not really sure where to start looking for answers here.
Can anyone suggest a starting point?
Thanks,
Shawn
Re: disk offline
On Tuesday 23 April 2002 02:38 am, GIC MLs wrote: I would expect this to be a frequently asked question, but after looking through Google, I didn't see much specifically on it, so... My amdump email report starts out: These dumps were to tape daily001. The next tape Amanda expects to use is: daily001. This in itself, is odd, very odd. Your amanda.conf seems to be out of whack somehow. [snip] (brought to you by Amanda version 2.4.2p2) Was this an rpm installed version? And whats an 'amcheck /config/' report? I'm not really sure where to start looking for answers here. Can anyone suggest a starting point? Building your own from scratch has always worked here. I have a short script that I use for the ./configure step so that each succeeding version remains compatible with the previous one by having the exact same options each time, and I'm currently running the 2.4.3b3-20020422 snapshot with a seagate changer. Thanks, Shawn -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.8+% setiathome rank, not too shabby for a hillbilly
Re: disk offline
My amdump email report starts out: These dumps were to tape daily001. The next tape Amanda expects to use is: daily001. This in itself, is odd, very odd. Your amanda.conf seems to be out of whack somehow. Well, that could very well be, I suppose... (brought to you by Amanda version 2.4.2p2) Was this an rpm installed version? No. I am running FreeBSD ports. I installed Amanda in January... I think it was done using the FreeBSD ports collection. And whats an 'amcheck /config/' report? %amcheck daily Amanda Tape Server Host Check - NOTE: skipping tape-writable test Tape daily001 label ok NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist NOTE: it will be created on the next run Server check took 5.145 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.114 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) I'm not really sure where to start looking for answers here. Can anyone suggest a starting point? Building your own from scratch has always worked here. I have a short script that I use for the ./configure step so that each succeeding version remains compatible with the previous one by having the exact same options each time, and I'm currently running the 2.4.3b3-20020422 snapshot with a seagate changer. I have no changer... A script sounds like a good idea. Thanks, Shawn
Re: disk offline ?
On Tue, 19 Feb 2002 at 7:56am, Martin Oehler wrote I got the same problem with one of my boxes. Are there known problems with amanda and ReiserFS? My log entries messages look like: got result for host pc20 disk /: 0 - -1K, -1 - -1K, -1 - -1K 0: pc20 / planner: FAILED pc20 / 0 [disk / offline on pc20?] Seems like amanda can't get the size of the disk. Any suggestions? Should I use tar unstead of dump? Well, seeing as there *is* no dump for ReiserFS, yes, you have to use tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
disk offline - addendum
sorry, I forgot OS is: SunOS fav 5.4 Generic_101945-43 sun4m sparc regards, rainer.
Re: disk offline ?
Rainer Fuegenstein [EMAIL PROTECTED] wrote: After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 Looks familiar... Try to supply the absolute path for the obstinate drive. If that helps, we're two... hauke -- Hauke Fath /~\The ASCII tangro software components GmbH \ / Ribbon Campaign D-69115 Heidelberg X Against Ruf +49-6221-13336-0, Fax -21 / \ HTML Email!
Re: disk offline ?
Hi! Hauke Fath wrote: Rainer Fuegenstein [EMAIL PROTECTED] wrote: After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 Looks familiar... Try to supply the absolute path for the obstinate drive. If that helps, we're two... I got the same problem with one of my boxes. Are there known problems with amanda and ReiserFS? My log entries messages look like: got result for host pc20 disk /: 0 - -1K, -1 - -1K, -1 - -1K 0: pc20 / planner: FAILED pc20 / 0 [disk / offline on pc20?] Seems like amanda can't get the size of the disk. Any suggestions? Should I use tar unstead of dump? CU and thanks Martin
Re: planner gives disk offline?
FAIL planner servera /data0 0 [disk /data0 offline on servera?] Always run amcheck first. That will most likely tell you that the selfcheck timed out which, in turn, should point you at detailed debugging steps in the FAQ: http://amanda.sourceforge.net/fom-serve/cache/16.html http://amanda.sourceforge.net/fom-serve/cache/140.html John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
planner gives disk offline?
Hello, Finally, went back to stable release of amanda (2.4.2p2) from sources, since debian package seems to be broken. Looking at logs got this: START driver date 20020213 START planner date 20020213 INFO planner Adding new disk servera:/data0. FAIL planner servera /data0 0 [disk /data0 offline on servera?] FINISH planner date 20020213 WARNING driver WARNING: got empty schedule from planner STATS driver startup time 1.047 Any hints buds? Regards.
disk offline
I'm here again, When i execute amdump, the backup fails FAILURE AND STRANGE DUMP SUMMARY: sc01us0105 /software/amanda/share/ lev 0 FAILED [disk /software/amanda/share/offline on sc01us0105?] frostis.cf /export/home/setup/freeware/amanda-2.4.2p2/ lev 0 FAILED [disk /export/home/setup/freeware/amanda-2.4.2p2/ offline on frostis.cf.jcyl.es?] Does anybody know why? My disklist is #hostname diskdevice ldumptype spindle interface sc01us0105 /software/amanda/share/ nocomp-test 0 frostis.cf.jcyl.es /export/home/setup/freeware/amanda-2.4.2p2/ comp-user-tar 0 And i want to usr GNUTAR. Thanks --- Javier Fernández Pérez Servicio de Informática Corporativa D.G. de Telecomunicaciones y Transportes Consejería de Fomento - Junta de Castilla y León Rigoberto Cortejoso, 14. 47014 Valladolid (Spain) e-mail: [EMAIL PROTECTED] ---
Re: disk offline
On 15 Jan 2002 at 2:47pm, [EMAIL PROTECTED] wrote FAILURE AND STRANGE DUMP SUMMARY: sc01us0105 /software/amanda/share/ lev 0 FAILED [disk /software/amanda/share/offline on sc01us0105?] frostis.cf /export/home/setup/freeware/amanda-2.4.2p2/ lev 0 FAILED [disk /export/home/setup/freeware/amanda-2.4.2p2/ offline on frostis.cf.jcyl.es?] Does anybody know why? My disklist is #hostname diskdevice ldumptype spindle interface sc01us0105 /software/amanda/share/ nocomp-test 0 frostis.cf.jcyl.es /export/home/setup/freeware/amanda-2.4.2p2/ comp-user-tar 0 And i want to usr GNUTAR. What's in sendsize*debug, amandad*debug, and/or sendbackup*debug on the failing clients? Do they have GNUtar installed? Was it there when you ./configured amanda? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
disk offline problem
Good afternoon, Well, when i execute dump... i receive the next e-mail FAILURE AND STRANGE DUMP SUMMARY: sc01us0105 /software/amanda/share/ lev 0 FAILED [disk /software/amanda/share/ offline on sc01us0105?] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - frostis.cf.j -a-2.4.2p2/ 1 14336 14336 --0:18 783.3 0:062374.2 sc01us0105 -nda/share/ 0 FAILED --- (brought to you by Amanda version 2.4.2p2) could anybody tell me what happen is? and why? My test disklist is sc01us0105 /software/amanda/share/ nocomp-test 0 frostis.cf.jcyl.es /export/home/setup/freeware/amanda-2.4.2p2/ nocomp-test 0 i'm using DUMP, if i use GNUTAR everythings gone fine. --- Javier Fernández Pérez Servicio de Informática Corporativa D.G. de Telecomunicaciones y Transportes Consejería de Fomento - Junta de Castilla y León Rigoberto Cortejoso, 14. 47014 Valladolid (Spain) e-mail: [EMAIL PROTECTED] ---
disk offline ?
Hi, After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 backup works with all other disks: fav c1t5d0s5tar-srv-low# /home1 fav c1t2d0s6tar-srv-low# /mnt2 fav / tar-srv-low # / fav /usrtar-srv-low # /usr [...] mount reports: / on /dev/md/dsk/d0 read/write/setuid on Thu Dec 27 14:40:16 2001 /usr on /dev/md/dsk/d6 read/write/setuid on Thu Dec 27 14:40:16 2001 /proc on /proc read/write/setuid on Thu Dec 27 14:40:16 2001 /dev/fd on fd read/write/setuid on Thu Dec 27 14:40:16 2001 /var on /dev/md/dsk/d4 read/write/setuid on Thu Dec 27 14:40:16 2001 /tmp on swap read/write on Thu Dec 27 14:40:21 2001 /opt on /dev/md/dsk/d5 setuid/read/write on Thu Dec 27 14:40:21 2001 /usr/openwin on /dev/md/dsk/d3 setuid/read/write on Thu Dec 27 14:40:21 2001 /mnt1 on /dev/dsk/c1t5d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 /home2 on /dev/dsk/c1t4d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 /home1 on /dev/dsk/c1t5d0s5 setuid/read/write on Thu Dec 27 14:40:21 2001 /mnt2 on /dev/dsk/c1t2d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 I already had a look at the FAQ and I'm sure that: - the disk isn't to large (2 gigs total) - the file system isn't corrupted (fsck reports OK) - tar is used for backup, not dump. so there's the permission problem left, but I'm not really familiar with sun device files. after a quick look I had the impression that permissions are the same for all disk device files. tnx in advance. regards, rainer.
disk offline - addendum
sorry, I forgot OS is: SunOS fav 5.4 Generic_101945-43 sun4m sparc regards, rainer.
Re: disk offline ?
Rainer Fuegenstein [EMAIL PROTECTED] wrote: After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 Looks familiar... Try to supply the absolute path for the obstinate drive. If that helps, we're two... hauke -- Hauke Fath /~\The ASCII tangro software components GmbH \ / Ribbon Campaign D-69115 Heidelberg X Against Ruf +49-6221-13336-0, Fax -21 / \ HTML Email!
Disk Offline
FAILURE AND STRANGE DUMP SUMMARY: bigeasy.in vg00_lvol5 lev 0 FAILED [disk vg00_lvol5 offline on bigeasy.in?] what that mean please amcheck without errors but the report giveme that. the client is a HP the serveur is a sun Solaris and the version of amanda is 2.4.2p2 thanks Best Regards, patrick -- __( / | | / \ | This message is transmitted by | \ \ | 100 % recycled electrons |___\ / |__( /__)
Re: Disk Offline
FAILURE AND STRANGE DUMP SUMMARY: bigeasy.in vg00_lvol5 lev 0 FAILED [disk vg00_lvol5 offline on bigeasy.in?] What's in /tmp/amanda/sendsize*debug on bigeasy.in? patrick John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Disk Offline
John R. Jackson wrote: FAILURE AND STRANGE DUMP SUMMARY: bigeasy.in vg00_lvol5 lev 0 FAILED [disk vg00_lvol5 offline on bigeasy.in?] What's in /tmp/amanda/sendsize*debug on bigeasy.in? patrick ho /etc/amdumpdates not there is it the prob ? ok here it is : sendsize: debug 1 pid 13246 ruid 15 euid 15 start time Thu Sep 13 22:05:52 2001 /usr/local/depot/amanda-2.4.2p2/libexec/sendsize: version 2.4.2p2 calculating for amname 'vg00_lvol5', dirname '/export/u06' sendsize: getting size via dump for vg00_lvol5 level 0 sendsize: running /usr/sbin/vxdump 0sf 1048576 - /dev/vg00/rlvol5 running /usr/local/depot/amanda-2.4.2p2/libexec/killpgrp vxdump: WARNING: no file `/etc/dumpdates', making an empty one vxdump: cannot create /etc/dumpdates: Permission denied vxdump: The ENTIRE dump is aborted. . (no size line match in above dump output) . asking killpgrp to terminate sendsize: pid 13246 finish time Thu Sep 13 22:05:53 2001 ...skipping... sendsize: debug 1 pid 29450 ruid 15 euid 15 start time Fri Sep 14 22:05:52 2001 /usr/local/depot/amanda-2.4.2p2/libexec/sendsize: version 2.4.2p2 calculating for amname 'vg00_lvol5', dirname '/export/u06' sendsize: getting size via dump for vg00_lvol5 level 0 sendsize: running /usr/sbin/vxdump 0sf 1048576 - /dev/vg00/rlvol5 running /usr/local/depot/amanda-2.4.2p2/libexec/killpgrp vxdump: WARNING: no file `/etc/dumpdates', making an empty one vxdump: cannot create /etc/dumpdates: Permission denied vxdump: The ENTIRE dump is aborted. . (no size line match in above dump output) . asking killpgrp to terminate sendsize: pid 29450 finish time Fri Sep 14 22:05:53 2001 -- __( / | | / \ | This message is transmitted by | \ \ | 100 % recycled electrons |___\ / |__( /__)
Re: Disk Offline
vxdump: WARNING: no file `/etc/dumpdates', making an empty one vxdump: cannot create /etc/dumpdates: Permission denied ... ho /etc/amdumpdates not there is it the prob ? Yes, that's the problem. Create it (as root, since it's in /etc) and make sure your Amanda user (uid 15) has read/write access to it (e.g. set the group to a group your Amanda user is a member of and chgrp g+rw /etc/dumpdates). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Disk Offline
What does /tmp/amanda/* say? Patrick LIN wrote: FAILURE AND STRANGE DUMP SUMMARY: bigeasy.in vg00_lvol5 lev 0 FAILED [disk vg00_lvol5 offline on bigeasy.in?] what that mean please amcheck without errors but the report giveme that. the client is a HP the serveur is a sun Solaris and the version of amanda is 2.4.2p2
Re: Disk Offline
Ok thanks i will let you know tomorrow after the nigthly backup thanks Best Regards Patrick John R. Jackson wrote: vxdump: WARNING: no file `/etc/dumpdates', making an empty one vxdump: cannot create /etc/dumpdates: Permission denied ... ho /etc/amdumpdates not there is it the prob ? Yes, that's the problem. Create it (as root, since it's in /etc) and make sure your Amanda user (uid 15) has read/write access to it (e.g. set the group to a group your Amanda user is a member of and chgrp g+rw /etc/dumpdates). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- __( / | | / \ | This message is transmitted by | \ \ | 100 % recycled electrons |___\ / |__( /__)
Re: disk offline
Also as suggestion that somebody kindly gave me I did as root this: [root@miro sandra]# /bin/gtar --create --file /dev/null --directory /Local --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/miro.tomandandy.com_Local_0.new --sparse --ignore-failed-read --totals /bin/gtar: Cowardly refusing to create an empty archive You forgot the trailing .. Look closely at the sendsize*debug line and you'll see it after the --totals. Sandra John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
disk offline
Hi everybody: since the last thrusday I'm getting this error "miro.toman /Local lev 0 FAILED [disk /Local offline on miro.tomandandy.com?]" I don't know what it is the problem. I have amanda 2.4.2p2 and tar(GNU tar) 1.13.17. root@miro /bin]# tar --version tar (GNU tar) 1.13.17 Copyright 2000 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. this is the report for amandad.debug and sendsize.debug amandad: debug 1 pid 2104 ruid 71 euid 71 start time Sat Jul 28 02:30:02 2001 amandad: version 2.4.2p2 amandad: build: VERSION="Amanda-2.4.2p2" amandad:BUILT_DATE="Fri Jul 20 08:42:22 EDT 2001" amandad:BUILT_MACH="Linux miro.tomandandy.com 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unkn own" amandad:CC="gcc" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient" amandad:GNUTAR="/bin/gtar" COMPRESS_PATH="/usr/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="miro.tomandandy.com" amandad:DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="miro.tomandandy.com" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN="backup" FORCE_USERID HAVE_GZIP amandad.20010728023002.debug Amanda 2.4 REQ HANDLE 000-B0B60708 SEQ 996301801 SECURITY USER backup SERVICE sendsize OPTIONS maxdumps=1;hostname=miro.tomandandy.com; GNUTAR /usr/local 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /usr/local 1 2001:7:27:7:14:56 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR /Local 0 1970:1:1:0:0:0 -1 GNUTAR /Local 1 2001:7:24:7:17:34 -1 sending ack: Amanda 2.4 ACK HANDLE 000-B0B60708 SEQ 996301801 bsd security: remote host miro.tomandandy.com user backup local user backup amandahosts security check passed amandad: running service "/usr/local/libexec/sendsize" amandad: sending REP packet: : Amanda 2.4 REP HANDLE 000-B0B60708 SEQ 996301801 OPTIONS maxdumps=1; /Local 0 SIZE -1 /Local 1 SIZE -1 /usr/local 0 SIZE 823020 /usr/local 1 SIZE 6730 amandad: got packet: Amanda 2.4 ACK HANDLE 000-B0B60708 SEQ 996301801 amandad: pid 2104 finish time Sat Jul 28 02:33:59 2001 (END) --sendsize.debug sendsize: debug 1 pid 2105 ruid 71 euid 71 start time Sat Jul 28 02:30:02 2001 /usr/local/libexec/sendsize: version 2.4.2p2 calculating for amname '/Local', dirname '/Local' sendsize: getting size via gnutar for /Local level 0 sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /Local --one-file-system --liste d-incremental /usr/local/var/amanda/gnutar-lists/miro.tomandandy.com_Local_0.new --sparse --ignore-failed -read --totals . . (no size line match in above gnutar output) . sendsize: getting size via gnutar for /Local level 1 sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /Local --one-file-system --liste d-incremental /usr/local/var/amanda/gnutar-lists/miro.tomandandy.com_Local_1.new --sparse --ignore-failed -read --totals . . (no size line match in above gnutar output) . calculating for amname '/usr/local', dirname '/usr/local' sendsize: getting size via gnutar for /usr/local level 0 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize.20010728023002.debug sendsize: argument list: /bin/gtar --create --file /dev/null --directory /usr/local --one-file-system --l isted-incremental /usr/local/var/amanda/gnutar-lists/miro.tomandandy.com_usr_local_0.new --sparse --ignor e-failed-read --totals . Total bytes written: 842772480 (804MB, 8.0MB/s) . sendsize: getting size via gnutar for /usr/local level 1 sendsize: missing exclude list file "/usr/local/lib/amanda/exclude.gtar" discarded sendsize: spawning /usr/local/libexec/runtar in pipeline sendsize: argument list: /bin/gtar --create --file /dev/null --directory /usr/local --one-file-system --l isted-incremental /usr/local/var/amanda/gnutar-lists/miro.tomandandy.com_usr_local_1.new --sparse --ignor e-failed-read --totals . Total bytes
Re: disk offline
(no size line match in above gnutar output) That line says GNU tar terminated but did not give Amanda an answer. What happens if you run this **as root** on that client: /bin/gtar --create --file /dev/null --directory /Local \ --one-file-system --listed-incremental /dev/null \ --sparse --ignore-failed -read --totals . I'm guessing you'll see some kind of error message. I would further guess that /Local is NFS mounted and root no longer has access from that client (or something like that). I can't send the sendbackup.debug file because I have only report for my other partion /usr/local not for /Local partition and I don't understand why I can't have this report, I though that with this amanda version I could have debug information for every partition that I try to back up. You do have debug information for every file system it tried to back up. It didn't try to back up /Local because the estimate failed. Sandra John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: disk offline
On May 20, 2001, Alexandre Oliva [EMAIL PROTECTED] wrote:
This appears to be a bug that triggers in a very particular
condition: when the environment is empty. It doesn't trigger with
1.12 because it just doesn't depend on librt.so.
Nope. It didn't trigger on 1.12 because it wasn't linked with GNU ld.
The problem is that GNU ld sets the dynamic linker as
/usr/lib/libc.so.1, whereas Sun ld sets it to /usr/lib/ld.so.1. Even
though Sun officially supports both, according to a friend of mine at
Sun, the one chosen by GNU ld fails because it assumes the environment
contains at least one non-NULL entry. My friend is working on a fix
for Solaris/x86 libc; I'm not sure we (GNU developers) are going to
fix GCC or GNU ld, or both, or neither, since the work-around is
simple: just link the program using
`-Wl,--dynamic-linker,/usr/lib/ld.so.1', or use Sun ld, or make sure
the environment is never empty, or wait for a patch from Sun.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: disk offline
#! /bin/sh
X=; export X
exec $0.exe ${1+$@}
What is ${1+$@} good for? Never seen that construction before...
Re: disk offline
On May 20, 2001, Bernhard R. Erdmann [EMAIL PROTECTED] wrote:
#! /bin/sh
X=; export X
exec $0.exe ${1+$@}
What is ${1+$@} good for? Never seen that construction before...
Some shells expand $@ to when $# = 0.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: disk offline
It's printed in sendsize.debug, IIRC. And in runtar.debug. It will reference a gnutar-list-dir .new file. It's created initially empty for level 0 estimates, and a copy of the lower level for incremental estimates. FWIW, I've had similar results with GNU tar 1.13.19 on Solaris 7/x86. I've started investigating, but didn't get very far, and ended up downgrading back to 1.12+patches. Hi, I solved the problem, it was an access right permission issue that was clearly indicated in /tmp/amanda/sendsize.*.debug I would suggest that this debug file is mentionned in the FAQ, about the disk offline question. It seems that it was mentionned several times on the mailing list. Here are few other ideas I had during the weekend. - My problem was due to the fact I did a ./configure --with-user=14 going with userID instead of user name. Maybe it could be clearly mentionned it should be the name and not the ID. - It appears that the estimation of the size is done with euid=ruid=amanda while the effective back-up (runtar) is done with ruid=amanda and euid=root. It would give a more accurate estimate if it was run with euid=root I think. - Apparently amcheck do not perform as deep verification as some cases can arise when amcheck will report OK while the dump will fail. The above case was one of it. - Runing amanda 2.4.2p2, with gnutar, there is no more problem with disk access permission: I configured/install amanda, as user/group amanda, did not modify anything on the disk, did not set up amanda in the goup orperator, wheel or whatever, and it runs smoothly. It is a great tool, thanks, Olivier
disk offline
Hello, I have upgraded to tar 1.13.19 but when I try to activate amanda on a client machine, I get disk off line error: FAILURE AND STRANGE DUMP SUMMARY: oak/home/fidji lev 0 FAILED [disk /home/fidji offline on oak?] oak/home/hawai lev 0 FAILED [disk /home/hawai offline on oak?] I decided to do every dump using tar only. I noticed running amstatus that the estimate could not be get for the remote machines, so I wonder what is the tar command that is used to calculate the estimate. I will try it by hand and see what I can get from it. It seems that syslog reports nothing unusual on the client machine. Dump for the Amanda server, as well as for Windows client Samba'ed from the Amanda server is working great. Best regards, Olivier
disk offline
amanda email output,
FAILURE AND STRANGE DUMP SUMMARY:
kascha sdb2 lev 0 FAILED [disk sdb2 offline on kascha?]
kascha sdb1 lev 0 FAILED [disk sdb1 offline on kascha?]
kascha sda1 lev 0 FAILED [disk sda1 offline on kascha?]
Since these are my boot disk and /usr disk they arnt off
line.
:}
Im using GNUTAR (or tryng to) using the options below,
tar version is 1.13.17-2 (latest Debian 2.2r2+)
amanda.conf8
org "DailySet1" # your organization name for reports
mailto "[EMAIL PROTECTED]" # space separated list of mail ssj
#12
dumpuser "backup" # the user to run dumps under
dumpcycle 1 #ssj added
#tapedev /dev/nst0 #ssj added disabled as per man page
inparallel 4# maximum dumpers that will run in parallel
netusage 6000 # maximum net bandwidth for Amanda, in KB persec
# a filesystem is due for a full backup once every dumpcycle days
#ssj dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 8 tapes # the number of tapes in rotation
#25
bumpsize 20 MB # minimum savings (threshold) to bump level 1 -
2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
#runtapes 9 # explained in WHATS.NEW
#tpchanger "no-changer" # the tape-changer glue script, see
TAPE.CHANGERS
tapedev "/dev/nst0" # Linux @ tuck, important: norewinding
# tapedev "/dev/nrst8" # or use the (no-rewind!) tape device directly
tapetype DEC-DAT# ssj what kind of tape it is
(seetapetypesbelow) dec-tk88
labelstr "^kaitlin[0-9][0-9]*$" # label constraint regex: all tapes
diskdir "/home/amanda" # where the holding disk is (dev/sdc1)
disksize 3000 MB# how much space can we use on
8
define tapetype DEC-DAT {
comment "DAT tape drives"
length 25000 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
speed 500 kbytes
}
-8
}
#ssj my option for linux boxes
define dumptype gnutar-full {
comment "Full dump of this filesystem always"
options compress-fast
priority high
dumpcycle 0
maxcycle 0
}
disklist8
#start with kascha
kascha sda1 gnutar-full
kascha sdb1 gnutar-full
kascha sdb2 gnutar-full
last log file
amdump: start at Tue Mar 27 07:58:01 NZST 2001
planner: pid 537 executable /usr/lib/amanda/planner version 2.4.1p1
planner: build: VERSION="Amanda-2.4.1p1"
planner:BUILT_DATE="Mon Jun 12 23:14:52 MDT 2000"
planner:BUILT_MACH="Linux rover 2.2.15pre15 #1 Thu Mar 23
02:22:27 MST 2000 i686 unknown"
planner:CC="gcc"
planner: paths: bindir="/usr/sbin" sbindir="/usr/sbin"
planner:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
planner:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
planner:RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
planner:RESTORE="/sbin/restore"
SAMBA_CLIENT="/usr/bin/smbclient"
planner:GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip"
planner:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
planner:listed_incr_dir="/var/lib/amanda/gnutar-lists"
planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
planner:DEFAULT_TAPE_SERVER="localhost"
planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
planner:USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID
HAVE_GZIP
planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
READING CONF FILES...
driver: pid 538 executable /usr/lib/amanda/driver version 2.4.1p1
driver: send-cmd time 0.003 to taper: START-TAPER 20010327
startup took 0.005 secs
SETTING UP FOR ESTIMATES...
setting up estimates for kascha:sda1
kascha:sda1 overdue 11408 days for level 0
setup_estimate: kascha:sda1: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates for kascha:sdb1
kascha:sdb1 overdue 11408 days for level 0
setup_estimate: kascha:sdb1: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates for kascha:sdb2
kascha:sdb2 overdue 11408 days for level 0
setup_estimate: kascha:sdb2: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates took 0.000 secs
GETTING ESTIMATES...
driver: started dumper0 pid 540
driver: started dumper1 pid 541
driver: started dumper2 pid 542
driver: started dumper3 pid 543
taper: pid 539 executable taper version 2.4.1p1
dumper: pid 540 executable dumper version 2.4.1p1, using port 540
dumper: pid 541 executable dumper version 2.4.1p1, using port 541
dumper: pid 542 executable dumper version 2.4.1p1, using port 542
dumper: pid 543
Re: disk offline
FAILURE AND STRANGE DUMP SUMMARY: kascha sdb2 lev 0 FAILED [disk sdb2 offline on kascha?] kascha sdb1 lev 0 FAILED [disk sdb1 offline on kascha?] kascha sda1 lev 0 FAILED [disk sda1 offline on kascha?] Since these are my boot disk and /usr disk they arnt off line. That's a generic statement for some kind of access problem. Running amcheck is always the first thing to do in cases like this. It reports much more specific information. If that doesn't help, look at /tmp/amanda/sendsize*debug on kascha. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
