No LVM specific errors ar reported to /var/log/messages or dmesg. Well the 
messages entries contain dm-6 as device which stands for DeviceMapper device 6 
as far as I'm concerned.

Usage of an journaled filesystem is generally a good idea and will be done.

Meanwhile we tried to write to the array with one cluster node entirely turned 
off. The problem remains. Also we found 3 different firmware versions on the 
disks in the array, which is generally bad. I had very bad experiences with 
different firmware revisions together in one array before, so this will be 
adressed to HP.

As for 2.6 kernels. HP supports HA cluster configurations with this 
architecture with SLES 9 which is using a 2.6 kernel. HP suggestet timing 
problems due to SMP Kernel on a hyperthreading CPU so I will try the kernel 
without SMP support.

-----Urspr�ngliche Nachricht-----
Von: Mohamed Badri [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 10. Februar 2005 17:10
An: [EMAIL PROTECTED]
Betreff: [Spamverdacht] Re: [gentoo-server] AW: [Spamverdacht] Re:
[gentoo-server] Problems with HP MSA 500 Storage


If vg is disabled he can't, because lvm2 devices are not created until
vg is activated.

any lvm2 specific errors ?
Did you ask hp, if they support this controller with 2.6 kernel ?

perhabs it's an issue with controller module in 2.6 kernel.

Sorry but I can't help, I never see this type of architecture with ext2. 
In this case it is common to use gfs if the 2 hosts are active
or any over journalized filesystems ( ext3, reiser ... )

But I think there is no link with filesystem as errors is sent by controller
kernel module.

Selon "Witschel, Matthias, Infraserv-Hoechst/DE" <[EMAIL PROTECTED]>:

> Hi!
> 
> I have heartbeat set up to control the entire volumegroup containing th
> msa500 volume. It's disabled at boot time on both hosts via boot.local and
> activated and mounted by heartbeat resource scripts. The only step to further
> disable any unwanted contact to the filesystem is  to take the ext2 kernel
> support out of the kernel to a module, that would additionally by loaded by
> heartbeat. Any idea if its possible for the standby host to write to the
> volume if the vg is disabled?
> 
> -----Urspr�ngliche Nachricht-----
> Von: Mohamed Badri [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 10. Februar 2005 16:08
> An: [EMAIL PROTECTED]
> Betreff: [Spamverdacht] Re: [gentoo-server] Problems with HP MSA 500
> Storage
> 
> 
> Hi,
> 
> did the msa500 lvm volume is mounted on each hosts at the same time ?
> or do you have an heartbeat software that mount the volume after the master
> host failed ?
> 
> This problem can happen if two hosts try to write in the ext2 filesystem at
> the
> same time, as ext2 cant handle this case.
> 
> Selon "Witschel, Matthias, Infraserv-Hoechst/DE"
> <[EMAIL PROTECTED]>:
> 
> > Hallo everybody!
> > 
> > Short info on architecture in use:
> > 
> > I have a setup of two HP DL380 with Smart Array 5i Controller for internal
> > Disks (RAID 1 for rootdisks, on mashine wit additional RAID 5 for local
> > database). Both Machines are attached to a HP MSA 500 Storage device via
> > Smart Array 532 Controller. The machines form a high availability cluster
> for
> > an Oracle database. Kernel in Use is 2.6.10-gentoo-r6. This construct is
> > suggestet by HP for use in HA clusters. The device has one singel lun wich
> is
> > used as LVM2 device via device-mapper. FS ist ext2.
> > 
> > For a few days now write access to the MSA 500 stalls. Afterwards every
> > access to that device stalls too. The machine refises to sync and will not
> > reboot without pressing tho power button.
> > 
> > Please help!
> > _any_ hint is welcome! Including input on working environments with
> similiar
> > setup or similiar problems. Any hint on possible problems with the used
> > kernel or host bus adapters?
> > 
> > Kind regards,
> > 
> > Matthias Witschel
> > 
> > PS: Here are the relevant messages from /var/log/messages:
> > (earlier tests included EXT2 error messages ahead of the timeout, this
> didn't
> > happen after fsck on the device)
> > 
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80000 timedout
> > Feb  9 16:56:16 telkas1 Buffer I/O error on device dm-6, logical block
> 60998
> > Feb  9 16:56:16 telkas1 lost page write due to I/O error on dm-6
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80248 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80490 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d806d8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80920 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80b68 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80db0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d80ff8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d81240 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d81488 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d816d0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d81918 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d81b60 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d81da8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d81ff0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d82238 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d82480 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d826c8 timedout
> > Feb  9 16:56:16 telkas1 Buffer I/O error on device dm-6, logical block
> 62023
> > Feb  9 16:56:16 telkas1 lost page write due to I/O error on dm-6
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d82910 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d82b58 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d82da0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d82fe8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d83230 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d83478 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d836c0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d83908 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d83b50 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d83d98 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d83fe0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d84228 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d84470 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d846b8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d84900 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d84b48 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d84d90 timedout
> > Feb  9 16:56:16 telkas1 Buffer I/O error on device dm-6, logical block
> 63048
> > Feb  9 16:56:16 telkas1 lost page write due to I/O error on dm-6
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d84fd8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d85220 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d85468 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d856b0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d858f8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d85b40 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d85d88 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d85fd0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d86218 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d86460 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d866a8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d868f0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d86b38 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d86d80 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d86fc8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d87210 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d87458 timedout
> > Feb  9 16:56:16 telkas1 Buffer I/O error on device dm-6, logical block
> 64073
> > Feb  9 16:56:16 telkas1 lost page write due to I/O error on dm-6
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d876a0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d878e8 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d87b30 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d87d78 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d87fc0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d88208 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d88450 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d88698 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d888e0 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d88b28 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d88d70 timedout
> > Feb  9 16:56:16 telkas1 cciss: cmd f7d88fb8 timedout
> > 
> 
> 
> 
> 
> ---------------------------
> http://webmail.netbadri.com
> 




---------------------------
http://webmail.netbadri.com

Reply via email to