lvlnboot

[dctw]

All of a sudden I got this entries in the syslog :-


May 13 16:19:01 server vmunix: 0/2/1/0.1.0.0.0.0 tgt
May 13 16:19:01 server vmunix: 0/2/1/0.1.0.255.0.0 tgt
May 13 16:19:01 server vmunix: 0/2/1/0.1.0.0.0.0.0 sctl
May 13 16:19:01 server vmunix: 0/2/1/0.1.0.255.0.0.0 sctl
May 13 16:19:01 server vmunix: 0/2/1/0.1.0.0.0.0.1 sdisk
May 13 16:19:01 server vmunix: 0/4/1/0.1.0.0.0.0 tgt
May 13 16:19:01 server vmunix: 0/4/1/0.1.0.255.0.0 tgt
May 13 16:19:01 server vmunix: 0/4/1/0.1.0.0.0.0.0 sctl
May 13 16:19:01 server vmunix: 0/4/1/0.1.0.255.0.0.0 sctl
May 13 16:19:01 server vmunix: 0/4/1/0.1.0.0.0.0.1 sdisk
May 13 16:19:46 server LVM[28673]: lvlnboot -v
May 13 16:20:06 server LVM[28741]: /usr/sbin/lvlnboot -v


Can anyone tell me what is happening? I didn't do anything on the server.

[Mridul Shrivastava]

These are normal messages and there is absolutely nothing to worry about.

Was there any OS Backup going on or someone executed ioscan etc ??

[dctw]

We didn't do anything.
Nor having ioscan or backup on the server.

[Avinash Agarkar]

Hi,

Check weather any cron script is not running for ioscan or lvlnboot.

Else it is normal it some times Hp diag tool also the few commands to check the errors.

Thanks,
Avinash

[Torsten.]

Maybe you opened SAM's disk section?

SAM will gather some information - any LVM command used will be recorded in syslog.

[Rasheed Tamton]

Most probably someone used the command manually. First lvlnboot -v then /usr/sbin/lvlnboot -v.

If you do it again manually, you could recreate it.

Other reason may be there was ignite backup at that time.

rgds.

[Wim Rombauts]

And the first lines (about vmunix) mean that the server has detected new hardware, and looking atthe hardware paths, it is on a SAN.