cciss/c0d1: messages filling dmesg

[Moonf4]

We are seeing this on several of our recent server installs.

cciss/c0d1:
blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

cciss/c0d1:
blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

cciss/c0d1:
blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

cciss/c0d1:
blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

blocks= 286677120 block_size= 512
heads= 255, sectors= 32, cylinders= 35132

Anyone know what would cause might be?

Thanks,

[Steven E. Protter]

Shalom,

This is informational, indicates no specific error.

Perhaps syslog.conf is wrong, causing these messages to repeat.

What is the Linux distribution and specific disk configuration here. Whole disk, LVM, etc.

SEP

[Moonf4]

It is happening for any unformatted hot stand-by disks we have on the servers.

The OS is RedHat EL 5.3. The servers are ProLiant DL380 G6 & DL385 G6's.

[Moonf4]

Anyone have any other suggestions?

Thanks,

[mbscholz]

Hi,

I can confirm that we're seeing the same messages on several DL360 G5 with RHEL 5. So it seems to be more or less normal :)

I guess you know that /dev/cciss is the Hardware-Raid-Controller, so you're seeing messages of the first Raid-Disk. And I agree that it's not to be understood as an error, just as an information.

Unfortunately I can't tell you why these messages occur. Printing the data of the disk every few minutes seems to be a really senseless thing to me...

When I find out more I'll post it here.

Best regards,
Michael

[mbscholz]

Hi,

I checked again and found out that these messages don't come again when I uninstall hpacucli (the tool for managing the disk array). So this seems to responsible for the messages. Unfortunately the documentation doesn't say anything about switching it off...

Best regards,
Michael