Question regarding ASM/LVM and block size

Solution Verified - Updated -

Issue

  • I was forwarded a known issue from Oracle in regards to ASM and disks block sizes. It seems there are cases where a firmware update on a storage array may change the block_size of LUNs from 512 bytes to 4k, which causes ASM to stop fail at start up time.

We have all ASM devices inside LVM (they are actually logical volumes), so I'm wondering how LVM will work if existing LUNs get their block_size changed from 512 to 4k, and whether there's any different in behavious from RHEL4 to RHEL6. I wouldn't expect someone to actually change this on purpose, but if a firmware does it automatically, and LVM passes it through, then yeah, we might have an issue.

Environment

  • Red Hat Enterprise Linux 4,5,6
  • Oracle ASM
  • LVM

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content