"Jason Clark" [EMAIL PROTECTED] writes:
Well, I've looked through the archives and it appears that some
people are having success with this driver. I am not one of them.
I'm currently running redhat 6.2 with a 2.2.16 kernel. I can get
the drive to work with the ide-tape module patched
Hi all,
amdump appears to work but I don't believe any files are being written to
tape, extracting from the tape with a dd gets only the header.
amcheck runs with no errors.
The warning/errors in the amdump.1 and log.20010404.1 are:
WARNING: got empty schedule from planner
dumper: could not
Hi,
I'm using SuSE 7.0, Kernel 2.2.16 with no osst-driver - only aic7xxx, an
Onstream ADR50i and I've got exactly the same problem.
Writing to a 25GB-Tape will work fine - but when attempting to write data
back, there seems to be a point/block (until ~1,2GB) where all readings
fail.
So changing
On Apr 3, 2001, David Lloyd [EMAIL PROTECTED] wrote:
Again: THIS IS NOT AMANDA'S FAULT! IT IS SMBCLIENT'S FAULT!
You obviously cannot understand what I am saying, or you have not
followed this thread. If you cannot understand English I will have this
translated into any other language
Hi all,
I thought I'd repost the question with more info:
amdump appears to work but I don't believe any files are being written to
tape, extracting from the tape with a dd gets only the header.
amcheck runs with no errors.
The warning/errors in the amdump.1 and log.20010404.1 are:
WARNING:
On Tue, 27 Mar 2001, Craig Dewick wrote:
Will try the 'sst' driver out and report on it's performance after I have
some sleep! 8-)
Well, I've tried the 'sst' driver and it works only slightly better than
the 'sgen' driver. With the 'sst' driver I can send as many 'mtx inquiry'
commands as I
Hi Folks ..
I am getting the below error when I run amdump , amcheck has no complains. I
tried changing the permission , does not help
Dr.Prab
These dumps were to tape Enki-03.
The next tape Amanda expects to use is: Enki-04.
FAILURE AND STRANGE DUMP SUMMARY:
cream c0t0d0s0 lev 0
Ok, I think finally understand what Marty is trying to say. Marty, there
are many people on this list who have been using samba for years and
understand it very well and how it interacts with amanda, and if we
couldn't understand the gist of your initial question, don't blame our
lack of
My last message should have been directed to David Lloyd, not Marty
Shannon. Sorry Marty!
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster
Hi,
When running amdump, it does nothing after completing the sendsize.
It is still running, but not consuming cpu nor disk nor net.
How may I find out what's going on?
on /usr/local/var/amanda/config/{amdump,log} I just can't find
any useful information.
Thank you very much,
Gonzalo Arana
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
How may I find out what's going on?
amstatus
--
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-Unicamp
On Apr 4, 2001, "Dr.Prabhakar Ganapathy" [EMAIL PROTECTED] wrote:
/export/home/enki/index/cream/c0t0d0s0/20010403_0.gz.tmp: Permission denied]
It means the Amanda server doesn't have permission to create index
files, so you won't be able to use amrecover.
--
Alexandre Oliva Enjoy
Alexandre Oliva wrote:
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
It says 'waiting for dump' on all hosts/directories.
All of them? What is the reason it claims for being idle?
Where may I see a reason? on the amstatus output?
It began to work right now (?)
I still
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
Where may I see a reason? on the amstatus output?
Yep. At the end of the report, it was why each dumper is idle; before
that, it prints the main reason why the whole process is idle, if it
is.
--
Alexandre Oliva Enjoy Guarana', see
Alexandre Oliva wrote:
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
Where may I see a reason? on the amstatus output?
Yep. At the end of the report, it was why each dumper is idle; before
that, it prints the main reason why the whole process is idle, if it
is.
Sorry, but
Hi folks,
Both amanda:sendsize and smbclient are OK, it is the interaction that is the
problem.
This started with my question re: read_socket_with_timeout errors
in sendsize.debug. The error is generated from lib/util_sock.c in
samba code. From the logs smbclient is noting a failed open to
Alexandre Oliva wrote:
On Apr 4, 2001, Gonzalo Arana [EMAIL PROTECTED] wrote:
dumping to tape : 0 0k ( 0.00%)
dumping : 00k0k ( 0.00%) ( 0.00%)
all dumpers active
Hmm... This is very odd. What is `inparallel' set to, in
Todd!
Marty says his samba setup works, but because of the fallback from wins to
broadcast the lookup takes longer than amanda is willing to wait. Amanda
times out and as far as amanda is concerned, smbclient failed. I'm not
even sure what the implications of this are or how to make it
On Wed, 4 Apr 2001, Christopher Linn wrote:
are you using gcc or SUNWspro cc?
gcc. It's the only compiler I have, since I'm not about to fork out money
for a commercial compiler which is less capable than the robust FSF
compiler. 8-)
if you are running a 64 bit kernel, then you must build
Any thoughts before I give up and just use dump.?
Start by looking at the debug files in /tmp/amanda. In particular,
sendsize*debug and sendbackup*debug.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
I have configured the system so that amcheck is happy, but amdump
reports disk is offline.
I have set the device permissions like so:
brw-r root system /dev/vol/rootvol (logical volume)
Is your Amanda user (the one inetd/xinetd runs amandad as) in group
"system"?
What's in
I tried changing the permission , does not help
What did you change the permissions on? What did you change them to?
What is your Amanda user (the one you run amdump as)?
I'm a little surprised amcheck did not whine. I thought I had put in
code in 2.4.2 to look for this type of problem.
On Apr 4, 2001, Hurf Sheldon [EMAIL PROTECTED] wrote:
Sendsize has noted the socket open failure and declared "session
setup failed: code 0"; since the smbclient process hasn't died yet,
sendsize continues to log information from the smbclient it spawned.
And it keeps looking for the size
On Apr 3, 2001, "Dave Hecht" [EMAIL PROTECTED] wrote:
I would like to use "dd" , or some similar tool to make exact images
of a drive as a full backup, rather than dump or tar. [...] Can
Amanda be modified to do this?
Yep. That's the kind of thing you should be able to do with the
DUMPER
Brand new build of amanda 2.4.2p2
server config build:
/configure --with-gnutar=/usr/local/bin/tar --with-portrange=900,950
--with-udpportrange=900,950 (etc)
client config build:
./configure --with-gtar=/usr/local/bin/gtar --without-server
--with-portrange=900,950 --with-udpportrange=900,950
Hey,
Yeah I had called tech support on that particular reason and they said
that premature EOTs were cause by the self cleaning engaging during middle
of the dump..
I supposedly have a .i file that removes the autocleaning ability and that
you'll hav to manually clean the tapes.
Tano
On Wed,
Hi,
Tanniel Simonian wrote:
Hey,
Yeah I had called tech support on that particular reason and they said
that premature EOTs were cause by the self cleaning engaging during middle
of the dump..
I supposedly have a .i file that removes the autocleaning ability and that
you'll hav to
I have the same problem, but I doubt anyone will answer in the amanda forum,
since I have asked about this issue before. Since it an mtx issue, I guess
there's a different forum to discuss this. But I will post my message again...
I have a SUN Enterprise 3500 with SunOS 5.7, a differential
28 matches
Mail list logo
