Bug 264245 - ciss(4): Very low transfer rate
Summary: ciss(4): Very low transfer rate
Status: Closed Not A Bug
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 13.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: Jason W. Bacon
URL:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2022-05-25 21:49 UTC by Jason W. Bacon
Modified: 2022-05-27 00:20 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason W. Bacon freebsd_committer freebsd_triage 2022-05-25 21:49:30 UTC
ciss0: <HP Smart Array P410i> port 0x4000-0x40ff mem 0xfac00000-0xfadfffff,0xfabf0000-0xfabf0fff irq 28 at device 0.0 on pci1
ciss0: PERFORMANT Transport
da0 at ciss0 bus 0 scbus0 target 0 lun 0

da0: <HP RAID 1(1+0) OK> Fixed Direct Access SPC-3 SCSI device
da0: Serial Number 5001438013638F40
da0: 135.168MB/s transfers
da0: Command Queueing enabled
da0: 953837MB (1953459632 512 byte sectors)

File operations are indeed very slow.

Not sure if this is a widespread issue or particular to this old hardware.  This server is not important to me, but I'm available to help fix this issue.
Comment 1 Jason W. Bacon freebsd_committer freebsd_triage 2022-05-25 22:01:53 UTC
Scratch that.  Now it's behaving normally.  Perhaps the controller was running a scan earlier.  Nothing in the sys logs, but the server had not been booted in quite a while.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2022-05-26 00:02:39 UTC
^Triage: Reporter is committer, and resolver, assign accordingly
Comment 3 Jason W. Bacon freebsd_committer freebsd_triage 2022-05-27 00:20:06 UTC
Set up another identical server today and discovered this:

root@proliant2:/home/bacon # cciss_vol_status /dev/ciss0 
/dev/ciss0: (Smart Array P410i) RAID 1(1+0) Volume 0 status: OK. 
/dev/ciss0(Smart Array P410i:0): Non-Volatile Cache status:
                   Cache configured: Yes
                 Total cache memory: 144 MiB
                        Cache Ratio: 25% Read / 75% Write
                  Read cache memory: 36 MiB
                 Write cache memory: 108 MiB
                Write cache enabled: No
   Write cache temporarily disabled
           Temporary disable condition. Posted write operations have
been disabled due to the fact that less than 75% of the
battery packs are at the sufficient voltage level.

So the poor performance on the first server was probably due to the write cache being disabled until the batteries recharged.  This explains why the problem resolved itself.