Start a Conversation

Unsolved

This post is more than 5 years old

80306

May 7th, 2013 09:00

Write Policy - PERC BIOS vs. OMSA

I'm getting a conflict between PERC BIOS and OMSA on the write policy of a virtual disk.  As you can see below the PERC BIOS shows Write Back, however OMSA is reporting Write Through.  I'm not using certified enterprise drives, which I'm hoping is the root of the issue. Is there a way to definitively determine which policy the system is using?  I'm OK with the issue being OMSA isn't reporting the write policy correctly, however I want to be sure the virtual disk is using write back.  This is a PERC H800 with 6 Samsung SSD 840 Series in a RAID10.  Let me know if there is any other info needed.

/opt/dell/srvadmin/bin#./omreport storage vdisk controller=0 vdisk=0
Virtual Disk 0 on Controller PERC H800 Adapter (Slot 1)

Controller PERC H800 Adapter (Slot 1)
ID : 0
Status : Ok
Name : WARM_SNDBY_DB
State : Ready
Hot Spare Policy violated : Not Assigned
Encrypted : No
Layout : RAID-10
Size : 1,395.75 GB (1498675150848 bytes)
Device Name : /dev/sda
Bus Protocol : SATA
Media : SSD
Read Policy : Adaptive Read Ahead
Write Policy : Write Through
Cache Policy : Not Applicable
Stripe Element Size : 64 KB
Disk Cache Policy : Enabled


















 
/opt/dell/srvadmin/bin#./omconfig storage vdisk controller=0 vdisk=0 action=changepolicy writepolicy=wb 
Command successful!

/opt/dell/srvadmin/bin#./omreport storage vdisk controller=0 vdisk=0
Virtual Disk 0 on Controller PERC H800 Adapter (Slot 1)

Controller PERC H800 Adapter (Slot 1)
ID : 0
Status : Ok
Name : WARM_SNDBY_DB
State : Ready
Hot Spare Policy violated : Not Assigned
Encrypted : No
Layout : RAID-10
Size : 1,395.75 GB (1498675150848 bytes)
Device Name : /dev/sda
Bus Protocol : SATA
Media : SSD
Read Policy : Adaptive Read Ahead
Write Policy : Write Through
Cache Policy : Not Applicable
Stripe Element Size : 64 KB
Disk Cache Policy : Enabled




















 
 

21 Posts

May 7th, 2013 09:00

Hi Chris,

I'm pretty sure I had performed a full system restart after changing the write policy, however I just did an OMSA service restart and I'm still seeing the same write through policy.

Moderator

 • 

8.4K Posts

May 7th, 2013 09:00

VPSA,

Have you restarted OMSA since changing the write policy?

Moderator

 • 

8.4K Posts

May 7th, 2013 10:00

Thank you. What is OMSA showing the battery status as? If the battery backed cache is down then it will auto convert to write through until the cache is restored.

21 Posts

May 7th, 2013 11:00

Learn State is Idle:

./omreport storage battery controller=0

Battery 0 on Controller PERC H800 Adapter (Slot 1)

Controller PERC H800 Adapter (Slot 1)

ID                        : 0

Status                    : Ok

Name                      : Battery 0

State                     : Ready

Recharge Count            : Not Applicable

Max Recharge Count        : Not Applicable

Predicted Capacity Status : Ready

Learn State               : Idle

Next Learn Time           : 76 days 4 hours

Maximum Learn Delay       : 7 days 0 hours

Learn Mode                : Auto

Thanks

21 Posts

May 7th, 2013 12:00

Hmm, I wonder if there is something up with the battery?  I can successfully change the policy to force write back:

/opt/dell/srvadmin/bin# ./opt/dell/srvadmin/bin#./omconfig storage vdisk controller=0 vdisk=0 action=changepolicy writepolicy=fwb

Command successful!

/opt/dell/srvadmin/bin# ./omreport storage vdisk controller=0 vdisk=0Virtual Disk 0 on Controller PERC H800 Adapter (Slot 1)

Controller PERC H800 Adapter (Slot 1)
ID : 0
Status : Ok
Name : WARM_SNDBY_DB
State : Ready
Hot Spare Policy violated : Not Assigned
Encrypted : No
Layout : RAID-10
Size : 1,395.75 GB (1498675150848 bytes)
Device Name : /dev/sda
Bus Protocol : SATA
Media : SSD
Read Policy : Adaptive Read Ahead
Write Policy : Force Write Back
Cache Policy : Not Applicable
Stripe Element Size : 64 KB
Disk Cache Policy : Enabled
 
Hope this helps some...
No Events found!

Top