vxfs mount: mount option(s) incompatible with file system /dev/vx/dsk/datadg/dg_oracle

[Syed Irfan]

Could anyone please help me here. I am new to SUN OS and I want to learn about this error message since each time this occurs, I have make multiple calls and engage differnt people to fix it. If there was something I could learn about mounting filesystems which can help me troubleshoot this issue, that would great.
I executed the command "mount -F vxfs/oracle"
Thanks
Irfan

[Deoncia Grayson_1]

have you take a look at how its set up in in your /etc/dfstab??? Is it really a vxfs file system???

did you do just a regular mount?
mount /oracle

[Bill Hassell]

Although this is the HP-UX forum, /etc/fstab is the most common file used to specify mount option automatically. Do this:

grep oracle /etc/fstab

There should be options listed which will be used with the mount command. If the filesystem is not vxfs, then using -F vxfs will fail. Or one of more of the options listed for this volume is not correct for the filesystem and/or volume manager. You'll need to correct the options in fstab.

You can start troubleshooting by commenting the line with a # in frontr of the line in fstab, then use mount by specifying the source and destination only. If that works OK, you'll need to investigate the options that are present in fstab to determine which one(s) are required and which are not compatible. For insatnce, if this fstab was copied from another system, some of the options may refer to optional products that are not installed. The man page for mounting vxfs will help.

[Patrice Le Guyader]

Hi Syed,

It seems that you file system is a vxvm fs (volume manager). The standard on solaris is SDS (Solaris Disk Suite) and is in UFS format. For your problem you should look to the mount options in /etc/vfstab. Verify if you have mount option not set for largefiles and your FS is in this mode.

try this :
mount -F vxfs -o delaylog,largefiles /dev/vx/dsk/datadg/dg_oracle /mount_point

Otherwise some commands :
To list imported volume group :
vxdg list
To display detailed information on volumes :
vxprint -Ath
To administrate volume and volumes groups :
vxdiskadm
To launch Administration GUI :
vmsa &

Hope this help
Kenavo
Pat

[Syed Irfan]

Hello people.
Thanks for your response.

Deoncia :
It is a "vxfs" file system. I checked the vfstab file. I also tried the regular "mount /oracle".

Bill :
The thing is, this file was copied from other systems. Like I said before, its a vxfs file system and the vfstab has the information regarding the filesystem.

Patrice:
Yeah you are right, I forgot to mention. The file system is a vxvm fs (volume manager). I mounted the /etc/vfstab. Did you want me to check if the option has the "largefile" option in there or not? cause its there. The filesystem has largefile option turned on.

Anyway, just as an aside, I read some more on it and found that sometimes this issue comes up with the "quickIO".

So tried this
mount -F vxfs -o noqio /oracle

since my fs is not in qio mode. And voila this worked!!! Now what I would like to know is, am I to expect some issues due to this?

Once again thanks for your responses.

Irfan

[Alzhy]

It appears your filesystem came from an advanced Veritas filesystem installation -- which required QuickIO.

1.) How was it copied to the server in question?

2.) Can you post the /etc/vfstab entry for the filesystem(s) in its original home?

3. Was the /etc/fstab entry simply copied from the original server?

You may have problems with the filesystem later on if :

a.) The files were simply copied (dumpt/restored or via cpio or tape) since it would h ave maintained the links to the .dot files that actually hold the data.

b.) If you do not have Database Edition License (which makes possible QuickIO) - then those filesystems need to be UnQuikIO'ed before being used.

VxFS QuickIO (it is the same on HP-UX and Solaris, etc.) have the following entries in the filesystems:

ls -l:
oradatafile.dbf -> .real_oradatafile.dbf::cdev:vxfs:


To UnQuickIO the filesystem so it can be used on a sever that does not have DB Edition License, simply:

rm oradatafile.dbf
mv .real_oradatafile.dbf::cdev:vxfs: oradatafile.dbf

TO mount it.. do not forget to use:

mincache=direct,convosync=direct

[Syed Irfan]

I am not sure how these servers were rebuilt. But I am sure that veritas was installed on these servers as well. We have two of these servers. We do not have database edition. Hence I tried the noqio option and the file system got mounted.

I shall forward these commands
"rm oradatafile.dbf
mv .real_oradatafile.dbf::cdev:vxfs: oradatafile.dbf" to my sysadmin and we shall see what we can do about this.
Thanks for your help. Right now, the filesystems are mounted and oracle DB is loaded and its been running smoothly as before. Lets hope it stays that way.

Thanks
Irfan

[Alzhy]

It will naturally still function since the link still works.

HOWEVER -- beware that should the DBAs start extending tablespaces -- you may have issues...

Your DBAs or admin of the prebious environment (if applicable) should be aware of this...