Answer - Mount points are not always inaccessible or read only after a ADVfs panic.
Thanks to all
>From Chris Ford:
Depending on the type and severity of the ADVFs Panic, it is very possible that the mount point is still mounted and accessible. On 4.x systems it was possible to drop a mount point, and in turn a box just by filling the file system. In 5.1 I have lost drives, raid sets, and LSM mirror sets which caused ADVFs panics but the file systems were all still available. Hope this helps...
>From Blake Berhl :
run "verify -a" (mounted file system) or "verify -f" (unmounted )
There's a really good book by Steven Hancock, Digital Press. "Tru64 UNIX File System Administration Handbook" ISBN 1-55558-227-3
Original Message -----
From: redhatcat
To: tru64-unix-managers_at_ornl.gov
Sent: Wednesday, April 03, 2002 10:31 PM
Subject: Q. ADVFS panic on TRU64 V5.1
ADVFS on Tru64 V5.1
Q. Does an ADVfs Panic necessarily put a mount point in an in-accessable state ?
Under V4.x mount points seemed to become inaccessible and you had to re-mount or reboot.
I had a ADVfs panic on V5.1 ( I was told no one intervened ) but when I checked ; all files were readable and I could write to the mount point. Is this possible OR did someone intervene ?
This is on a SAN ( if that makes a difference ).
TIA - rhc
Received on Fri Apr 05 2002 - 23:16:31 NZST