Operating System - HP-UX
1827293 Members
2359 Online
109717 Solutions
New Discussion

Re: using device without a filesystem

 
Mauro Gatti
Valued Contributor

using device without a filesystem

Hi all,
in a serviceguard package I have a VG which contains 3 LV.
2 LV have a vxfs FS mounted by control script.
The last one is an LV I use with "-o snapof" mount_vxfs option.
So, every time package runs, it mounts a "snapshot".
I put the mount/umount commands in the customizable start and stop command sections of control script.
In fact, if I put the mount command in LV mount section, package doesn't start because it fails when it does an fsck check before mounting the LV.
It fails I use "-V" in FS_FSCK_OPT though.

Now I have 2 questions:
Is it possible to tell ServiceGuard to Ignore fsxk operation for this LV?
Does the option KILL_PROCESSES_ACCESSING_RAW_DEVICES="YES" affect my LV too?

Thank You

Regards

Mauro
Ubi maior, minor cessat!
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: using device without a filesystem

Shalom,

There should be no fsck operation on a raw disk device. You will need to modify your control script to stop trying to mount a filesystem on this raw disk device, then the fsck errors should stop.

Make sure there is no mount attempt in /etc/fstab as well.

This problem is due to a mistake in configuration of SG, most likely.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Sajjad Sahir
Honored Contributor

Re: using device without a filesystem

Dear Mauro

doing fsck? u have to configure u script, i think it is written wrongly


thanks and regards

Sajjad Sahir

Stephen Doud
Honored Contributor

Re: using device without a filesystem

If you listed this volume in the section with the other file systems, expect to see the script attempt to fsck it and mount it.

If you don't want that, remove that LV[?] entry and transfer any specially handled volume commands to the customer_defined_run_cmds function in the legacy package control script (or external script, if this is a modular package).