Tom King wrote:
> Richard B. Gilbert wrote:
> >>> My guess would be that /opt is currently part of /. If this is the
> >>> case:
>
> Yes it was it was staring me in the face too many late nights and too
> much coffee. Sigh simply directory sigh.
>
>
> > Only if you have a disk at target 10 on controller 0 AND that's where
> > you created your new file system AND where you put the files from the
> > existing /opt.
>
> yes to all that works now thanks for the pointers
>
> Tom

Tom; been there, done that. For future reference, one useful way of
determining what file system /opt (or whatever future directory you
wish) is part of would be to do a df -k on /opt. For instance, I have
the same setup on one of our servers; /opt is simply a directory under
root. so a df -k on /opt shows:

# df -k /opt
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/rootvol 4131866 2203902 1886646 54% /

As you can see, the file system is shown at the left, and the directory
it is mountes on is on the right. This tells you that the /opt
directory is not on a file system of its own, but is simply a
sub-directory of /.

Not sure I worded all the above correctly, but hopefully, you get the
gist.

One other area that the above can come in handy is for when you get a
message /opt (or whatever) is full. Checking out the df -k to verify,
can lead you to look in / (for core files, mis-placed temp files,
anythin that shouldn't be there and is taking up space), instead of
simply looking in /opt to free up space.

Hope this was useful...

Joe D.