Re: debugging chg-scsi
2004-11-05 08:51:22
Hi again,
i would bet it is a permision-problem, but i have no experience with
autogenerated device-nodes like yours.
Erik Anderson schrieb:
On Thu, 4 Nov 2004 14:51:54 -0600, Erik Anderson <erikerik AT gmail DOT com>
wrote:
Okay - here's the deal. My /dev/sg* entries are symlins. They're
pointing as follows:
/dev/sg0 -> scsi/host0/bus0/target0/lun0/generic
/dev/sg1 -> scsi/host1/bus0/target1/lun0/generic
/dev/sg2 -> scsi/host1/bus0/target3/lun0/generic
The permissions on the symlinks are 555, but the permissions on the
Huh????
a symlink with permisions other than 0777 ???? never have been able to
produce such a beast. But maybe your filesystem supports other features
then my ext2/3 .
>>targets are 660, which is correct.
and what is the owner/group set to?
is your amanda-user a member of that group?
do all files mentioned in your chg-scsi.conf exist and
are they writeable for the amanda-user?
Christoph
Sorry - hit the send button prematurely there.
If I put the full path to the device into chg-scsi.conf instead of the
symline, I get this:
amanda@lpdlnx00 LPD $ amcheck LPD
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps/amanda: 36514756 KB disk space available, that's plenty
amcheck-server: could not get changer info: open:
/dev/scsi/host1/bus0/target1/lun0/generic: Success
Amanda Backup Client Hosts Check
--------------------------------
Client check: 0 hosts checked in 0.001 seconds, 0 problems found
(brought to you by Amanda 2.4.4p2)
With the full path to the scsi devices in chg-scsi.conf, amcheck
executes in about a quarter second, so that doesn't seem right.
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: debugging chg-scsi, (continued)
- Re: debugging chg-scsi, Christoph Scheeder
- Re: debugging chg-scsi, Erik Anderson
- Re: debugging chg-scsi, Erik Anderson
- Re: debugging chg-scsi,
Christoph Scheeder <=
- Re: debugging chg-scsi, Frank Smith
- Re: debugging chg-scsi, Erik Anderson
- Re: debugging chg-scsi, Gene Heskett
- Re: debugging chg-scsi, Eric Schnoebelen
- Re: debugging chg-scsi, Gene Heskett
- Re: debugging chg-scsi, Erik Anderson
- Re: debugging chg-scsi, Gene Heskett
- Re: debugging chg-scsi, Stephen Carville
Re: debugging chg-scsi, Jon LaBadie
|
|
|