Re: tapetype problem (now)
Mozzi wrote:
HI
Yes it is updateing I am now on the second set of numbers
[root@ais-back01 tape-src]# ./tapetype -e 40960 -f /dev/nst0 -t
TandbergVS80
wrote 1235460 32Kb blocks in 102955 files in 275434 seconds (short write)
wrote 701742 32kb blocks in 116977 files
It is still busy,almost 6 days now
From these numbers I can see you are using an old version of tapetype.
The newer version is much faster (it writes only about 100 files in the
first pass to fill the tape).
Attached is a patched version (not official, based on the fast 4.2.3b3)
that detects compressed tape drives, and gives an estimate after a few
minutes how long it will take for the total run (so you can plan to
go fishing if you like).
--
Paul Bijnens, Xplanation Tel +32 16 40.51.40
Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61
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 *
***
/*
* Amanda, The Advanced Maryland Automatic Network Disk Archiver
* Copyright (c) 1991-1998 University of Maryland at College Park
* All Rights Reserved.
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that
* copyright notice and this permission notice appear in supporting
* documentation, and that the name of U.M. not be used in advertising or
* publicity pertaining to distribution of the software without specific,
* written prior permission. U.M. makes no representations about the
* suitability of this software for any purpose. It is provided as is
* without express or implied warranty.
*
* U.M. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL U.M.
* BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
* Author: James da Silva, Systems Design and Analysis Group
* Computer Science Department
* University of Maryland at College Park
*/
/*
* $Id: tapetype.c,v 1.1.1.1 2002/09/16 10:36:33 paulb Exp $
*
* tests a tape in a given tape unit and prints a tapetype entry for
* it. */
#include amanda.h
#include tapeio.h
#define NBLOCKS 32 /* number of random blocks */
static char *sProgName;
static char *tapedev;
static int fd;
static int blockkb = 32;
static int blocksize;
static char *randombytes = (char *) NULL;
#if USE_RAND
/* If the C library does not define random(), try to use rand() by
defining USE_RAND, but then make sure you are not using hardware
compression, because the low-order bits of rand() may not be that
random... :-( */
#define random() rand()
#define srandom(seed) srand(seed)
#endif
static void initnotrandombytes() {
int i, j;
char *p;
j =NBLOCKS * blocksize;
if (randombytes == (char *)NULL) {
randombytes = alloc(j);
}
p = randombytes;
for(i=0; i j; ++i) {
*p++ = (char) (i % 256);
}
}
static void initrandombytes() {
int i, j;
char *p;
j = NBLOCKS * blocksize;
if (randombytes == (char *)NULL) {
randombytes = alloc(j);
}
p = randombytes;
for(i=0; i j; ++i) {
*p++ = (char)random();
}
}
static char *getrandombytes() {
static int counter = 0;
return randombytes + ((counter++ % NBLOCKS) * blocksize);
}
static int short_write;
int writeblock(fd)
int fd;
{
size_t w;
if ((w = tapefd_write(fd, getrandombytes(), blocksize)) == blocksize) {
return 1;
}
if (w = 0) {
short_write = 1;
} else {
short_write = 0;
}
return 0;
}
/* returns number of blocks actually written */
size_t writeblocks(int fd, size_t nblks)
{
size_t blks = 0;
while (blks nblks) {
if (! writeblock(fd)) {
return 0;
}
blks++;
}
return blks;
}
void usage()
{
fputs(usage: , stderr);
fputs(sProgName, stderr);
fputs( -h, stderr);
fputs( [-b blocksize], stderr);
fputs( [-e estsize], stderr);
fputs( [-f tapedev], stderr);
fputs( [-t typename], stderr);
fputc('\n', stderr);
}
void help()
{
usage();
fputs(\
-h
Re: win32
On Tue, 17 Sep 2002 15:58:26 -0400
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
--- In [EMAIL PROTECTED], JC Simonetti [EMAIL PROTECTED] wrote:
snip
Well... You're right, I got the actual state of the Sourceforge
project and did not touch to anything to the sources. Everything goes
well.
For your bugs :
1. selfcheck bug is not a bug, it's just that selfcheck is not
provided in the Win32 version. If you are suck with the amcheck
errors, do the same thing as me : selfcheck.c : int main() {return
0;}, and if you are lazy compiling such a thing, I've attached it
here.
2. sendsize crash ? Well... Er... Er... Er... Where ??? I've had
some problems with sendsize, but it corrected itself with the
-udp=10080 -no-exit parameters to the amandad.exe program. I did not
examine precisely the source code but the -no-exit seems to be very
important...
What I've done with this project? Well... Just got it from
Sourceforge and installed it on W2K boxes: what I've done is installed
it as a WinNT service. I am running it with an Amanda 2.4.3b2 server
on a Linux box, and no errors reported yet (1,5 Go backed up every
night). Not checked with omre recent versions.
--
Jean-Christian SIMONETTI email: [EMAIL PROTECTED]
SysAdmin Wanadoo Portails phone: (+33)493004911
Sophia Antipolis, France
--
Are you SURE there are no errors? I tested this yesterday. It
appears that sendbackup only logs the errors tothe debug file in
/tmp/amanda. Also, each sendbackup process overwrites this file.
It also appears that this doesn`t support excludes. Amandad reports
the standard exclude list path, but I couldn,t get it to work.
You previously mentioned that amanda maps the archive bit to the UNIX
execute bit. It is actually the win32 tar that does this. I believe
Samba also doed this to help preserve the Windows permissions.
This appears to be early alpha quality software, not ready for
production. Unfortunately, it also appears to be abandoned :-(
Bruce Osborne
I am sure there are no errors. I am currently backing up 6 servers for a total amount
of 2 Go, everything goes perfectly well.
Concerning the exludes, it is written that this feature does not work from now on.
Concerning the NT rights, Samba does NOT preserve them. Samba backs up the bits from
the files, and if their names are in US-ASCII (whoops, I'm french, don't forget the
accentuated characters) the names are also backed up (I've got problems with special
characters translation and no recover possible for some files, due to their names that
had been changed.
And as for the general quality, I think you're right when you speak about alpha
quality. But when I see the smbtar feature, I prefer an alpha quality that works (I
managed to make it work in my environment) rather than a solution that tells me
everyday ? ERRDOS - ERRbadshare opening remote file \EF\EFinfo2.SDC (\EF\) and that
I am not sure to be able to recover the data I am backing up...
The actual version of Win32 Amanda is yet in development version (not even in unstable
mode, to speak Debian-like). But I prefer this solution, as I managed to make it work,
rather than the smbtar I couldn't make it work correctly.
If someone is interested in going through the development of this client, we might
start the development again... But I cannot do it alone, I do not have enough time.
Re: tapetype problem (again)
Mozzi wrote: Paul Bijnens wrote: Mozzi wrote: HI Yes it is updateing I am now on the second set of numbers [root@ais-back01 tape-src]# ./tapetype -e 40960 -f /dev/nst0 -t TandbergVS80 wrote 1235460 32Kb blocks in 102955 files in 275434 seconds (short write) wrote 701742 32kb blocks in 116977 files It is still busy,almost 6 days now From these numbers I can see you are using an old version of tapetype. The newer version is much faster (it writes only about 100 files in the first pass to fill the tape). Attached is a patched version (not official, based on the fast 4.2.3b3) that detects compressed tape drives, and gives an estimate after a few minutes how long it will take for the total run (so you can plan to go fishing if you like). Hi I got this [root@ais-back01 tape-src]# ./tapetype -e 40960 -f /dev/nst0 -t Ooops. Your estimate is missing the units (kbytes default). Try: ./tapetye -e 40g -f /dev/nst0 -t tandberg_VS80 tandberg_VS80 Estimate phase 1... Estimate phase 2... Estimated time to write 2 * 40 Mbyte: 45 sec = 0 h 0 min wrote 1692 32kb blocks in 152 files Should it be writing 32kb blocks ? Looks like it is going on again -- Paul Bijnens, Xplanation Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 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: tapetype problem (now)
On Wed, Sep 18, 2002 at 08:48:45AM +0200, Mozzi wrote: HI Yes it is updateing I am now on the second set of numbers [root@ais-back01 tape-src]# ./tapetype -e 40960 -f /dev/nst0 -t TandbergVS80 wrote 1235460 32Kb blocks in 102955 files in 275434 seconds (short write) wrote 701742 32kb blocks in 116977 files It is still busy,almost 6 days now Way too many files being written. Your estimate is too low or you are using an old version of tapetype. I just looked at the source for tapetype. It seems to take the estimate with no suffix, as KB. Thus your estimate is claiming a 40MB total tape capacity. This is then divided by 1000 (100?) to determine the size of each file of random data to write. Probably you should have given the estimate as 4M or 40G -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Help please
Is someone out there kind enough to share a good howto on installing amanda? I am planning to reinstall my non-working f** amanda. I have tried the INSTALL file that comes with it. I also have posted earlier about the issue I was encountering but never had any replies to that POST. Thanks.
Re: Help please
On Wed, Sep 18, 2002 at 05:33:52AM -0500, Neil wrote: Is someone out there kind enough to share a good howto on installing amanda? I am planning to reinstall my non-working f** amanda. I have tried the INSTALL file that comes with it. I also have posted earlier about the issue I was encountering but never had any replies to that POST. Thanks. Amanda requires an awful lot of ducks to be in a nice neat row, and the documentation isn't always completely transparent. INSTALL, at least the one at the top of the source tree, is a generic free software install instruction. Nothing Amanda-specific. Have you also read README, and have you followed the references: HOW DO I GET AMANDA UP AND RUNNING? --- Read the file docs/INSTALL. There are a variety of steps, from compiling Amanda to installing it on the tape server host and the client machines. docs/INSTALLcontains general installation instructions. docs/SYSTEM.NOTES contains system-specific information. docs/FAQcontains answers to frequently asked questions. docs/KERBEROS explains installation under Kerberos 4. docs/TAPE.CHANGERS explains how to customize the changer interface. docs/WHATS.NEW details new features. Persevere. It's a great package once you have it working. I missed your earlier post. Perhaps you could tell us a little about what you've tried, and about what where things went wrong. -- - Dan Wilder [EMAIL PROTECTED] Technical Manager SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://www.linuxjournal.com/ -
Colorado, again
Hi all,
Still gnashing my teeth over this HP Colorado drive. Found some pointers
which suggested disabling DMA -- have done so for both drives on that
controller. Got 3 successful dumps since Thursday (3GB written).
The problem today is as follows. The dumps failed with an Input/Output
error after 299kb written. When amcheck ran (without changing the tape) it
failed before reading the tape. My logs give me:
Sep 18 10:45:01 valhalla kernel: st: Version 20020205, bufsize 32768, wrt
30720, max init. bufs 4,
s/g segs 16
Sep 18 10:45:01 valhalla kernel: Attached scsi tape st0 at scsi0, channel 0,
id 0, lun 0
Sep 18 10:45:01 valhalla kernel: st0: Block limits 6684 - 1711130 bytes.
Sep 18 11:00:01 valhalla kernel: scsi : aborting command due to timeout : pid
329140, scsi0, channel 0, id 0, lun 0 Read (6) 01 00 00 40 00
Sep 18 11:00:01 valhalla kernel: hdd: irq timeout: status=0xc0 { Busy }
Sep 18 11:00:02 valhalla kernel: hdd: ATAPI reset complete
Sep 18 11:00:02 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
Sep 18 11:00:02 valhalla kernel: hdd: ATAPI reset complete
Sep 18 11:00:02 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
Sep 18 11:00:02 valhalla kernel: st0: Error 2707 (sugg. bt 0x20, driver
bt 0x7, host bt 0x7).
Sep 18 11:20:01 valhalla kernel: st: Unloaded.
Can I be sure that those IRQ timeouts are due to a faulty device? Can there
be another explanation?
Regards,
Brian Jonnes
--
Init Systems - Linux consulting
031 767-0139082 769-2320[EMAIL PROTECTED]
Re: Help please
Hi! On Wednesday 18 September 2002 12:33, [EMAIL PROTECTED] wrote: Is someone out there kind enough to share a good howto on installing amanda? I can recommend this one: http://www.storagemountain.com/amanda.html It helped me installing AMANDA and I think it is very well written. Regards, Stefan.
Re: Help please
On Wednesday 18 September 2002 06:33, Neil wrote:
Is someone out there kind enough to share a good howto on
installing amanda? I am planning to reinstall my non-working
f** amanda. I have tried the INSTALL file that comes with it.
I also have posted earlier about the issue I was encountering but
never had any replies to that POST.
Thanks.
I've been keeping up with the 2.4.3 branch, which means I rebuild it
everytime Jean-Louis makes another snapshot available.
I do the builds in /home/amanda/amanda-version-number by unpacking
tha tar.gz's there as root, then do a chown -R amanda:disk * to
set the owner:group of the unpacked files. Then I call up whatever
file manager you use and copy the gh.cf file from the previous
version's top level directory to the new versions top level
directory. This is the file that contains all the options one
needs to configure amanda, and it looks like this:
#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo Warning
echo Amanda needs to be configured and built by the user amanda,
echo but must be installed by user root.
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-tape-device=/dev/nst0 \
--with-changer-device=/dev/sg1 \
--with-gnu-ld --prefix=/usr/local \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=192.168.1.3 \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda
--
Customize to suit of course, particularly the with-tape-server=
line, and whatever devices will be used to access the tape drive
and robot on your system.
Then with the prelims out of the way, cd to the new versions tree,
do an su amanda (you do have a user amanda don't you? And amanda
is a member of group disk? Ok, just checking:)
and do
#./gh.cf
which is the name of the above file.
when the configure is done;
#make
get back to root
#exit
and
#make install
All done, all the execution perms are set correctly and amanda is
ready to use.
If you don't already have the working configuration setup, then you
will have to use (as amanda, not root!) the amcheck utility to help
you pinpoint the missing files and to actually get it ready for
use, the syntax being amcheck /config/ where /config/ is the name
of the subdir in (from above, /usr/local/etc/amanda/config) where
all of amandas controlling file, and her record keeping, will live.
If running a later RH system, RH is now using xinetd instead of
inetd, and you will need this file, named amanda, to be placed in
your /etc/xinetd.d directory.
--
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons such it needs
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
---
The rest is the a---s elbows grunt work of getting all the
needed files touched, directories made according to the output of
amcheck. Note that WARNING's aren't fatal as they will be created
by amdump, but I prefer to do all that ahead of time just to
prevent last minute gotcha's.
Once amcheck is happy with everything but the tape name it finds,
then you start to apply labels to your rotating tape stock, for my
system I use 20 tapes so the /config/amanda.conf file has
dumpcycle 1 week
tapecycle 20
runtapes 1
runspercycle 1
Ones tapecycle should be at least 2x dumpcycle tapes.
This setup has no provision for long term storage since this is a
home machine setup of 2 machines, with rsync making a mirror of one
machine on the others bigger drive. If I make a mistake and need
to restore, I'll know I need to restore well before the tapecycle
is done and the restore I need has been overwritten, so its
adequate for me. If you want long term storage, then most setup
another /config/ directory and set that one up to always do fulls
(runtapes may have to be expanded in that case) at say weekly
Re: Colorado, again
On Wednesday 18 September 2002 07:03, Brian Jonnes wrote:
Hi all,
Still gnashing my teeth over this HP Colorado drive. Found some
pointers which suggested disabling DMA -- have done so for both
drives on that controller. Got 3 successful dumps since Thursday
(3GB written).
The problem today is as follows. The dumps failed with an
Input/Output error after 299kb written. When amcheck ran
(without changing the tape) it failed before reading the tape. My
logs give me:
Sep 18 10:45:01 valhalla kernel: st: Version 20020205, bufsize
32768, wrt 30720, max init. bufs 4,
s/g segs 16
Sep 18 10:45:01 valhalla kernel: Attached scsi tape st0 at scsi0,
channel 0, id 0, lun 0
Sep 18 10:45:01 valhalla kernel: st0: Block limits 6684 - 1711130
bytes. Sep 18 11:00:01 valhalla kernel: scsi : aborting command
due to timeout : pid 329140, scsi0, channel 0, id 0, lun 0 Read
(6) 01 00 00 40 00 Sep 18 11:00:01 valhalla kernel: hdd: irq
timeout: status=0xc0 { Busy } Sep 18 11:00:02 valhalla kernel:
hdd: ATAPI reset complete Sep 18 11:00:02 valhalla kernel: hdd:
irq timeout: status=0x80 { Busy } Sep 18 11:00:02 valhalla
kernel: hdd: ATAPI reset complete Sep 18 11:00:02 valhalla
kernel: hdd: irq timeout: status=0x80 { Busy } Sep 18 11:00:02
valhalla kernel: st0: Error 2707 (sugg. bt 0x20, driver bt
0x7, host bt 0x7).
Sep 18 11:20:01 valhalla kernel: st: Unloaded.
Can I be sure that those IRQ timeouts are due to a faulty device?
Can there be another explanation?
Regards,
Brian Jonnes
I've run into a similar situation, but on my cdrw. When the driver
get its hole in the sock fixed, maybe, but till then its reboot
time to re-initilalize and fix the driver. One of the reasons to
use scsi where scsi does it best I guess.
What kernel version again please?
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Help please
Neil wrote: Is someone out there kind enough to share a good howto on installing amanda? I am planning to reinstall my non-working f** amanda. I have tried the INSTALL file that comes with it. I also have posted earlier about the issue I was encountering but never had any replies to that POST. Thanks. http://www.frankenlinux.com/guides/amandaserver.html Mozzi
Comments in .amandahosts
Hi there, Is it possible to add some comments in the .amandahosts file ? For example: # this is my comment bla bla bla bla 192.168.200.200 amandauser Regards Marc
Re: Comments in .amandahosts
On Wednesday 18 September 2002 08:01, [EMAIL PROTECTED] wrote: Hi there, Is it possible to add some comments in the .amandahosts file ? For example: # this is my comment bla bla bla bla 192.168.200.200 amandauser Regards Marc Good Q Marc, all I can say is I don't have any in mine. You can add a line, and run amcheck to see if it complains I suppose. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
Re: Comments in .amandahosts
Well looks like comments starting with # in .amandahosts works, I added a few line of comments in it and did an amcheck, no errors where returned... Marc Gene Heskett To: [EMAIL PROTECTED], [EMAIL PROTECTED] gene_heskett@i cc: olinc.netSubject: Re: Comments in .amandahosts 09/18/02 03:19 PM On Wednesday 18 September 2002 08:01, [EMAIL PROTECTED] wrote: Hi there, Is it possible to add some comments in the .amandahosts file ? For example: # this is my comment bla bla bla bla 192.168.200.200 amandauser Regards Marc Good Q Marc, all I can say is I don't have any in mine. You can add a line, and run amcheck to see if it complains I suppose. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly
newbie needs help deciphering vauge error message
Hi, I think I've managed to setup amanda to backup my desktop PC from a
central backup server. amcheck returns all is well, so I decided to run
amdump daily.
I've attached the dump report below. Could someone point me in the
directions of some diagnostics ?
(BTW, I'm incredibly impressed by the faq-o-matic the large number of
possible error messages explained in the man pages...I just wish this
report had a few error messages in it).
John
begin forwarded file
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape DailySet1-000.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
jlooney.ji /home RESULTS MISSING
jlooney.ji /etc RESULTS MISSING
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:00 0:00 0:00 (0:00 start)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
^L
NOTES:
driver: WARNING: got empty schedule from planner
taper: tape DailySet1-000 kb 0 fm 0 [OK]
^L
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
--
jlooney.j /etc MISSING
jlooney.j /home MISSING
readline termcap libraries?.
Title: readline termcap libraries?. Hi Group, Can anyone advise -- which version of readline library should be used?.. GNU site has v4.3, while the amanda docs recommend 2.2, so does that matter?.. Also, should readline use termcap (there is 1.3.1 dated last month or so..) or ncurses?.. I am putting all that together on SPARC Solaris 8 (if that matters..) Your advices will be deeply appreciated. thanks, Oleg
Re: help for compiling amanda to support xfsdump in RH 7.3
Hi Joshua: I tried to recompile amanda client to support xfsdump...and followed the four steps you mentioned below...for some reason, it still can not backup xfs volume on that client...so, I am wondering that something must be wrong when I was doing the recompiling... Could you please give me a little more specific instructions about this? I really appreciate your help. Thanks a lot, Zhen Liu --- On Fri, 23 Aug 2002 at 10:30am, Zhen Liu wrote I first checked that I have xfsdump installed in the box, then I started to run ./configure, make, make check, make install...and configured the amanda client...it seems like amanda can not recognize the xfs... First check to make sure that ./configure finds xfsdump: checking for xfsdump... /sbin/xfsdump checking for xfsrestore... /sbin/xfsrestore configure: warning: *** xfsdump causes the setuid-root rundump program to be enabled configure: warning: *** to disable it, just #undef XFSDUMP in config/config.h I saw these when I was running ./configure... Second, make sure you're doing the 'make install' as root, or the bits that need to be setuid won't be. I was doing the 'make, make check, anda make install' as root... Third, are your XFS partitions in the fstab? I have the XFS paritions in the fstab... Fourth, make sure you're trying to use xfsdump on entire partitions only -- it won't work on subdirectories. I am trying to use xfsdump on entire partitions. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University Zhen Liu Via Webmail [EMAIL PROTECTED]
Re: Comments in .amandahosts
Gene Heskett wrote: On Wednesday 18 September 2002 08:01, [EMAIL PROTECTED] wrote: Is it possible to add some comments in the .amandahosts file ? For example: # this is my comment bla bla bla bla 192.168.200.200 amandauser Good Q Marc, all I can say is I don't have any in mine. You can add a line, and run amcheck to see if it complains I suppose. I just read through the source code (common-src/security.c, line 426 etc) , and it seems that the first two fields, separated by whitespace are always interpreted as hostname and username. The rest of the line is ignored. The file is read sequentially, until a match (simple strcasecmp) is found, or until eof. Empty lines and very long lines are handled fine (no buffer overflows). So I suppose you could say: # # this is my comment bla bla bla # # some more comments # # Just make sure the first two fields are not existent 192.168.200.200 amandauser # this part is ignored too And never have some host named '#' (I believe that would be very difficult to achieve?) Bordercase: the second field is always the username, so next line allows only the user named '#' to access the amandaserver, probably not what you intended. 192.168.200.201 # WRONG! only the user named '#' is allowed! 192.168.200.201 # # even double hashes is wrong. Well you could just as well have the comments in a file named README in the amanda home directory. That makes it safer when the source changes. -- Paul Bijnens, Xplanation Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 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: readline termcap libraries?.
On Wed, Sep 18, 2002 at 09:59:48AM -0400, Oleg Svintsitski mentioned: I am putting all that together on SPARC Solaris 8 (if that matters..) Your advices will be deeply appreciated. I'd advise visiting www.sunfreeware.com and getting the solaris 8 Amanda package - it's what I did, and saved me a lot of time! John
Re: amanda/iptables problem
Galen Johnson wrote:
John Dalbec wrote:
I sometimes get sendsize packets being dropped by iptables, presumably
because the iptables connection tracking decided the UDP connection
was closed. This causes the estimates to take much longer because the
first sendsize process gives up. Has anyone found a solution to this?
Thanks,
John Dalbec
I am currently running amanda through an iptables based firewall with no
issues. I'm using Slack 8.1. Are you able to log the drops?
I'm using Red Hat 7.1, kernel 2.4.9-34 w/ReiserFS quota patches.
These dumps were to tape DailySet104.
The next tape Amanda expects to use is: DailySet105.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)1:00
Run Time (hrs:min) 1:23
Dump Time (hrs:min)0:20 0:06 0:15
Output Size (meg)4865.8 1339.5 3526.2
Original Size (meg) 4865.8 1339.5 3526.2
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 23 3 20 (1:19 3:1)
Avg Dump Rate (k/s) 4098.2 4008.7 4133.3
Sep 12 00:45:32 mail03 kernel: INT_IN DROP 5 IN=eth0 OUT=
MAC=00:02:55:58:9d:fa:00:02:55:7c:ff:52:08:00 SRC=150.134.10.202
DST=150.134.10.203 LEN=304 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP
SPT=10080 DPT=604 LEN=284
Sep 12 00:45:34 mail03 kernel: INT_IN DROP 5 IN=eth0 OUT=
MAC=00:02:55:58:9d:fa:00:02:55:7c:fd:01:08:00 SRC=150.134.10.201
DST=150.134.10.203 LEN=265 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP
SPT=10080 DPT=604 LEN=245
Sep 12 00:45:42 mail03 kernel: INT_IN DROP 5 IN=eth0 OUT=
MAC=00:02:55:58:9d:fa:00:02:55:7c:ff:52:08:00 SRC=150.134.10.202
DST=150.134.10.203 LEN=304 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP
SPT=10080 DPT=604 LEN=284
Sep 12 00:45:44 mail03 kernel: INT_IN DROP 5 IN=eth0 OUT=
MAC=00:02:55:58:9d:fa:00:02:55:7c:fd:01:08:00 SRC=150.134.10.201
DST=150.134.10.203 LEN=265 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP
SPT=10080 DPT=604 LEN=245
Sep 12 00:45:52 mail03 kernel: INT_IN DROP 5 IN=eth0 OUT=
MAC=00:02:55:58:9d:fa:00:02:55:7c:ff:52:08:00 SRC=150.134.10.202
DST=150.134.10.203 LEN=304 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP
SPT=10080 DPT=604 LEN=284
... there are more, but you get the idea.
The connection tracking should be handling this. If I have to hack my
firewall to let these packets through I might as well be using ipchains.
Thanks,
John Dalbec
Re: Help please
Hey guys, thanks for that massive replies :) Anyway, My system is FreeBSD 4.6 STABLE. I've tried reinstalling amanda but this time, using the ports and not from the the source. I think, it's almost the same as ports grabs the source file. Anyway, I modified the Makefile in /usr/ports/misc/amanda-server, specifically --with-user. Now, it's set to --with-user=amanda. I also modified the group for the amanda account in /etc/passwd using vipw. When I executed su amanda -c amcheck Daily, it told me that the tape is not an amanda. I search google and found out that from a thread the I should execute amlabel. I tried amlabel Daily VOL01 but that didn't work. Fortunately, it showed me a regular expressions that I should follow. So I executed it again as amlabel Daily Daily01. This time it worked. I also tried dd if=/dev/nsa0 bs=32k count=1, then I saw the headers of my tape which was AMANDA, .. so on :) Tonight, I will try backing up a data. But I would like someone to visit my amanda.conf in http://restricted.dyndns.org/amanda.conf. I only have 1 tape drive and 1 tape. I am only doing this at home and is very determined to learn amanda. I would like to have a full backup every saturday 10pm only. No needs yet for incremental. Once I have bought new tapes, I will post here again about it. :) Btw, i did use non-rewind on my amanda.conf, I don't know if I got the right device entered there (/dev/nrsa0). So please give me some fix that I need to do on my amanda.conf Thank you very much for all the help and succeeding ones. Neil
Antigen Notification:Antigen found FILE FILTER= in*.exe file
Antigen for Exchange found selfcheck.exe matching FILE FILTER= in*.exe file filter. The file is currently Removed. The message, Re: win32, was sent from JC Simonetti and was discovered in IMC Queues\Inbound located at Cognex/Tokyo/WENDY.
Antigen Notification:Antigen found FILE FILTER= in*.exe file
Antigen for Exchange found selfcheck.exe matching FILE FILTER= in*.exe file filter. The file is currently Removed. The message, Re: win32, was sent from JC Simonetti and was discovered in IMC Queues\Inbound located at Cognex/Tokyo/WENDY.
Re: Measure and Graph Tape Usage
On Friday 13 September 2002 13:17, Galen Johnson wrote: Jason Greenberg wrote: Is there any way to measure how many bytes where written to the tape every night? I would like to feed the values to MRTG or something, so I can see when I am close to using two tapes per dump. Also, if the data is available, is it the raw uncompressed bytes, or the post-gzipped bytes that are recorded? I would like to see the both, to measure my compression ratios. Thanks group, Jay Yes, that information is available but you will need to be able to parse the email amanda sends you after she completes a run. =G= One could also take a look with amplot, but I find its a bit hard to interpret. Probably me, but... -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.265987 secs) *** Qmail-Scanner Envelope Details End ***
Re: Dumpcycles vs Runs
On Saturday 14 September 2002 12:57, Jason Greenberg wrote: You'll have to excuse my newbieness for this one, if you would... If I have a dumpcycle of 7 days, with 7 runs per cylce, I understand that I will have a full backup every 7 days. So, if that's the case, here are my questions: 1) How many tapes are used for these 7 runs? 7? or just 1? At least one per run, more if you permit, and amanda needs to use. 2) does the tape change after every dumpcycle or every run? Run, but not until the next dump, or amcheck run which is why you have a cron job in the middle of the day that does this amcheck, and if it fails to find the next required tape, sends you an email advising you of this problem so you can fix it before the real run while you are busy checking your eyelids for leaks, :-D 3) I have 15 tapes, and I would like to use 1 tape per week, with 15 weeks of total history. What would the dumpcycle / runspercycle config be? But to satisfy the requirements you lay out while maintaining a full each week, dumpcycle would be 7 days or 1 week, and runspercycle wopuld be 7, tapecycle would be runspercycle*weeks, or a minimum of 105 tapes for a runspercycle of 7. IMO thats overkill of the type only needed in banking or insurance, but if thats the case, then I'd expect the cost of the tapes can be justified easily. Please understand that amanda doesn't do two things for pure dependability reasons. One, because of the possibility of someone miss-positioning a tape, amanda does not ever do an append to an existing backup on a tape even if there is only 2 megs on a 50 gig tape. That tape is not allowed to be re-used until its turn in the tapecycle comes around again. And two, again for the same reason, amanda cannot span more than one tape with a given filesystem entry in the disklist. If a partition at level 0 is bigger than a tape, then you must use tar, not dump, and specify individual subdirs in that partition that are small enough to fit on one tape in the disklist. I do that with /usr since /usr is about 33 gigs if full, and I'm using just one 4 gig DDS2 tape per nightly run. I have presently 37 entries in the disklist, and amanda schedules one or more fulls every night, and then does incrementals to fill up the remainder, attempting to arrive at a value on tape that is pretty close to the running average tape usage. Here, that running average is about 2 gigs on a 4gig tape to cover a 46 gig drive with a full every week. And tapecycle is 20 tapes, so I have at least 2 fulls on hand at any one time. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.26606 secs) *** Qmail-Scanner Envelope Details End ***
Re: [Amanda-users] Re: Tape DDS-3 values
Good drives and tapes rarely have errors. If you are getting frequent tape errors you should investigate why; your tapes and/or drives could be in need of cleaning/repair/replacement. Since failing drives and tapes don't get better, just worse, you will be continually adding more workarounds (shorter backup cycles, duplicate backups, duplicating data on your systems, archiving in error-tolerant formats, etc.) and still always live in fear of having to attempt a restore. I've been there, done that, and its certainly no fun. If your company won't pay to repair or replace whatever it takes, and you don't have any other employment options at the moment (I know times are tough in IT), be sure to document your problems, send memos, add it to your reports, so when (not if) you are unable to restore critical data due to tape errors you won't be the one escorted out the door. Frank --On Saturday, September 14, 2002 13:16:10 +1000 Jason Thomas [EMAIL PROTECTED] wrote: we had the same problem, we now store the data uncompressed on the tape. And still get frequent errors. On Fri, Sep 13, 2002 at 06:14:46PM +0100, Niall O Broin wrote: On Fri, Sep 13, 2002 at 10:25:29AM -0400, Jon LaBadie wrote: Is it a real, or theoretical, problem? I.e. has anybody experienced bit errors in a gzip'ed document? For me the incidence is low enough that I don't feel a need to use bzip2 for that extra protection. The value of your data may lead to a different conclusion. I brought this up and it's not theoretical - I've had problems with gzipped tar files coming back off tapes. I definitely have problems with my tape drive but as mentioned, such errors in a tar file would only have caused problems with some files - with the gzipped tar file, you're done for once you hit an error. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.53702 secs) *** Qmail-Scanner Envelope Details End ***
Re: Dumpcycles vs Runs
On Sat, Sep 14, 2002 at 12:57:15PM -0400, Jason Greenberg wrote: You'll have to excuse my newbieness for this one, if you would... If I have a dumpcycle of 7 days, with 7 runs per cylce, I understand that I will have a full backup every 7 days. So, if that's the case, here are my questions: 1) How many tapes are used for these 7 runs? 7? or just 1? 2) does the tape change after every dumpcycle or every run? 3) I have 15 tapes, and I would like to use 1 tape per week, with 15 weeks of total history. In that case, use a different backup program. Unless you only plan to backup (run amdump) once a week. Then: dumpcycle 1 wk# maybe 0 runspercycle1 runtapes1 tapecycle 15 -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.263501 secs) *** Qmail-Scanner Envelope Details End ***
Re: Measure and Graph Tape Usage
On Saturday 14 September 2002 12:44, Jason Greenberg wrote: Is there any way to measure how many bytes where written to the tape every night? I would like to feed the values to MRTG or something, so I can see when I am close to using two tapes per dump. Also, if the data is available, is it the raw uncompressed bytes, or the post-gzipped bytes that are recorded? I would like to see the both, to measure my compression ratios. Thanks group, Jay Are you not getting an email from amanda for each run? All of this info is part of the report she emails the maintainer of record as defined in the top of the amanda.conf file. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.15% setiathome rank, not too shabby for a WV hillbilly *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.35383 secs) *** Qmail-Scanner Envelope Details End ***
Re: tape error
On Fri, Sep 13, 2002 at 11:55:31AM -0700, John Koenig wrote: Anyone seen this tape error message before? Does this indicate a bad tape or a tape wherein the AMANDA label has been inadvertently removed? thanks, J ### Subject: DailySet2 AMFLUSH MAIL REPORT FOR September 13, 2002 *** A TAPE ERROR OCCURRED: [reading label: No space left on device]. ^^ Obscure possibility: tape drive block size is set to something fixed and larger than 32KB. Reason I suggest that is dd, which reads off the label, has a wierd message if its input buffer is too small for the a tape block and overflows. Not certain if it is this message or someother similarly wierd message. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.262412 secs) *** Qmail-Scanner Envelope Details End ***
Re: Tape DDS-3 values
On Fri, Sep 13, 2002 at 10:25:29AM -0400, Jon LaBadie wrote: Is it a real, or theoretical, problem? I.e. has anybody experienced bit errors in a gzip'ed document? For me the incidence is low enough that I don't feel a need to use bzip2 for that extra protection. The value of your data may lead to a different conclusion. I brought this up and it's not theoretical - I've had problems with gzipped tar files coming back off tapes. I definitely have problems with my tape drive but as mentioned, such errors in a tar file would only have caused problems with some files - with the gzipped tar file, you're done for once you hit an error. Regards, Niall O Broin *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 1.182701 secs) *** Qmail-Scanner Envelope Details End ***
Measure and Graph Tape Usage
Is there any way to measure how many bytes where written to the tape every night? I would like to feed the values to MRTG or something, so I can see when I am close to using two tapes per dump. Also, if the data is available, is it the raw uncompressed bytes, or the post-gzipped bytes that are recorded? I would like to see the both, to measure my compression ratios. Thanks group, Jay *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.265007 secs) *** Qmail-Scanner Envelope Details End ***
Re: Dumpcycles vs Runs
On Sat, Sep 14, 2002 at 12:57:15PM -0400, Jason Greenberg wrote: If I have a dumpcycle of 7 days, with 7 runs per cylce, I understand that I will have a full backup every 7 days. So, if that's the case, here are my questions: 1) How many tapes are used for these 7 runs? 7? or just 1? 7 x runtapes (which is the number of tapes used per run) 2) does the tape change after every dumpcycle or every run? After every run - amanda is a backup solution for people who are serious about backing up their data, and that means that you don't put a number of backups one after the other on one tape. 3) I have 15 tapes, and I would like to use 1 tape per week, with 15 weeks of total history. What would the dumpcycle / runspercycle config be? You can't do that, or at least not with the above spec. You could have dumpcycle 7 days and runspercycle 1 but you probably don't want to do that :-) (because you'd only be backing up once per week) With 15 tapes, assuming that you backup on weekdays only, and have sufficient tape capacity, you'll get only three weeks history. Regards, Niall O Broin *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 1.257272 secs) *** Qmail-Scanner Envelope Details End ***
tape error
Anyone seen this tape error message before? Does this indicate a bad tape or a tape wherein the AMANDA label has been inadvertently removed? thanks, J ### Subject: DailySet2 AMFLUSH MAIL REPORT FOR September 13, 2002 *** A TAPE ERROR OCCURRED: [reading label: No space left on device]. ^^ -- *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.267526 secs) *** Qmail-Scanner Envelope Details End ***
Re: Measure and Graph Tape Usage
Jason Greenberg wrote: Is there any way to measure how many bytes where written to the tape every night? I would like to feed the values to MRTG or something, so I can see when I am close to using two tapes per dump. Also, if the data is available, is it the raw uncompressed bytes, or the post-gzipped bytes that are recorded? I would like to see the both, to measure my compression ratios. Thanks group, Jay Yes, that information is available but you will need to be able to parse the email amanda sends you after she completes a run. =G= *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.264672 secs) *** Qmail-Scanner Envelope Details End ***
Dumpcycles vs Runs
You'll have to excuse my newbieness for this one, if you would... If I have a dumpcycle of 7 days, with 7 runs per cylce, I understand that I will have a full backup every 7 days. So, if that's the case, here are my questions: 1) How many tapes are used for these 7 runs? 7? or just 1? 2) does the tape change after every dumpcycle or every run? 3) I have 15 tapes, and I would like to use 1 tape per week, with 15 weeks of total history. What would the dumpcycle / runspercycle config be? Thanks group, Jay *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.263871 secs) *** Qmail-Scanner Envelope Details End ***
RE: tape error
No, actually I think it means it's not rewound (Is this a word? Bah!). Try doing an mt -f /dev/nst0 rewind and then run an amcheck on that tape and see if it's happy. -Original Message- From: John Koenig [mailto:[EMAIL PROTECTED]] Sent: Friday, September 13, 2002 1:56 PM To: [EMAIL PROTECTED] Subject: tape error Anyone seen this tape error message before? Does this indicate a bad tape or a tape wherein the AMANDA label has been inadvertently removed? thanks, J ### Subject: DailySet2 AMFLUSH MAIL REPORT FOR September 13, 2002 *** A TAPE ERROR OCCURRED: [reading label: No space left on device]. ^^ -- *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.265187 secs) *** Qmail-Scanner Envelope Details End ***
Deja vu all over again
What's up with last week's postings getting re-injected into the list? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Deja vu all over again
I thought I was going crazy - thanks for confirming that I am not. -- Sam Nicolary On Wed, 18 Sep 2002, Frank Smith wrote: What's up with last week's postings getting re-injected into the list? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Deja vu all over again
Here's the relevent section of headers: Received: from pwd.reeusda.gov ([192.73.224.125]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g8IImln797017 for [EMAIL PROTECTED]; Wed, 18 Sep 2002 14:48:47 -0400 (EDT) Received: from reeusda.gov - 192.73.224.2 by pwd.reeusda.gov with Microsoft SMTPSVC(5.5.1774.114.11); Wed, 18 Sep 2002 14:46:22 -0400 Received: (qmail 17216 invoked by uid 0); 18 Sep 2002 18:32:14 - Received: from guiness.omniscient.com (64.134.101.78) by maat.reeusda.gov with SMTP; 11 Sep 2002 18:30:49 - -Mitch On Wed, 18 Sep 2002, Frank Smith wrote: What's up with last week's postings getting re-injected into the list? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Deja vu all over again
What's up with last week's postings getting re-injected into the list? I've removed a bunch of queued up messages from last week, blocked the originating site and sent mail mail to their postmasters. In the future, if you see someone doing this, please let [EMAIL PROTECTED] know, and if you could include complete headers to one of the offending messages, that would be even better. -Todd
RE: Deja vu all over again
I am already aware of the problem, have fixed it, and taken care of it. Instead of posting to the whole list, you could have just emailed me about it and I would have taken care of it thank you very much Michael Martinez System Administrator -Original Message- From: Mitch Collinsworth [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 18, 2002 3:09 PM To: Frank Smith Cc: [EMAIL PROTECTED] Subject: Re: Deja vu all over again Here's the relevent section of headers: Received: from pwd.reeusda.gov ([192.73.224.125]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g8IImln797017 for [EMAIL PROTECTED]; Wed, 18 Sep 2002 14:48:47 -0400 (EDT) Received: from reeusda.gov - 192.73.224.2 by pwd.reeusda.gov with Microsoft SMTPSVC(5.5.1774.114.11); Wed, 18 Sep 2002 14:46:22 -0400 Received: (qmail 17216 invoked by uid 0); 18 Sep 2002 18:32:14 - Received: from guiness.omniscient.com (64.134.101.78) by maat.reeusda.gov with SMTP; 11 Sep 2002 18:30:49 - -Mitch On Wed, 18 Sep 2002, Frank Smith wrote: What's up with last week's postings getting re-injected into the list? Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: [Amanda-users] Re: Tape DDS-3 values
we had the same problem, we now store the data uncompressed on the tape. And still get frequent errors. On Fri, Sep 13, 2002 at 06:14:46PM +0100, Niall O Broin wrote: On Fri, Sep 13, 2002 at 10:25:29AM -0400, Jon LaBadie wrote: Is it a real, or theoretical, problem? I.e. has anybody experienced bit errors in a gzip'ed document? For me the incidence is low enough that I don't feel a need to use bzip2 for that extra protection. The value of your data may lead to a different conclusion. I brought this up and it's not theoretical - I've had problems with gzipped tar files coming back off tapes. I definitely have problems with my tape drive but as mentioned, such errors in a tar file would only have caused problems with some files - with the gzipped tar file, you're done for once you hit an error. *** Qmail-Scanner Envelope Details Begin *** X-Qmail-Scanner-Mail-From: [EMAIL PROTECTED] via maat.reeusda.gov X-Qmail-Scanner-Rcpt-To: [EMAIL PROTECTED] X-Qmail-Scanner: 1.12 (hbedv: 2.0.3/vdf=6.14.0.3 Clear:. Processed in 0.53725 secs) *** Qmail-Scanner Envelope Details End ***
Can Amanda put its index on a tape?
Hello everyone. Question: Can Amanda be setup so that it writes a copy of it's indexes to the beginning of each tape? I realize that I can add the filesystem that holds the indexes to my disklist, but then I won't know where on the tape it is. If it were always the first thing after the label I could easily find it in an emergency. Thanks! Anthony Valentine -- UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.
Re: Can Amanda put its index on a tape?
On Wed, Sep 18, 2002 at 02:29:58PM -0800, Anthony Valentine wrote: Question: Can Amanda be setup so that it writes a copy of it's indexes to the beginning of each tape? I realize that I can add the filesystem that holds the indexes to my disklist, but then I won't know where on the tape it is. If it were always the first thing after the label I could easily find it in an emergency. That'd be a nice feature, but then a lot of things about time travel might be nice :-) I don't think it can be done in the general case, because taping will usually have started before the indices would be updated. Of course in the case of an emergency such that you need to get the indices from tape, I suppose having on on the last tape a copy of the indices correct as to the previous tape would be a whole lot better than nothing. What I, and I think many others, do is to copy the indices to a different disk after each daily Amanda run which gives you a little insurance against a disk crash. As I write this it occurs to me that the indices are not so big that it would be unreasonable to also ship them offsite somewhere also, presuming that you have access to such a place. You could even simply email them to youself at a special account on a non-company mailserver. Kindest regards, Niall O Broin
Re: readline termcap libraries?.
On Wed, Sep 18, 2002 at 09:59:48AM -0400, Oleg Svintsitski wrote: Hi Group, Can anyone advise -- which version of readline library should be used?.. GNU site has v4.3, while the amanda docs recommend 2.2, so does that matter?.. Also, should readline use termcap (there is 1.3.1 dated last month or so..) or ncurses?.. I am putting all that together on SPARC Solaris 8 (if that matters..) Your advices will be deeply appreciated. Your Solaris cd's should have come with a companion cd. Use the versions of readline and ncurses that come on that. ncurses incorporates the needed termcap functionality. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
