On Friday 18 July 2003 11:30, Byarlay, Wayne A. wrote:
>I tried the following things, and I still get the problem of "Not a
> device file".
>
>>(Jon LaBadie wrote:) If I understand changer-status, your comment
>> "created
>
>by wab" should not have been created or touched in any way by wab.
>
>Well, I thought that I shouldn't be touching changer-status either,
> but every time I went to do an "amlabel" (Which I thought would be
> a first step, but I'll try ammt & amtape like you suggested), it
> kept prompting me, saying stuff was missing from the
> changer-status! I think possibly I am referencing this file in an
> incorrect location?
>
>>(Jon LaBadie wrote:) You have two statefile definitions, one in
>
>changer.conf and another
>in changer-status.
>
>Gah! *fixed*. I am using the one in /var/lib/amanda/DailyNAS1.
>
>>(Paul Bijnens wrote:)Just verifying: you are using amanda 2.4.3 or
>> later?
>
>NO I am using 2.4.1p1.
>
I won't go so far as to say it incompatible because it shouldn't be.
But there has been several million acre feet of water under the
bridge since that was new.
>One potential problem was maybe fixed: I did a manual check of the
> directory I'm trying to use to back up to... and my user "backup"
> did NOT have permission in the "data" directory! However, after
> doing this and attempting to do amlabel, it still screwed up. So at
> least, I know that it's not that.
>
>I sincerely thank you all for your help and patience.
>
>p.s. I still can't figure out why I can't get my amanda.conf file to
> open... it'll copy to the NAS (which has SMB installed as well) and
> all my other config files I can open w/notepad & copy/paste into
> e-mail. Except for amanda.conf. Root is supposed to have RW on this
> sucker, but I can view the directory, delete the file, RENAME the
> file... but I cannot view its contents or copy it to my desktop!
> Argh! Confusing permissions thing there; ancillary to this problem.
>
>Wayne
First, all amanda related files should be owned by whomever
(unpriviledged user) is actually running amanda. Most will make that
ownership read amanda:disk, where amanda can be most any
unpriviledged user, and disk can be anybody with systemwide perms,
some systems could use 'sys' or system in place of disk.
So as root, one possible fix might be to cd into the parent directory
of any of the amanda stuff, and do a "chown -R 'youruser:yourdisk'
amanda".
Just to keep the system from biteing you, you should become this user
when editing amanda.conf, or any of the other config related files,
I've had linux very occasionally convert ownership to root:root,
which of course brings everything to a halt, with the screeching
usually being done by the root perpetrator :)
All this becomes automatic if you build from tarballs, following the
instructions in it.
>-----Original Message-----
From: Jon LaBadie [mailto:jon AT jgcomp DOT com]
>Sent: Thursday, July 17, 2003 4:21 PM
>To: 'amanda-users AT amanda DOT org'
>Subject: Re: Tapeless Backup using chg-multi
>
>On Thu, Jul 17, 2003 at 03:26:38PM -0500, Byarlay, Wayne A. wrote:
>> I am attempting to use AMANDA to write to Disk instead of Tape.
>>
>> I have followed the directions in the archives to the best of my
>
>ability...
>
>> but I'm still running into an error.
>>
>> I try to use amlabel (/usr/sbin/amlabel -f DailyNAS1 DailyNAS01
>> slot 1)to prepare the directories, but I keep getting an error
>> that says "device
>
>could
>
>> not load slot "current": not a device file."
>>
>> Very similar error if I omit the slot 1.
>>
>> If I CD into this dir, I can create/delete files/directories so
>> it's not a permissions problem (even though the path is a NFS
>> mounted remote NAS.)
>>
>>
>> ------------------------
>> Contents of amanda.conf:
>> uh, having problems getting this one... let me know if you need to
>> see something
>>
>>
>> ------------------------
>> Contents of changer.conf:
>> multieject 0
>> gravity 0
>> needeject 0
>> ejectdelay 0
>> statefile /etc/amanda/DailyNAS1/changer-status
>> firstslot 1
>> lastslot 1
>> slot 1 file:/test/amanda/slot1 #verified to be existing. this path
>
>contains
>
>> a folder called "data".
>>
>> ----------------------------
>> contents of changer-status:
>> #created by wab 7-16-03
>> multieject 0
>> gravity 0
>> needeject 0
>> ejectdelay 0
>> firstslot 1
>> lastslot 1
>> curslot 1
>> curloaded 1
>> slot 1 file:/test/amanda/slot1
>> statefile /var/lib/amanda/DailyNAS1/statefile
>
>I presume you are using chg-multi as your changer type in
> amanda.conf.
>
>Couple of comments,
>You have two statefile definitions, one in changer.conf and another
>in changer-status.
>
>If I understand changer-status, your comment "created by wab" should
>not have been created or touched in any way by wab. Mine has much
>less info;
>
> # multi-changer state cache: DO NOT EDIT!
> curslot 4
> curloaded 1
>
>Your changer.conf file seems similar to mine:
>
> multieject 0
> gravity 0
> needeject 0
> ejectdelay 0
> posteject 0
> statefile /usr/local/etc/amanda/FT/changer-status
> firstslot 1
> lastslot 10
> slot 1 file:/w2/FileDrive/FTape-01
> slot 2 file:/w2/FileDrive/FTape-02
> ...
> slot 9 file:/w2/FileDrive/FTape-09
> slot 10 file:/w2/FileDrive/FTape-10
>
>
>Can you get reasonable results from ammt and amtape using
>your setup? That should be a first step.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 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.
|
