Skip to main content

linux - Samsung 850 EVO + HP P410 limited iops?

I´m experiencing a weird write iops limitation with a HP
P410 256mb cache controller and 4x consumer grade ssd´s (Samsung EVO 850) in RAID5/10.
After upgrade to latest firmware (6.64) for HP P410 controller, it continues with
problems.




Iostat
output:



Device: rrqm/s wrqm/s r/s
w/s rkB/s wkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util
sda 0.00
0.00 1.00 158.00 36.00 15631.00 197.07 12.16 75.84 6.00 76.28 6.30
100.10

158 writes/s and 100 %
util.


My hpacucli
output:




=> ctrl all
show config detail

Smart Array P410 in Slot 2
Bus
Interface: PCI
Slot: 2
Serial Number: PACCR9SYLZ34

Cache Serial Number: PACCQ9SYP5CK
RAID 6 (ADG) Status: Disabled

Controller Status: OK

Hardware Revision: C
Firmware
Version: 6.62
Rebuild Priority: Medium
Expand Priority:
Medium
Surface Scan Delay: 15 secs
Surface Scan Mode:
Idle
Queue Depth: Automatic
Monitor and Performance Delay: 60
min
Elevator Sort: Enabled
Degraded Performance Optimization:
Disabled

Inconsistency Repair Policy: Disabled
Wait for
Cache Room: Disabled
Surface Analysis Inconsistency Notification:
Disabled
Post Prompt Timeout: 0 secs
Cache Board Present:
True
Cache Status: OK
Cache Ratio: 100% Read / 0% Write

Drive Write Cache: Disabled
Total Cache Size: 256 MB
Total Cache
Memory Available: 144 MB

No-Battery Write Cache:
Disabled
Battery/Capacitor Count: 0
SATA NCQ Supported:
True

Array: A
Interface Type: Solid State
SATA
Unused Space: 0 MB
Status: OK
Array Type:
Data




Logical Drive: 1

Size: 698.6 GB
Fault Tolerance: RAID 5
Heads: 255

Sectors Per Track: 32
Cylinders: 65535
Strip Size: 256
KB
Full Stripe Size: 768 KB

Status: OK

Caching: Enabled
Parity Initialization Status: Initialization
Failed
Unique Identifier: 600508B1001C8929D0C6820FB103773E
Disk
Name: /dev/sda
Mount Points: None
Logical Drive Label:
A516FD0DPACCR9SYLZ3435C0
Drive Type: Data

physicaldrive
1I:1:1

Port: 1I
Box: 1
Bay: 1

Status: OK
Drive Type: Data Drive
Interface Type: Solid State
SATA
Size: 250 GB
Firmware Revision: EMT01B6Q
Serial
Number: S21PNSAG270000F
Model: ATA Samsung SSD 850


SATA NCQ Capable: True
SATA NCQ Enabled: True
Current Temperature
(C): 30
Maximum Temperature (C): 70
SSD Smart Trip Wearout: Not
Supported
PHY Count: 1
PHY Transfer Rate:
3.0Gbps

physicaldrive 1I:1:2
Port:
1I

Box: 1
Bay: 2
Status: OK
Drive
Type: Data Drive
Interface Type: Solid State SATA
Size: 250
GB
Firmware Revision: EMT01B6Q
Serial Number: S21PNSAG269993V

Model: ATA Samsung SSD 850
SATA NCQ Capable:
True

SATA NCQ Enabled: True
Current Temperature (C):
32
Maximum Temperature (C): 70
SSD Smart Trip Wearout: Not
Supported
PHY Count: 1
PHY Transfer Rate:
3.0Gbps

physicaldrive 1I:1:3
Port: 1I
Box:
1

Bay: 3
Status: OK
Drive Type: Data
Drive
Interface Type: Solid State SATA
Size: 250 GB

Firmware Revision: EMT01B6Q
Serial Number: S21PNSAG269984Z
Model:
ATA Samsung SSD 850
SATA NCQ Capable: True
SATA NCQ Enabled:
True

Current Temperature (C): 31
Maximum Temperature
(C): 70
SSD Smart Trip Wearout: Not Supported
PHY Count:
1
PHY Transfer Rate: 3.0Gbps

physicaldrive
1I:1:4
Port: 1I
Box: 1
Bay: 4


Status: OK
Drive Type: Data Drive
Interface Type: Solid State
SATA
Size: 250 GB
Firmware Revision: EMT01B6Q
Serial
Number: S21PNSAG269998N
Model: ATA Samsung SSD 850
SATA NCQ
Capable: True
SATA NCQ Enabled: True
Current Temperature (C):
31

Maximum Temperature (C): 70
SSD Smart Trip Wearout:
Not Supported
PHY Count: 1
PHY Transfer Rate:
3.0Gbps


SEP (Vendor ID PMCSIERA, Model SRC 8x6G)
250
Device Number: 250
Firmware Version: RevC
WWID:
500143800694906F

Vendor ID: PMCSIERA
Model: SRC 8x6G



Someone has
experienced this problem with HP P410?

Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able