vxfs mesg 080 being written to syslog

[Berd]

Hello,

Has anyone come across the below error message before. I've checked all by filesystems using fstyp -v, and they are all version 4 ?????

Nov 21 10:27:40 thbk10 vmunix: msgcnt 1 vxfs: mesg 080: Disk layout versions older than Version 4 wi
ll not be
Nov 21 10:27:40 thbk10 vmunix: supported in the next release. It is advisable to upgrade
Nov 21 10:27:40 thbk10 vmunix: to the latest layout version now. See vxupgrade(1M) for
Nov 21 10:27:40 thbk10 vmunix: information on upgrading a VxFS file system and see the
Nov 21 10:27:40 thbk10 vmunix: VxFS Release Notes for information on disk layout support.

Regards,
Berd

[Coolmar]

Hi Berd,

This thread my help you out:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1046263

[Peter Godron]

Berd,
might be worthwhile running vxupgrade to see which fs it is complaining about.
From "man vxupgrade"
When invoked without the -n option, vxupgrade prints the disk layout version number of the file system.

Any hidden raw partitions ?

For further details on the message:
http://docs.hp.com/en/5971-4772/apbs03.html
towards the end of the page.

[Berd]

Thanks for the input,

I have used both fstyp and vxupgrade to confirm the vxfs version, and all filesystems are version 4 ??? I don't think I have any hidden raw volumes, how could I confirm ?

Regards,
Berd

[Peter Godron]

Berd,
sorry, ignore the raw partition line.
Can you pinpoint what was happening on the machine at the time ? Was anything changed/installed on the machine? Did the warning in syslog.log occur after a reboot ?

[Berd]

Peter,

The server producing the errors is our Netbackup server. From looking at the times when the entry is written to syslog it looks like this is the point in time when Business Copy volume groups are activated and mounted for backup. I have checked these filesystems when they're mounted and they are all Version 4??

Regards,
Berd

[Peter Godron]

Berd,
ok, my last idea, how about the volume (tape) you are backing up to ? Does it have a previous (old version) fs ?

[Berd]

Peter,

Do you know how I could check this ?

Berd

[Dave Hutton]

We have the same error on our backup server.
Basically I've ignored it only because as I read this, its just an informational message.

We do the same thing, our backup server is running hpux 11.23 and the host we are mounting the BC's from is an 11.11.

As I read it, its just stating that other file systems on the local server are running the newer file system type where the mounted BC is older.

Below is our filesystem that stays on our server is version 5.
servera:root /usr/local/bin # fstyp -v /dev/vg07/lvol1
vxfs
version: 5
f_bsize: 8192
f_frsize: 1024
f_blocks: 62668800
f_bfree: 8605908
f_bavail: 8068039
f_files: 2232632
f_ffree: 2151476
f_favail: 2151476
f_fsid: 1074200577
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 0
f_fsindex: 9
f_size: 62668800


Where the bc is version 4:
servera:root /usr/local/bin # fstyp -v /dev/vg65/lvol1
vxfs
version: 4
f_bsize: 8192
f_frsize: 8192
f_blocks: 7110656
f_bfree: 2884670
f_bavail: 2862134
f_files: 2102528
f_ffree: 721152
f_favail: 721152
f_fsid: 1078001665
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_size: 7110656


Could we upgrade the fs of the bc? I'm sure we could, but I'm not sure how it would handle it on the production host.

Hopefully that makes sense.

So for us, we ignore it since we don't want to upgrade the file system on the prod host to match our backup server file systems.

[Berd]

Thanks for the imput everyone.

I spotted the culprit, a couple of filesystems which are temporarily mounted for backup. I managed to check vxfs version whilst they were mounted, and they were indeed version 3. I will now arrange to vxupgrade them.

Berd