13 00:24, James D. Freels wrote:
> > I got into debugging mode and discovered why this was happening.
> > Apparently this upgrade, or a recent change in AMANDA, now forces (or by
> > error) the data to be compressed with gzip before going from the client
> > to the server.
, Alexander Jolk wrote:
James D. Freels wrote:
> I am also using the aic7xxx driver also in a vanilla 2.6.14.2 kernel.
You might also want to tell linux-scsi about this problem, I recall
there's been a few aic7xxx related problems lately.
Alex
--
James D. Freels, Ph.D.
O
(FC4), the
server worked correctly with FC2.
It works correctly on FC4 with an old kernel (2.6.10-1.771_FC2smp).
I suspect the scsi driver, which driver are you using, I'm using aic7xxx.
Jean-Louis
On Wed, Nov 16, 2005 at 01:25:26PM -0500, James D. Freels wrote:
> Hello folks ! I have be
to latest kernel might help. Are you
using additional drivers?
Paddy
On 11/16/05, James D. Freels <[EMAIL PROTECTED]> wrote:
Hello folks ! I have been using AMANDA now for several years and find it to be a superb backup tool. I just converted one of
rnel: flags:0x010c mapping:8100080ec238 mapcount:2 count:0
Nov 7 00:12:48 fea8 kernel: Backtrace:
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
On Mon, 2005-11-14 at 15:36 -0500, James D. Freels wrote:
Hello folks ! I have been using AMANDA now for several years and find it to be a superb backup tool. I just converted one of my AMANDA backup servers (fea5) from an Alpha 64-bit machine running Debian/Sarge to a new AMD64 64-bit
I put the cartridge in backwards (which looks like forwards for traditional tape drives). I will always have to remember this !!!
Now in the process of taking the unit apart to take out the cartridge.
On Thu, 2005-02-24 at 09:17 -0500, James D. Freels wrote:
The Exabyte lack of timely
This request did not seem to go through. Try again.
On Thu, 2005-02-24 at 09:17 -0500, James D. Freels wrote:
The Exabyte lack of timely tech support may be hurting them. I get better help through this forum which may discourage people from purchasing from Exabyte.
I have
The Exabyte lack of timely tech support may be hurting them. I get better help through this forum which may discourage people from purchasing from Exabyte.
I have great success with the first round of 10 tapes with the autoloader. Each day, a new tape was loaded and the AMANDA backup perform
>From the packet-loader manual the following timing information is available:
Autoloader power-on sequence time (power-on to ready status):
53 seconds when autoloader contains 10 cartridges with bar code labels
105 seconds when autoloader contains 10 cartridges without bar code labels
Cartri
amtape commands in a row to get it to work.
I will post back here if I figure something out. At least I have a workable backup system running now with the new packet loader and AMANDA.
On Tue, 2005-02-15 at 13:00 -0500, James D. Freels wrote:
Recall I had a problem getting this device to w
max_drive_wait=240
initial_poll_delay=10
On Tue, 2005-02-15 at 13:00 -0500, James D. Freels wrote:
Recall I had a problem getting this device to work properly when it failed to write to the tape. This problem was correct by a new and separate scsi card dedicated to the packet loader.
When I
I think I missed something here. The response below, where did it come from ? (about the sleep delays, etc.)
On Tue, 2005-02-15 at 13:56 -0500, Eric Siegerman wrote:
On Tue, Feb 15, 2005 at 01:40:44PM -0500, Jon LaBadie wrote:
> If I issue another command to the drive before it is really
>
Recall I had a problem getting this device to work properly when it failed to write to the tape. This problem was correct by a new and separate scsi card dedicated to the packet loader.
When I use the older ncr53c7xx driver in Linux, it works OK, but does not automatically reload tapes. Here
, James D. Freels wrote:
> I have the new scsi card (an inexpensive LSILogic LSIU80ALVDB) that
> fixes the problems I was having. So, the Exabyte tech support was
> correct and the great advice I got herein this mailing list also said
> "get a separate scsi card" !
...
>
&
dating the driver to the newer sym53c8xx-2 and also experimenting with the "amtape" and "mtx" commands to manipulate this new autoloader. I may be asking some additional good questions if I have any more problems. Thanks for all the great help !
On Mon, 2005-02-07 at 16:2
I am near positive I did not fry anything since everything is working correctly except a sustained write to the tape. If anything were damages, I would expect nothing to work at all. I have ordered the new scsi card and I will report back in to this thread when I find the results. I am also
On Fri, 2005-02-04 at 14:36 -0500, Gene Heskett wrote:
The cable IS completely disconnected from the scsi card and the cd-rom IS the only
device on that cable. This is what is so strange. I did this test thinking it might
fix my problem since I am down from 2-internal, 1-external on the sam
to buy for this Alpha machine ?
On Fri, 2005-02-04 at 11:04 -0500, Gene Heskett wrote:
On Friday 04 February 2005 10:12, Geert Uytterhoeven wrote:
>On Fri, 4 Feb 2005, James D. Freels wrote:
>> The tape drive is within the VXA-2 Packet-Loader 1U rack mount.
>> It is connected
wide cable plugged to the rest
of the devices. Come to think of it, the 50-pin is just out there; no termination. Hmmm... let's try
that next.
On Fri, 2005-02-04 at 16:12 +0100, Geert Uytterhoeven wrote:
On Fri, 4 Feb 2005, James D. Freels wrote:
> The tape drive is within the VXA-2 Packe
+0100, Geert Uytterhoeven wrote:
On Fri, 4 Feb 2005, James D. Freels wrote:
> When you say "cabling" issues, does this include a separate scsi card
> specific for the
> tape drive ? I think my cable connections are good.
The cable may be too long, or not properly terminated.
>
is giving me problems at present. It is able to label the tapes,
but not write a larger data set to the tape.
On Thu, 2005-02-03 at 23:17 -0500, Gene Heskett wrote:
On Thursday 03 February 2005 17:49, James D. Freels wrote:
>No. It should be still Alpha compatible. The problem is that the
D. Freels wrote:
> Here is what [drive vendor's Tech Support said] is needed:
>
> 1) need a separate scsi chain; they said I already have too many scsi
> devices on this chain to make it reliable.
See recent threads re. SCSI cables, bus lengths, etc. (Recent ==
last month or tw
I am getting scsi sense errors using the new drive about 1-2 minutes after an amdump or amflush starts. Below are the reommendations from Exabyte tech support to fix it.
Any comments ?
Forwarded Message
From: James D. Freels <[EMAIL PROTECTED]>
Reply-To: [EMAIL PRO
I need to properly create an /etc/stinit.def file for the Exabyte VXA-2 tape drive for purposes of initializing the tape drive using mt-st prior to usage by AMANDA. Currently, AMANDA cannot write to the tape drive since it is initialized incorrectly. A first attempt at the initialization loo
2005-02-02 at 13:38 -0500, James D. Freels wrote:
I finally have time to work on this new tape drive (vxa-2-packet-loader). I am having difficulty since this is my first autoload-type system. I have amanda running fine for years with a single manually-loaded tape drive. Here are a few
I finally have time to work on this new tape drive (vxa-2-packet-loader). I am having difficulty since this is my first autoload-type system. I have amanda running fine for years with a single manually-loaded tape drive. Here are a few questions:
1) it appears that I must get mtx to respond
Exabyte sells a new and relatively inexpensive auto loader device.
Called the "VXA-2 PacketLoader 1x10 1U Autoloader". I have no
experience with autoloaders and AMANDA as I have been using AMANDA now
for years with manually-loaded tapes. I do know from reading the
AMANDA docks that some autoload
it's own semantics when reading blocks from tape.
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
the clean tapes would recognize
the label. The label is not recognized after the amflush.
The tape drive has compression on according to the tapetype. Could this
be the cause somehow ?
On Fri, 2004-04-30 at 11:02, Paul Bijnens wrote:
> James D. Freels wrote:
>
> > OK. Stranger by
I am writing to the non-rewinding device as always, /dev/nts0.
If I changed the blocksize, how would I have done so ? If I have the
incorrect tapetype, will this do it ? How can I correct the blocksizes,
etc. ?
On Fri, 2004-04-30 at 10:56, Paul Bijnens wrote:
> James D. Freels wr
"mt rewind", turn around and issue another amcheck fea, and the tape has
an error on it. So, the amflush and/or amdump process is writing
something to the tape that causes it to not be usable after that point.
Is this sounding like a scsi error or some type ?
On Fri, 2004-04-30 at 10
make sure it was not that. Just yesterday I labeled 25 tapes
!!
On Fri, 2004-04-30 at 10:07, James D. Freels wrote:
> Hello Amanda-Users !
>
> I have duplicated my previous amanda backup setup from an existing
> machine to a new machine. The new machine has a different tape dri
plenty of memory, etc.
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
34 matches
Mail list logo
