Показаны сообщения с ярлыком Adaptec. Показать все сообщения
Показаны сообщения с ярлыком Adaptec. Показать все сообщения

четверг, 22 марта 2012 г.

Способы сборки массивов Adaptec - clear / build verify / quick init / skip init

Подробно описаны тут: http://ask.adaptec.com/cgi-bin/adaptec_tic.cfg/php/enduser/std_adp.php?p_faqid=10062&p_created=1065098797&p_sid=TkmSHeZk&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQ6MSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9Nyw3JnBfcHJvZHM9MCZwX2NhdHM9MCZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9cXVpY2sgaW5pdA**&p_li=&p_topview=1

воскресенье, 18 марта 2012 г.

Adaptec - замена сразу двух жестких дисков в RAID 10

К сожалению, такое случается. При этом, есть одна фича - насколько я понял, контроллер не выполняет более 1го ребилда в один момент времени. То есть, если у Вас есть массив в состоянии DEGRADED с двумя missing жесткими дискам и Вы заменяете два диска на новые, то сначала один из них станет rebuilding, а второй так и останется миссинг, но в arcconf pd 1 его статус будет "ready". Как закончится первый ребилд, сразу же начнется второй и missing превратится в rebuilding.

Как узнать прогресс ребилда рейда на Adaptec?

arcconf GETSTATUS 1
Controllers found: 1
Logical device Task:
  Logical device                 : 0
  Task ID                        : 105
  Current operation              : Rebuild
  Status                         : In Progress
  Priority                       : High
  Percentage complete            : 15

Как узнать, почему Adaptec пометил диск сбойным / выкинул диск из массива?

Следуюящая команда выдает лог сбоев дисков по всему контроллеру:
arcconf getlogs 1 dead

Строка, повествтующая об отказе/выбросе диска из массива выглядит как: deadDriveEntry vendorID="SEAGATE " rtcSeconds="1" rtcMinutes="47" rtcHours="8" rtcDay="18" rtcMonth="3" rtcYear="2012" serialNumber="3SJ202FY00009104X2T0" productID="ST330065" wwn="5000c500240e70a8" failureReasonCode="1"

Где, failureReasonCode - код, в котором зашифрована причина действия контроллера.

Вот все коды:
0 or 0x00 Unknown failure
1 or 0x01 Device not ready
2 or 0x02 Selection timout
3 or 0x03 User marked the drive dead
4 or 0x04 Hardware error
5 or 0x05 Bad block
6 or 0x06 Retries failed
7 or 0x07 No Response from drive during discovery
8 or 0x08 Inquiry failed
9 or 0x09 Probe(Test Unit Ready/Start Stop Unit) failed
A or 0x0A Bus discovery failed

Источник: http://ask.adaptec.com/scripts/adaptec_itic.cfg/php.exe/enduser/std_adp.php?p_faqid=17051&p_created=1284026018

вторник, 2 августа 2011 г.

Запуск arcconf на read only (ro) файловой системе

Итак, есть сервер с контроллером Adaptec, ФС которого перешла в RO. Очевидный вариант - проверить состояние массива утилитой arcconf, но она не срабатывает!

arcconf getconfig 1 ld
Could not open log file: /var/log/UcliEvt.log

После выдачи ошибки команда блокируется. Первое предположение было, что открытие лог файла необходимо для работы программы, но strace открыл глаза на источник проблемы:

umask(022) = 077
poll(0, 0, 50) = 0 (Timeout)
umask(077) = 022
open("/var/lock/.aac0lock", O_RDWR) = -1 EROFS (Read-only file system)
umask(022) = 077
poll(0, 0, 50) = 0 (Timeout)
umask(077) = 022
open("/var/lock/.aac0lock", O_RDWR) = -1 EROFS (Read-only file system)
umask(022) = 077
poll(0, 0, 50) = 0 (Timeout)
umask(077) = 022
open("/var/lock/.aac0lock", O_RDWR) = -1 EROFS (Read-only file system)
umask(022) = 077
poll(0, 0, 50) = 0 (Timeout)
umask(077) = 022
open("/var/lock/.aac0lock", O_RDWR) = -1 EROFS (Read-only file system)
umask(022) = 077
poll(0, 0, 50) = 0 (Timeout)
umask(077) = 022
open("/var/lock/.aac0lock", O_RDWR) = -1 EROFS (Read-only file system)
umask(022) = 077
poll(0, 0, 50) = -1 EINTR (Interrupted system call)

То есть, программа не могла создать лок-файл. Фиксится легко:
mount -t tmpfs none /var/lock

Все, после этого сработало на ура:
arcconf getconfig 1 ld
Could not open log file: /var/log/UcliEvt.log
Controllers found: 1
----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device number 0
Logical device name : Device 0
RAID level : 10
Status of logical device : Optimal
Size : XXXXX MB
Stripe-unit size : 256 KB
Read-cache mode : Enabled
MaxIQ preferred cache setting : Enabled
MaxIQ cache setting : Disabled
Write-cache mode : Enabled (write-back)
Write-cache setting : Enabled (write-back)
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
Power settings : Disabled
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Group 0, Segment 0 : Present (0,0) 6SJ0ET5R0000M124SKJU
Group 0, Segment 1 : Present (0,1) 6SJ0DRBM0000M125DK6G
Group 1, Segment 0 : Present (0,2) 6SJ0EET40000M125DNTK
Group 1, Segment 1 : Present (0,3) 6SJ0ERJZ0000M1214JZD



Command completed successfully.
Could not open log file: /var/log/UcliEvt.log

вторник, 31 мая 2011 г.

Активация write-cache на Adaptec 5405

Имеем изнчачально:
arcconf getconfig 1 ld
Controllers found: 1
----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device number 0
Logical device name : Device 0
RAID level : 10
Status of logical device : Optimal
Size : 571382 MB
Stripe-unit size : 256 KB
Read-cache mode : Enabled
MaxIQ preferred cache setting : Disabled
MaxIQ cache setting : Disabled
Write-cache mode : Disabled (write-through)
Write-cache setting : Enabled (write-back) when protected by battery/ZMM
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
Power settings : Disabled
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Group 0, Segment 0 : Present (0,0) 3SJ262RY00009107YURG
Group 0, Segment 1 : Present (0,1) 3SJ23Z2800009107YUZ7
Group 1, Segment 0 : Present (0,2) 3SJ262YX00009107XUQ6
Group 1, Segment 1 : Present (0,3) 3SJ261VB00009107XUQP

arcconf SETCACHE 1 LOGICALDRIVE 0 wb
Controllers found: 1
WARNING: Power failure without battery/ZMM support will lead to data loss.
Do you wish to continue?
Press y, then ENTER to continue or press ENTER to abort: y

Command completed successfully.

В результате включается кэш:
arcconf getconfig 1 ld
Controllers found: 1
----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device number 0
Logical device name : Device 0
RAID level : 10
Status of logical device : Optimal
Size : 571382 MB
Stripe-unit size : 256 KB
Read-cache mode : Enabled
MaxIQ preferred cache setting : Disabled
MaxIQ cache setting : Disabled
Write-cache mode : Enabled (write-back)
Write-cache setting : Enabled (write-back)
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
Power settings : Disabled
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Group 0, Segment 0 : Present (0,0) 3SJ262RY00009107YURG
Group 0, Segment 1 : Present (0,1) 3SJ23Z2800009107YUZ7
Group 1, Segment 0 : Present (0,2) 3SJ262YX00009107XUQ6
Group 1, Segment 1 : Present (0,3) 3SJ261VB00009107XUQP



Command completed successfully.

Обращаю внимание, что без наличия UPS кэш записи включать нельзя!

четверг, 26 мая 2011 г.

Несколько слов о write cache в контроллерах Adaptec

http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=8971&p_created=1056105282&p_topview=1

Технология ZMCP от Adaptec - сохранение кэша RAID контроллера без батарейки BBU

Zero-Maintenance cache Protection

Если вкратце, то эта технология заменяет собой функцию батарейки на RAID контроллере обычной флешкой. Если ранее для сохранения содержимого кэша (хранимого в энергозависимой микросхеме) контроллера использовалась батарейка (блок BBU, который, к слову, стоит весьма немало - для контроллера Adaptec 5405 стоящего 13 т.р. BBU модуль обойдется в 4.5 т.р.), то сейчас технология изменилась. Теперь при потере питания специальная схема фикисрует этот факт и посредством энергии суперконденсатора переносит данные из энергозависимого кэша на Nэнергонезависимый NAND флеш. После восстановления питания содержимое кэша переносится с флеш-карты непосредственно в кэш и все операции ввода-вывода завершаются успешно, без потери данных.

Новые контроллеры с поддержкой технологии ZMCP: 5405Z, 5805Z, 5445Z.

Вот сраница описания технологии: http://www.adaptec.com/ru-ru/_common/zmcp/

А вот презенатция в PDF (положил в репо, так как Adaptec регулярно ломает ссылки на своем сайте): http://fastvps.googlecode.com/files/ru_6514_series5z_17.pdf

воскресенье, 24 апреля 2011 г.

Adaptec: Simple Volume vs JBOD

Столкнулся вот с такой штукой на Adaptec:
Logical device information
----------------------------------------------------------------------
Logical device number 0
Logical device name : SSD-Volume
RAID level : Simple_volume
Status of logical device : Optimal
Size : 114290 MB
Read-cache mode : Enabled
MaxIQ preferred cache setting : Enabled
MaxIQ cache setting : Disabled
Write-cache mode : Enabled (write-back)
Write-cache setting : Enabled (write-back)
Partitioned : No
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
Power settings : Disabled
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Segment 0 : Present (0,0) 110965043200046100B1


Но вот как создавать эти самые Simple_volume через arcconf и чем они отличаются от JBOD - не знаю. Кто подскажет?

Создать Simple Volume можно так:
arcconf create 1 LOGICALDRIVE MAX volume 0,1

Причем, можно создать SM прямо из JBOD раздела.

У Simple Volume заметил преимущество - не надо ребутать систему, чтобы были увидены массивые, в отличие от JBOD.

пятница, 25 марта 2011 г.

Странные ошибки от контролллера Adaptec 5405

sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:<3>Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Dev sdc: unable to read RDB block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
unable to read partition table
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:<3>Buffer I/O error on device sdc, logical block 0
Dev sdc: unable to read RDB block 0
unable to read partition table
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:Dev sdc: unable to read RDB block 0
unable to read partition table
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:Dev sdc: unable to read RDB block 0
unable to read partition table
sd 6:0:0:0: Device offlined - array deleted
sd 6:0:0:0: Device online - array created
SCSI device sdc: 1170210816 512-byte hdwr sectors (599148 MB)
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc: detected capacity change from 1073741824 to 599147937792
SCSI device sdc: 1170210816 512-byte hdwr sectors (599148 MB)
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
SCSI device sdc: 1170210816 512-byte hdwr sectors (599148 MB)
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc: unknown partition table
printk: 30 messages suppressed.
TCP: Treason uncloaked! Peer 217.118.66.105:46079/80 shrinks window 1145999560:1146003940. Repaired.
TCP: Treason uncloaked! Peer 217.118.66.105:46079/80 shrinks window 1145999560:1146003940. Repaired.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.


В целом массив работает отлично, ошибки заметил уже лишь потом, но все равно приятного мало.

среда, 23 марта 2011 г.

Adaptec: aacraid: Host adapter abort request

Вот такие вот рекомендации дает производитель: http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=15357&p_created=1225366599

Реальное воспроизведение этой проблемы у меня на CentOS / OpenVZ ядре выглядело так:
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter reset request. SCSI hang ?
aacraid: SCSI bus appears hung
INFO: task kjournald:2667 blocked for more than 300 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kjournald D ffff81063d6c6d20 0 2667 239 2694 2614 (L-TLB)
ffff81063c96dd10 0000000000000046 ffff8103cef55c18 ffff81063e994048
ffff81063d6c6d20 ffff81063f2c21e0 00225e9c3f355275 007303b73490f812
ffff81063d6c6f28 ffff81063f2be000 ffffffff80315a00 ffffffff8006f959
Call Trace:
[] do_gettimeofday+0x40/0x8f
[] sync_buffer+0x0/0x40
[] io_schedule+0x59/0x8a
[] sync_buffer+0x3b/0x40
[] __wait_on_bit+0x40/0x6e
[] sync_buffer+0x0/0x40
[] out_of_line_wait_on_bit+0x6c/0x78
[] wake_bit_function+0x0/0x23
[] :jbd:journal_commit_transaction+0x66b/0x163e
[] autoremove_wake_function+0x0/0x2e
[] try_to_del_timer_sync+0x7f/0x88
[] keventd_create_kthread+0x0/0xc4
[] :jbd:kjournald+0xb9/0x21b
[] autoremove_wake_function+0x0/0x2e
[] :jbd:kjournald+0x0/0x21b
[] kthread+0xfe/0x132
[] child_rip+0xa/0x11
[] keventd_create_kthread+0x0/0xc4
[] kthread+0x0/0x132
[] child_rip+0x0/0x11
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000000
end_request: I/O error, dev sda, sector 1133805164
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 112099172
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 303601948
Buffer I/O error on device sda3, logical block 33492206
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 183335284
Buffer I/O error on device sda3, logical block 18458873
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 273263468
Buffer I/O error on device sda3, logical block 29699896
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 232821356
Buffer I/O error on device sda3, logical block 24644632
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 86586132
Buffer I/O error on device sda3, logical block 6365229
lost page write due to I/O error on sda3
Buffer I/O error on device sda3, logical block 6365230
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1116971484
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 84935588
Buffer I/O error on device sda3, logical block 6158911
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 263340548
Buffer I/O error on device sda3, logical block 28459531
lost page write due to I/O error on sda3
Buffer I/O error on device sda3, logical block 28459532
lost page write due to I/O error on sda3
Buffer I/O error on device sda3, logical block 28459533
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 275067372
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 306325300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 306325332
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 312738348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 316436948
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 263233268
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 316519140
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 316568044
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 346630132
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 347241932
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 459654004
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 460845484
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 565326356
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 569129404
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 640792020
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 660554428
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 928905388
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 77890148
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 198046388
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 208842820
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 232649956
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 928970300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 929035804
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1093459916
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1098507076
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 198046204
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100424348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100424452
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100425092
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 198028908
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100425300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1103607796
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160166780
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 82970692
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 189826148
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 189878244
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 190022364
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160171820
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160187908
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160198900
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160203716
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 160737052
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160214452
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 70747316
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 71142516
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 71665108
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 74873164
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 77072380
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 80954860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 82987108
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 82987156
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 83334076
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 83334124
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 84943132
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98054508
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98187988
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189236
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189268
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189804
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189964
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98271148
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98271340
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98278748
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 128166348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98278812
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98278860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98281972
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282084
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282420
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282948
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282980
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98287612
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98287748
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98287948
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 123360132
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 127312892
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 135922428
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 138690860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 154303020
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 156942356
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 158376348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 308734652
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1088653580
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1087114988
Aborting journal on device sda3.
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 273794092
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
ext3_abort called.
EXT3-fs error (device sda3): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
end_request: I/O error, dev sda, sector 78396708
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 215049556
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 191614356
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 199221588
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1094780788
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1094781492
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 415043868
EXT3-fs error (device sda3): ext3_find_entry: reading directory
#11855957 offset 0
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_truncate: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error

arcconf при этом также не работал:
/usr/StorMan/arcconf getconfig 1
Could not open log file: /var/log/UcliEvt.log
[[email protected] ~]#

пятница, 8 октября 2010 г.

Установка утилиты arcconf для Adaptec 5405 на Debian 5 Lenny Linux

Вполне возможна, даже есть официальные (но минимально протестированные!) сборки StorMan для Debian/Ubuntu: здесь.

Инструкцию по установке:
cd /usr/src
wget http://download.adaptec.com/tmp0001/adaptec/asmdeb/asm_debian_x86_x64_v6_50_18570.tgz
tar -xf asm_debian_x86_x64_v6_50_18570.tgz
# 64 бита
dpkg -i storman_6.50-18570_amd64.deb
# 32 бита
dpkg -i storman_6.50-18570_i386.deb

Отключаем stor agent и выключаем его автозапуск:
/etc/init.d/stor_agent stop
update-rc.d -f stor_agent remove

Также ставим библиотеку, необходимую для работы arcconf:
apt-get install -y libstdc++5

Пробуем запустить arcconf:
/usr/StorMan/arcconf getversion 1
Controllers found: 1
Controller #1
==============
Firmware : 5.2-0 (17899)
Staged Firmware : 5.2-0 (17899)
BIOS : 5.2-0 (17899)
Driver : 1.1-5 (2461)
Boot Flash : 5.2-0 (17899)


Command completed successfully.

Возможно ли использование сторонних SSD носителей для подключения к Adaptec MaxIQ кэшу?

Да, если у Вас Adaptec контроллер Q серии (модели начального уровня стоят от $400).

Источник: база знаний Adaptec.

Что будет с данными, если вдруг откажет MaxIQ SSD кэш диск?

Ничего!

With MaxIQ, all the data gets first written to the RAID rotating media, protecting the data in case the SSD cache pool fails.

(с) http://www.adaptec.com/en-US/products/CloudComputing/MaxIQ/SSD-Cache-Performance/_resources/SSD_FAQs.htm?nc=/en-US/products/CloudComputing/MaxIQ/SSD-Cache-Performance/_resources/SSD_FAQs.htm

MaxIQ: ускорение работы массива за счет использования адаптивного кэша на SSD

Крайне крутая технология от Adaptec - позволяет без серьезных изменений в конфигурации ускорить существующие RAID массивы за счет кэша на SSD: http://www.adaptec.com/en-US/products/CloudComputing/MaxIQ/

Но можно ли использовать сторонние SSD для этого? Ответ читайте здесь: http://phpsuxx.blogspot.com/2010/10/ssd-adaptec-maxiq.html

Какое ускорение MaxIQ дает для веб-сервера? Ссылка

Какое ускорение MaxIQ дает для MySQL ? Ссылка