Thanks to Dr. Blinn, Pat O'Brien, Olle Eriksson, Bob Full, Olsin McGuiness,
and everyone else who replied to my message. Many of you were right on the
money, the kernel was not configured to use AdvFS, even though AdvFS was
installed on the system.
Following the advice of numerous sysadmins, I went into /sys/conf, opened up
the kernel configuration file, and added 'options MSFS' (without the
hashes). Then, I rebuilt the kernel using the modified file and rebooted
the system.
Worked like a charm! AdvFS happily created my filedomain for me after the
reboot. Thanks again to all who replied. The original problem is included
below for reference.
Pearce Statts
GE Fanuc Automation
Admins,
I've got an Alphaserver 4100 running Tru64 4.0G that is having problems when
trying to use AdvFS to create a new file domain. From the command line,
here is what I am typing:
# mkfdmn /dev/rz10c usr_domain
And here is what I get back:
mkfdmn: domain init error E_ADVFS_NOT_INSTALLED (-1108)
mkfdmn: can't create new domain 'usr_domain'
To verify that the disk itself wasn't causing the problem, I zeroed out the
disklabel for rz10c, and then reinitialized it with this:
# disklabel -rw -t advfs /dev/rrz10c rz1db
No change.
I'm at a loss to explain why the system is complaining about AdvFS not being
installed. The license PAK for the AdvFS utilities is in place, and all of
the neccessary software subsets have been installed, both from the primary
OS installation disk and from associated products vol. 2. In addition,
everything -seems- to be OK. I can bring up dtadvfs without any problems
and it works fine, addvol, mkfset, mkfdmn, etc. all respond to input. The
advfsd daemon comes up at boot and runs without any errors...
There are two things I can think of. First, this system is a test-bed for
moving our production environment from Tru64 4.0D to 5.1. This system is at
the 4.0G 'intermediate' stage. The license PAK for AdvFS was installed when
the system was at 4.0D, but I didn't install the actual AdvFS subsets until
I got to 4.0G, because I knew I would just have to reinstall them after I
upgraded. Not sure if installing the PAK at one OS rev and then installing
the subsets after an upgrade would cause this problem. In addition, when I
went back through the subsets to make sure I hadn't missed something, I
noticed that I had failed to install 'AdvFS Kernel Objects'
(OSFADVFSBINOBJECT445). I overlooked this because it was in the 'software
development' department, and I assumed I wouldn't need it, since this
machine won't be used for development. Just to be sure, I went back and
installed the subset, but it didn't help.
Like I said, everything -looks- right, and AdvFS is indeed working on this
system, just refusing to create filedomains for me, so it's somewhat useless
at the moment. Does anyone have any advice as to where I should look for
the source of the problem next?
Thanks,
Pearce Statts
GE Fanuc Automation
pearce.statts_at_gefanuc.com
> Pearce Statts
> Information Systems Engineer
> GE Fanuc Automation, N.A.
> P.O. Box 8106
> Charlottesville, VA 22906
> Phone: 277-5937 Fax: 277-5097
>
>
Received on Fri Feb 15 2002 - 19:12:06 NZDT