On Tuesday, September 28, 2010 09:42:43 pm Dustin J. Mitchell did opine:

> On Tue, Sep 28, 2010 at 6:26 PM, Gene Heskett <[email protected]> 
wrote:
> > I now see a 'data' link to slot 5, I nuked that 2 days ago because
> > nothing was paying an attention to it, and neither amcheck nor amdump
> > was updating it, and the loss causes no errors, none, nada, zip.  My
> > helper script no longer pays any attention to it either.
> 
> That's really weird.  I can't replicate this behavior at all.  Having
> reviewed the code, chg-disk actually looks at what the 'data' symlink
> is pointing to in order to determine the "current" slot.
> 
> In particular, I don't see why amtape would set the symlink, but
> amcheck and amdump would not.  Reasons I can think of off the top of
> my head:
>  - permissions problems
Everything involved is either amanda:amanda or amanda:disk
>  - wrapper scripts?

I only read what amanda sets in those, no writes.

>  - multiple copies of Amanda installed?

Yeah, about the last 30 snapshots, but all the working links are to 3457 
stuff.  I nuked the rest which didn't results in any broken links, and 
anything in those dirs that was not dated the 27th when I installed 3457.

>  - voodoo?

I thought of that, but I'm not very good at that sort of thing. ;-)
 
> Can you set up a smaller config without using your wrapper script and
> with a fresh set of vtapes and a simple DLE (/boot or something like
> that), and see how amtape and amcheck behave?  Don't run amdump..
> 
> Dustin

That took about an hour and a whole bunch of detail edits in the copied 
amanda.conf to /usr/local/etc/amanda/test/amanda.conf, plus some re-writing 
of my mkvtapes-test test script, but here is what I wind up with.
[ama...@coyote GenesAmandaHelper-0.6]$ amtape test show
amtape: scanning all 10 slots in changer:
slot   1: date X              label test-1
slot   2: date X              label test-2
slot   3: date X              label test-3
slot   4: date X              label test-4
slot   5: date X              label test-5
slot   6: date X              label test-6
slot   7: date X              label test-7
slot   8: date X              label test-8
slot   9: date X              label test-9
slot  10: date X              label test-10

and 
[ama...@coyote GenesAmandaHelper-0.6]$ amcheck test
Amanda Tape Server Host Check
-----------------------------
Holding disk /usr/amandatest: 620937216 kB disk space available, using 
620425216 kB
slot 1: volume 'test-1'
Will write to volume 'test-1' in slot 1.
NOTE: skipping tape-writable test
NOTE: conf info dir /usr/local/var/amanda/test/curinfo does not exist
NOTE: it will be created on the next run.
NOTE: index dir /usr/local/var/amanda/test/index does not exist
NOTE: it will be created on the next run.
Server check took 0.187 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 6.018 seconds.  0 problems found.

(brought to you by Amanda 3.2.0alpha.svn.3457)

[ama...@coyote GenesAmandaHelper-0.6]$ ls -l /amandatapes/test
total 44
lrwxrwxrwx 1 amanda amanda    5 2010-09-28 21:40 data -> slot1/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot1/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot10/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot2/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot3/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot4/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot5/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot6/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot7/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot8/
drwxr-x--- 2 amanda amanda 4096 2010-09-28 21:40 slot9/
-rw------- 1 amanda amanda  131 2010-09-28 21:40 state

Now, I suspect I can nuke that 'data' link without bothering a thing, but 
haven't.  My mkvtapes-test script uses it to display the contents of 'data' 
as the individual vtape is created.  There amlabel correctly modifies the 
data link as it labels, so in order for it to order the generated tapelist, 
the for n in 10 9 8 7 6 5 4 3 2 1 reverses the order so it winds up with 
data pointed at slot-1 and the usage pattern is then in 1 2 3 etc order.

I have this setup in parallel, with a separate holding disk, a separate  
/usr/local/var/amanda/test for a database location.  Theoretically I should 
be able to run it without interaction with the normal 'Daily' setup.  
Theoretically, usually Murphy proves he is alive and well.

The one dle disklist:
coyote  /boot                   coyote-tar      1       local

And I still don't have a tapedev defined.  What should that be for a vtape 
setup running to /amandatapes/test/slot-* as the vtape?

Anyway, its setup, and awaiting orders Cap'n.  Next?

 

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Prediction is very difficult, especially of the future.
- Niels Bohr

Reply via email to