On Fri, Jul 25, 2003 at 02:46:31PM -0700, Chris Miller wrote:
>
> Hello,
> we recently added some Linux servers to our mix of *BSD servers.
> The server is running FreeBSD 4.7p10 with amanda 2.4.4 (from /usr/ports,
> looks like it's the base release, i.e. not the latest) and the clients are
> running RedHat Linux 7.3 with amanda-client-2.4.2p2-7. When running
> amcheck, it complains that it can't find just one of the disks, yet all
> are defined the same (i.e. sd1a, sd3a, etc). Here's the error :
>
> Amanda Backup Client Hosts Check
> --------------------------------
> ERROR: <hostname>: [could not access sda3 (sda3): No such file or directory]
>
> If I change the disk name on sd3a to include the full path, everything is
> fine :
>
> host sda1 comp-root-index
> host /dev/sda3 comp-root-index
> host sdb1 comp-user-index
> host md0 comp-user-index
>
> I don't see anything special about sd3a to cause this :
>
> [root@host /]# df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/sda3 14927248 1122460 13046520 8% /
> /dev/sda1 497829 17867 454260 4% /boot
> /dev/sdb1 17496684 136304 16471588 1% /var
> /dev/md0 34993280 47604 33168096 1% /home
> none 515632 0 515632 0% /dev/shm
>
> All other disks work fine without the full path, dumps worked fine last
> night with the above config. I searched the archives and couldn't find
> mention of this, and I've experienced the same problem on two identical
> machines. Ideas?
There is probably something in Linux like Solaris' /etc/vfstab.
I think amanda uses this to map simple disk names to full paths
and directories to mount points. Perhaps sda3 is not listed there.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
