"John R. Jackson" wrote:
amcheck give an error, so does amdump
I figured that. Sheesh!
The question is, what was the error message, i.e. what **exactly** did
it say? Without that information, nobody is going to be able to guess
what was wrong.
That was the exact error msg from amcheck:
ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6
(/dev/dsk/c0t1d0s6): No such file or directory]
* I put /dev/dsk/c0t1d0s6 just to test if it will find the device since
it failed on the name.
It is the same as disc1
ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such
file or directory]
ERROR: myserver.mydomain.com: [can not access /disc1 (/disc1): No such
file or directory]
* disc1 2 are two additional disks, the strange thing is that I have no
problem with the system disk.
/dev/dsk/c0t1d0s6 is /disc1
OK, then what do you get for these commands:
df -k /disc1
ls -ld /disc1
ls -lLd /disc1
ls -l /dev/dsk/c0t1d0s6
ls -lL /dev/dsk/c0t1d0s6
ls -l /dev/rdsk/c0t1d0s6
ls -lL /dev/rdsk/c0t1d0s6
grep /disc1 /etc/vfstab
yes, but amanda still can find it.
Then run these commands and post the results:
df -k /disc2
bash-2.03# df -k /disk1
df: (/disk1) not a block device, directory or mounted resource
ls -ld /disc2
bash-2.03# ls -ld /disc2
drwxr-xr-x 8 root root 512 Apr 4 16:46 /disc2
ls -lLd /disc2
bash-2.03# ls -lLd /disc2
drwxr-xr-x 8 root root 512 Apr 4 16:46 /disc2
grep /disc2 /etc/vfstab
bash-2.03# grep /disc2 /etc/vfstab
/dev/dsk/c0t2d0s6 /dev/dsk/c0t2d0s6 /disc2 ufs 1
yes -
Tal Ovadia
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
--
Tal Ovadia
Jalan Network Services Inc.
Phone: (818)-262-3895
---
Why Oh Why didn't I take the Blue Pill...
