From: Ireneusz P. <ip...@wp...> - 2010-06-15 06:28:02
|
Hello, as I find from docs and the mailing list there is already support for LSI MegaRaid, with "-d megaraid" option. However this is true for Linux only. Is there any hope to have that in FreeBSD soon? Is this difficult to be implemented? Thanks Irek. |
From: Alex K. <ad...@li...> - 2010-06-29 16:02:39
|
15.06.2010 10:27, Ireneusz Pluta пишет: > Hello, > > as I find from docs and the mailing list there is already support for > LSI MegaRaid, with "-d megaraid" option. However this is true for Linux > only. > Is there any hope to have that in FreeBSD soon? > Is this difficult to be implemented? > it's really needed feature we have servers with MegaRaid controllers, but cannot monitoring smart status disks on it |
From: Christian F. <Chr...@t-...> - 2010-06-30 14:54:11
|
Alex Keda wrote: > 15.06.2010 10:27, Ireneusz Pluta пишет: > >> Hello, >> >> as I find from docs and the mailing list there is already support for >> LSI MegaRaid, with "-d megaraid" option. However this is true for Linux >> only. >> Is there any hope to have that in FreeBSD soon? >> Is this difficult to be implemented? >> >> > it's really needed feature > we have servers with MegaRaid controllers, but cannot monitoring smart > status disks on it > > Of course it makes sense to add this feature. Please open a new ticket if possible. One problem might be that the contributors to the smartmontools FreeBSD code don't have access to MegaRaid controllers. Does the FreeBSD MegaRaid driver provide passthrough I/O-controls similar to Linux (see megaraid.h: MEGAIOCCMD, MEGASAS_IOC_FIRMWARE) ? Thanks, Christian |
From: Ireneusz P. <ip...@wp...> - 2010-06-30 15:24:19
|
Christian Franke pisze: > Does the FreeBSD MegaRaid driver provide passthrough I/O-controls similar to Linux (see megaraid.h: MEGAIOCCMD, MEGASAS_IOC_FIRMWARE) ? > actually, yes, and I initially missed that possibility. The mfip device bundled with the main mfi(4) is the clue used by /dev/pass*. I found accidentally this link http://old.nabble.com/how-to-create-pass-devices-without-reboot--td27045949.html and it helped me with what I wanted. It may be necessary to update mfi driver to what is in newer freebesd releases, as I found in svn log something dealing with interoperability of mfip with mfi depending on whether they run as loadable kernel modules or as compiled in kernel. Here is how it works: [root@myhost]# kldstat | grep mfi && ls -l /dev/mfi* /dev/pass* && mfiutil show config && for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15; do smartctl -a /dev/pass${i}; done | grep -A2 "INFORMATION SECTION" 4 2 0xffffffff80e23000 f440 mfi.ko 5 1 0xffffffff80e33000 22b8 mfip.ko 6 1 0xffffffff80e36000 1270 mfi_linux.ko crw-r----- 1 root operator 0, 35 Jun 29 20:27 /dev/mfi0 crw-r----- 1 root operator 0, 115 Jun 29 23:08 /dev/mfid0 crw-r----- 1 root operator 0, 116 Jun 29 23:09 /dev/mfid0p1 crw------- 1 root operator 0, 120 Jun 29 20:27 /dev/pass0 crw------- 1 root operator 0, 121 Jun 29 20:27 /dev/pass1 crw------- 1 root operator 0, 130 Jun 29 20:27 /dev/pass10 crw------- 1 root operator 0, 131 Jun 29 20:27 /dev/pass11 crw------- 1 root operator 0, 132 Jun 29 20:27 /dev/pass12 crw------- 1 root operator 0, 133 Jun 29 20:27 /dev/pass13 crw------- 1 root operator 0, 134 Jun 29 20:27 /dev/pass14 crw------- 1 root operator 0, 135 Jun 29 20:27 /dev/pass15 crw------- 1 root operator 0, 122 Jun 29 20:27 /dev/pass2 crw------- 1 root operator 0, 123 Jun 29 20:27 /dev/pass3 crw------- 1 root operator 0, 124 Jun 29 20:27 /dev/pass4 crw------- 1 root operator 0, 125 Jun 29 20:27 /dev/pass5 crw------- 1 root operator 0, 126 Jun 29 20:27 /dev/pass6 crw------- 1 root operator 0, 127 Jun 29 20:27 /dev/pass7 crw------- 1 root operator 0, 128 Jun 29 20:27 /dev/pass8 crw------- 1 root operator 0, 129 Jun 29 20:27 /dev/pass9 mfi0 Configuration: 7 arrays, 1 volumes, 0 spares array 0 of 2 drives: drive 16 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2857138> SATA enclosure 1, slot 0 drive 17 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2862206> SATA enclosure 1, slot 1 array 1 of 2 drives: drive 18 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2863007> SATA enclosure 1, slot 2 drive 19 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2766651> SATA enclosure 1, slot 3 array 2 of 2 drives: drive 20 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2540132> SATA enclosure 1, slot 4 drive 21 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2860702> SATA enclosure 1, slot 5 array 3 of 2 drives: drive 22 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2807860> SATA enclosure 1, slot 6 drive 23 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2857164> SATA enclosure 1, slot 7 array 4 of 2 drives: drive 24 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2764110> SATA enclosure 2, slot 0 drive 25 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2857109> SATA enclosure 2, slot 1 array 5 of 2 drives: drive 26 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2766186> SATA enclosure 2, slot 2 drive 27 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2831901> SATA enclosure 2, slot 3 array 6 of 2 drives: drive 28 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2856642> SATA enclosure 2, slot 4 drive 29 ( 1863G) ONLINE <WDC WD2002FYPS-0 5G05 serial=WD-WCAVY2766250> SATA enclosure 2, slot 5 volume mfid0 (13T) RAID-10 64K OPTIMAL spans: array 0 array 1 array 2 array 3 array 4 array 5 array 6 === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2857138 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2862206 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2863007 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2766651 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2540132 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2860702 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2807860 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2857164 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2764110 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2857109 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2766186 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2831901 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2856642 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2766250 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2864791 -- === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2691574 |
From: Alex S. <ml...@os...> - 2010-08-17 20:00:43
|
On 06/15/2010 08:27 AM, Ireneusz Pluta wrote: > as I find from docs and the mailing list there is already support for > LSI MegaRaid, with "-d megaraid" option. However this is true for Linux > only. > Is there any hope to have that in FreeBSD soon? > Is this difficult to be implemented? > Its possible to implement, but i have no access to FreeBSD with installed megaraid (or Dell PERC) controller. This option works using ioctl on special file, created by linux driver. I don`t know if it is provided by FreeBSD driver, and if it is - if this ioctl is compatible. |
From: Ireneusz P. <ip...@wp...> - 2010-08-17 19:37:51
|
Alex Samorukov pisze: > On 06/15/2010 08:27 AM, Ireneusz Pluta wrote: >> as I find from docs and the mailing list there is already support for >> LSI MegaRaid, with "-d megaraid" option. However this is true for Linux >> only. >> Is there any hope to have that in FreeBSD soon? >> Is this difficult to be implemented? >> > Its possible to implement, but i have no access to FreeBSD with > installed megaraid (or Dell PERC) controller. > > This option works using ioctl on special file, created by linux > driver. I don`t know if it is provided by FreeBSD driver, and if it is > - if this ioctl is compatible. > Hey, it's already resolved, withoud a need of any core development, but instead with use of mfip passthrough driver and /dev/pass* device nodes: # kldstat | grep mfi 5 2 0xffffffff80e44000 f440 mfi.ko 6 1 0xffffffff80e54000 22b8 mfip.ko 7 1 0xffffffff80e57000 1270 mfi_linux.ko # smartctl -a /dev/pass0 smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 8.0-RELEASE-p3 amd64] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B1 Serial Number: WD-WCAVY2857138 Firmware Version: 04.05G05 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Aug 17 21:33:31 2010 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === ... and so on ... |