what is lvmdevd deamon ?

[Can EKINGEN]

After installing some new lvm patches to hpux 11.0 I noticed a new deamon appeared :
# ps -ef| grep lvmdevd
root 31 0 0 Apr 23 ? 0:00 lvmdevd
root 51 0 0 Apr 23 ? 0:00 lvmdevd
root 52 0 0 Apr 23 ? 0:00 lvmdevd
root 53 0 0 Apr 23 ? 0:00 lvmdevd
root 54 0 0 Apr 23 ? 0:00 lvmdevd
root 55 0 0 Apr 23 ? 0:00 lvmdevd

what is it ?
thanks

[Robert-Jan Goossens]

No idear !

Could you check your installed patches.

# swlist -l fileset -a state -a revision

or run

# check_patches

Regards,
Robert-Jan

[Patrick Wallek]

I can find absolutely NOTHING in the technical knowledge base or the patch database on the ITRC that references lvmdevd.

The only thing I have been able to find that even remotely resembles it is a small piece on lvmdev for LINUX from 2001. In case you are interested, here's the link:
http://www.nezumi.plus.com/lvmboot/man.html

What happens if you do:

# swlist -l file | grep lvmdev

This command may take a while.....
What does it return?

[Jdamian]

Hi Can

I think this daemon as others as statdaemon, lvmkd, sblksched, ... and vhand are main kernel processes. Have you noticed the PPID of they all are zero (swapper) ? You'll fail if you try to find files in file system with those names.

I never got a satisfactory answer about this question. I think it is dark area of HP-UX.

[Can EKINGEN]

I guess you are right , this is a kernel process.

swlist -l file | grep lvmdev
gives nothing !!

I attach output of swlist -l fileset -a state -a revision

output of check_patches :
Report from check_patches utility
Revision: 1.30
05/18/04 10:24:36
System: imisdb6

============================== Invalid Patches ===============================

* Determining if any HP-UX 11.00 patches are missing the SD-UX patch
* attributes required for SD-UX to handle the patches properly. If the
* patch attributes are missing SD-UX does not treat the software as
* patches, which can lead to unexpected results.

No invalid patches are present.

=============================== ar(1) patches ================================

* Determining if patches PHSS_16841 and PHSS_17571 are active. These
* patches contain a version of the ar(1) command that can affect the
* loading of object modules into archive libraries. If the object
* module to be loaded has an older timestamp than the module currently
* in the library, ar(1) does not load the object module but reports the
* operation as successful.

* Since many kernel-related patches deliver object modules that are
* loaded into kernel libraries, PHSS_16841 and PHSS_17571 can affect
* the success of installing kernel-related patches. The kernel-related
* patches may be reported as installed when the modules were not
* actually loaded into the kernel libraries. If either of these patches
* is currently active, it should be removed before installing any
* additional patches that deliver object modules.

Neither PHSS_16841 nor PHSS_17571 is currently active.

=========================== Object Module Checksums ==========================

* Determining if the checksum values of the object modules delivered in
* the currently active patches match the checksum values of the modules
* in the appropriate library.

All object modules checksum values match.

=========================== Missing Patch Filesets ===========================

* Determining if the active patches have all their applicable filesets
* installed.

All applicable patch filesets for the active patches are present.

============================ Patch Fileset States ============================

* Determining if all patch filesets are in the configured state.

NOTE: One or more patch filesets are in the installed state, but
they do NOT include a configure script. Since these patch
filesets do not include a configure script, there is no
difference between the installed or configured state.

The patch filesets in this condition are:

PHKL_24004.C-INC
PHKL_24004.CORE-KRN
PHKL_24004.CORE2-KRN
PHKL_24004.KERN2-RUN
PHKL_24004.SPT2-DVR

If you prefer to have these patch filesets in the configured
state as opposed to the installed state, they can be
configured with swconfig(1M), for example:

swconfig PHKL_24004.SPT2-DVR

or to configure all the filesets in a patch:

swconfig PHKL_24004


================================ Patch_States ================================

* Determining if all patch_state attributes are correct.

ERROR: One or more patch filesets are in the incorrect patch_state.
Most likely due to a defect in swconfig(1M), these patch
filesets are in the 'applied' patch_state when they are
actually superseded on this system. You can run the
/usr/sbin/cleanup utility with the '-s' option to correct
the problem for the following patch filesets:

PHCO_20882.VXFS-BASE-RUN
PHKL_20207.CORE2-KRN
PHKL_20207.FCMS-ENG-A-MAN
PHKL_20207.FCMS-KRN
PHKL_20207.FCMS-RUN
PHKL_20674.VXFS-BASE-KRN
PHKL_21392.VXFS-BASE-KRN
PHKL_22589.C-INC
PHKL_22589.CORE-KRN
PHKL_22589.CORE2-KRN
PHNE_19899.CORE2-KRN
PHNE_19899.NET2-KRN
PHNE_19899.NMS2-KRN
PHNE_20008.STREAMS-32ALIB
PHNE_20008.STREAMS-64ALIB
PHNE_20008.STREAMS-64SLIB
PHNE_20008.STREAMS-KRN
PHNE_20008.STREAMS-MIN
PHNE_20008.STREAMS2-KRN
PHNE_20657.LAN-RUN
PHNE_20657.LAN2-KRN
PHNE_20657.NW-ENG-A-MAN

========================= Swverify on Patch Filesets =========================

ERROR: The swverify(1M) command on all patch filesets failed with
the following error(s):

ERROR: "imisdb6:/": 38 files had errors during this operation.
WARNING: "imisdb6:/": 2 files had warnings during this operation.

Please review the /var/adm/sw/swagent.log file for details.

[Jdamian]

In my box no lvmdevd process is found, but others are. These names should be inside kernel. To get the children of swapper:

ps -ef| awk '$3==0'

In my box appears some 'unknown' procesess: sblksched, statdaemon, lvmkd, ...

Then run the following command line:

strings -a /stand/vmunix | grep -e statdaemon -e sblksched

and the following output is printed:

Could not create statdaemon
statdaemon
sblksched
statdaemon
S$476DD$statdaemon