SAS drives along with the extra overhead from the encryption. Most likely, this is due to the slowness of SATA drives vs. When files are being written to the RAID array. Use the 'show' command on devices to show additional details about the configuration. > controller slot0 array C remove drives1I:1:9 Error: This operation is not supported with the current configuration. Workqueue: writeback wb_workfn (flush-254:8) There are many more interesting and useful commands, but these require license key. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. But in the output of hpacucli ctrl slot0. The disks has been replaced and in hpacucli ctrl slot0 show config everything seems to be OK, the new disk is marked as spare. Its RAID5 consisting of 5 disks with an additional 6th disk as spare. Tainted: G I 3.12.0-1-amd64 #1 Debian 3.12.6-1 Having a little problem with a Smart Array P410i in a ProLiant D元80G6. ![]() INFO: task kworker/u65:0:29268 blocked for more than 120 seconds. The first one addresses all unassigned drives while the second one is addressing them directly but the result will be the same. When running cryptsetup to setup a LUKS encrypted drive on a HP SmartArray that is filled with SATA drives instead of SAS, then regardless of the filesystem (although XFS seems to make the problem manifest more often), you might get errors such as:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |