8192 bytes of 8192 bytes not paged

[Pietro84]

Hi,
what mean this message on syslog?

vmunix: device 0x80003001, 1K block #1234119792, 8192 bytes of 8192 bytes not paged, page addr =dead31.e00000017eeec000, bflag =40008f, bp = e0000001930bca00

Thanks

[Mel Burslan]

One line out of syslog usually does not mean much. As far as I can remember, these mmessages come in a block of other syslog messages with vmunix header and is indicative of a hardware failure of some kind.

Could you post +/- 50 lines (total of 100 lines) around this error message. If you have sensitive information in these lines, you can omit them out. Just make sure ones starting with word vmunix right after the system name is included in your post.

[Pietro84]

I have a lot of this message:


Mar 29 16:12:08 mi5gcg02 vmunix: device 0x80003001, 1K block #1226326176, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be550000, bflag =40008f, bp = e00000034b8ea700
Mar 29 16:12:08 mi5gcg02 vmunix: device 0x80003001, 1K block #1176801024, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be550000, bflag =40008f, bp = e00000034b8ea700
Mar 29 16:12:08 mi5gcg02 vmunix: device 0x80003001, 1K block #1234034672, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:08 mi5gcg02 vmunix: device 0x80003001, 1K block #1176869520, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:08 mi5gcg02 vmunix: device 0x80003001, 1K block #1225735760, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:09 mi5gcg02 vmunix: device 0x80003001, 1K block #1225739616, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:09 mi5gcg02 vmunix: device 0x80003001, 1K block #1234006824, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:09 mi5gcg02 vmunix: device 0x80003001, 1K block #1234010984, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:09 mi5gcg02 vmunix: device 0x80003001, 1K block #1225771935, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:09 mi5gcg02 vmunix: device 0x80003001, 1K block #1230300225, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:10 mi5gcg02 vmunix: device 0x80003001, 1K block #1226370985, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:10 mi5gcg02 vmunix: device 0x80003001, 1K block #1230304080, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:10 mi5gcg02 vmunix: device 0x80003001, 1K block #1230307944, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be548000, bflag =40008f, bp = e00000034b8ead00
Mar 29 16:12:10 mi5gcg02 vmunix: device 0x80003001, 1K block #1226378968, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be5a8000, bflag =40008f, bp = e00000030322d100
Mar 29 16:12:11 mi5gcg02 vmunix: device 0x80003001, 1K block #1234018968, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be5a8000, bflag =40008f, bp = e00000030322d100
Mar 29 16:12:11 mi5gcg02 vmunix: device 0x80003001, 1K block #1225727777, 8192 bytes of 8192 bytes not paged, page addr =dead31.e0000003be5a8000, bflag =40008f, bp = e00000030322d100

[Mel Burslan]

Together with not being sure, some place in the back of my brain tells me, the disk containing your paging area, is going (or went) bad. Check for any other vmunix messages which started showing up right around the start time of these messages.

[Pietro84]

first message in syslog is:

Mar 20 12:29:22 mi5gcg02 vmunix: device 0x80003001, 1K block #1172859288, 8192 bytes of 8192 bytes not paged, page addr =dead31.e000000359054000, bf
lag =40008f, bp = e0000001cdb65400
Mar 20 12:29:22 mi5gcg02 vmunix: vxfs: WARNING: msgcnt 1 mesg 038: V-2-38: vx_dataioerr - /dev/emcata00/Proc_Raw file system file data read error in
dev/block 0/1172859288

[Mel Burslan]

I am under the impression you are using VxVM not LVM. Not one of my forte but sounds like the volume is having hardware problems. find the disks in your rootdg and start a read exercise

dd if=/dev/dsk/cXtXdX of=/dev/null bs=16M

see if any of the disks is giving out an error message somewhere in this process.

prior to that, you can check if there are any totally dead drives on your system:

ioscan -fnC disk | more

look for NO_HW string in the output.

[Pietro84]

This is a LUN on a Clariion.
I have no NO_HW from ioscan and this is LVM. FS is vxfs type.

[Mel Burslan]

This makes me think that your are using Veritas Storage foundation:

V-2-38: vx_dataioerr

but again I might be mistaken. But again, you should check the explanation for this error, by clicking the link below:

http://www.symantec.com/business/support/index?page=content&id=HOWTO24736&key=15101&actp=LIST

In a condensed for, it says, diagnose the disk and replace if necessary.

If this is a Clariion LUN, get in touch with SAN admins and see if they have done anything to corrupt this volume ? They somehow, "accidentally" resize volumes towards the smaller size direction, causing all bedlam like you are experiencing.