LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 09-16-2015, 03:13 AM   #1
Sidus
LQ Newbie
 
Registered: Apr 2014
Posts: 4

Rep: Reputation: Disabled
MDADM recovery issue


Hi all,

Need some help here. I'm running an LVM on an MDADM array and everything works fine for the most part. I've got a scheduled task to do a SMART scan once a day to detect drive failures, and ironically the scan seems to CAUSE one of the drives to fall out of sync every now an then.

But this question is not about the cause of these failures (I'm not 100 yet that it is the scan causing it).

My problem is that I cannot remotely recover from the failure. The RAID enters degraded state and the system stays up, but any attempt to access or re-add the drive locks up the system. "reboot -f" also fails to reboot the system. The only way for me to repair the system is to pull the power manually.

Once it comes back, a simple "mdmadm /dev/mdX -a /dev/sdXY" gets me back. I've searched the logs, but I may need some help finding the relevant log file and/or entries. So far I've got this:

Code:
Sep 16 06:54:48 jericho kernel: [414152.868020] ata16: EH in SWNCQ mode,QC:qc_active 0x200 sactive 0x200
Sep 16 06:54:48 jericho kernel: [414152.869854] ata16: SWNCQ:qc_active 0x200 defer_bits 0x0 last_issue_tag 0x9
Sep 16 06:54:48 jericho kernel: [414152.869854]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Sep 16 06:54:48 jericho kernel: [414152.873548] ata16: ATA_REG 0x40 ERR_REG 0x0
Sep 16 06:54:48 jericho kernel: [414152.875366] ata16: tag : dhfis dmafis sdbfis sactive
Sep 16 06:54:48 jericho kernel: [414152.876937] ata16: tag 0x9: 0 0 0 1
Sep 16 06:54:48 jericho kernel: [414152.878304] ata16.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x6 frozen
Sep 16 06:54:48 jericho kernel: [414152.879687] ata16.00: failed command: WRITE FPDMA QUEUED
Sep 16 06:54:48 jericho kernel: [414152.881052] ata16.00: cmd 61/08:48:10:20:00/00:00:00:00:00/40 tag 9 ncq 4096 out
Sep 16 06:54:48 jericho kernel: [414152.881052]          res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 06:54:48 jericho kernel: [414152.883757] ata16.00: status: { DRDY }
Sep 16 06:54:48 jericho kernel: [414152.885148] ata16: hard resetting link
Sep 16 06:54:48 jericho kernel: [414152.885150] ata16: nv: skipping hardreset on occupied port
Sep 16 06:54:48 jericho kernel: [414153.352026] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:54:53 jericho kernel: [414158.360024] ata16.00: qc timeout (cmd 0x27)
Sep 16 06:54:53 jericho kernel: [414158.360029] ata16.00: failed to read native max address (err_mask=0x4)
Sep 16 06:54:53 jericho kernel: [414158.360031] ata16.00: HPA support seems broken, skipping HPA handling
Sep 16 06:54:53 jericho kernel: [414158.360034] ata16.00: revalidation failed (errno=-5)
Sep 16 06:54:53 jericho kernel: [414158.361854] ata16: hard resetting link
Sep 16 06:54:53 jericho kernel: [414158.361856] ata16: nv: skipping hardreset on occupied port
Sep 16 06:54:54 jericho kernel: [414158.828023] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:54:54 jericho kernel: [414158.852140] ata16.00: configured for UDMA/133
Sep 16 06:54:54 jericho kernel: [414158.852149] ata16: EH complete
Sep 16 06:55:25 jericho kernel: [414189.860022] ata16: EH in SWNCQ mode,QC:qc_active 0x400 sactive 0x400
Sep 16 06:55:25 jericho kernel: [414189.861848] ata16: SWNCQ:qc_active 0x400 defer_bits 0x0 last_issue_tag 0xa
Sep 16 06:55:25 jericho kernel: [414189.861848]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Sep 16 06:55:25 jericho kernel: [414189.865497] ata16: ATA_REG 0x40 ERR_REG 0x0
Sep 16 06:55:25 jericho kernel: [414189.867300] ata16: tag : dhfis dmafis sdbfis sactive
Sep 16 06:55:25 jericho kernel: [414189.869099] ata16: tag 0xa: 0 0 0 1
Sep 16 06:55:25 jericho kernel: [414189.870854] ata16.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x6 frozen
Sep 16 06:55:25 jericho kernel: [414189.872556] ata16.00: failed command: WRITE FPDMA QUEUED
Sep 16 06:55:25 jericho kernel: [414189.873888] ata16.00: cmd 61/08:50:10:20:00/00:00:00:00:00/40 tag 10 ncq 4096 out
Sep 16 06:55:25 jericho kernel: [414189.873888]          res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 06:55:25 jericho kernel: [414189.876558] ata16.00: status: { DRDY }
Sep 16 06:55:25 jericho kernel: [414189.877934] ata16: hard resetting link
Sep 16 06:55:25 jericho kernel: [414189.877935] ata16: nv: skipping hardreset on occupied port
Sep 16 06:55:25 jericho kernel: [414190.344027] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:55:25 jericho kernel: [414190.368137] ata16.00: configured for UDMA/133
Sep 16 06:55:25 jericho kernel: [414190.368147] ata16: EH complete
Sep 16 06:55:56 jericho kernel: [414220.900021] ata16: EH in SWNCQ mode,QC:qc_active 0x800 sactive 0x800
Sep 16 06:55:56 jericho kernel: [414220.901867] ata16: SWNCQ:qc_active 0x800 defer_bits 0x0 last_issue_tag 0xb
Sep 16 06:55:56 jericho kernel: [414220.901867]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Sep 16 06:55:56 jericho kernel: [414220.905559] ata16: ATA_REG 0x40 ERR_REG 0x0
Sep 16 06:55:56 jericho kernel: [414220.907393] ata16: tag : dhfis dmafis sdbfis sactive
Sep 16 06:55:56 jericho kernel: [414220.909225] ata16: tag 0xb: 0 0 0 1
Sep 16 06:55:56 jericho kernel: [414220.911028] ata16.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x6 frozen
Sep 16 06:55:56 jericho kernel: [414220.912861] ata16.00: failed command: WRITE FPDMA QUEUED
Sep 16 06:55:56 jericho kernel: [414220.914671] ata16.00: cmd 61/08:58:10:20:00/00:00:00:00:00/40 tag 11 ncq 4096 out
Sep 16 06:55:56 jericho kernel: [414220.914671]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 06:55:56 jericho kernel: [414220.917807] ata16.00: status: { DRDY }
Sep 16 06:55:56 jericho kernel: [414220.919174] ata16: hard resetting link
Sep 16 06:55:56 jericho kernel: [414220.919175] ata16: nv: skipping hardreset on occupied port
Sep 16 06:55:56 jericho kernel: [414221.384027] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:55:56 jericho kernel: [414221.408140] ata16.00: configured for UDMA/133
Sep 16 06:55:56 jericho kernel: [414221.408145] ata16.00: device reported invalid CHS sector 0
Sep 16 06:55:56 jericho kernel: [414221.408153] ata16: EH complete
Sep 16 06:56:27 jericho kernel: [414251.876022] ata16: EH in SWNCQ mode,QC:qc_active 0x1000 sactive 0x1000
Sep 16 06:56:27 jericho kernel: [414251.877863] ata16: SWNCQ:qc_active 0x1000 defer_bits 0x0 last_issue_tag 0xc
Sep 16 06:56:27 jericho kernel: [414251.877863]   dhfis 0x0 dmafis 0x0 sdbfis 0x0
Sep 16 06:56:27 jericho kernel: [414251.881533] ata16: ATA_REG 0x40 ERR_REG 0x0
Sep 16 06:56:27 jericho kernel: [414251.883350] ata16: tag : dhfis dmafis sdbfis sactive
Sep 16 06:56:27 jericho kernel: [414251.885165] ata16: tag 0xc: 0 0 0 1
Sep 16 06:56:27 jericho kernel: [414251.886937] ata16.00: NCQ disabled due to excessive errors
Sep 16 06:56:27 jericho kernel: [414251.886940] ata16.00: exception Emask 0x0 SAct 0x1000 SErr 0x0 action 0x6 frozen
Sep 16 06:56:27 jericho kernel: [414251.888633] ata16.00: failed command: WRITE FPDMA QUEUED
Sep 16 06:56:27 jericho kernel: [414251.889996] ata16.00: cmd 61/08:60:10:20:00/00:00:00:00:00/40 tag 12 ncq 4096 out
Sep 16 06:56:27 jericho kernel: [414251.889996]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 06:56:27 jericho kernel: [414251.892710] ata16.00: status: { DRDY }
Sep 16 06:56:27 jericho kernel: [414251.894036] ata16: hard resetting link
Sep 16 06:56:27 jericho kernel: [414251.894037] ata16: nv: skipping hardreset on occupied port
Sep 16 06:56:27 jericho kernel: [414252.360025] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:56:27 jericho kernel: [414252.400142] ata16.00: configured for UDMA/133
Sep 16 06:56:27 jericho kernel: [414252.400147] ata16.00: device reported invalid CHS sector 0
Sep 16 06:56:27 jericho kernel: [414252.400154] ata16: EH complete
Sep 16 06:56:58 jericho kernel: [414282.852027] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 16 06:56:58 jericho kernel: [414282.853822] ata16.00: failed command: WRITE DMA
Sep 16 06:56:58 jericho kernel: [414282.855596] ata16.00: cmd ca/00:08:10:20:00/00:00:00:00:00/e0 tag 13 dma 4096 out
Sep 16 06:56:58 jericho kernel: [414282.855596]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 06:56:58 jericho kernel: [414282.859189] ata16.00: status: { DRDY }
Sep 16 06:56:58 jericho kernel: [414282.860838] ata16: hard resetting link
Sep 16 06:56:58 jericho kernel: [414282.860839] ata16: nv: skipping hardreset on occupied port
Sep 16 06:56:58 jericho kernel: [414283.328024] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:56:58 jericho kernel: [414283.352140] ata16.00: configured for UDMA/133
Sep 16 06:56:58 jericho kernel: [414283.352145] ata16.00: device reported invalid CHS sector 0
Sep 16 06:56:58 jericho kernel: [414283.352152] ata16: EH complete
Sep 16 06:57:29 jericho kernel: [414313.828030] ata16: limiting SATA link speed to 1.5 Gbps
Sep 16 06:57:29 jericho kernel: [414313.828035] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 16 06:57:29 jericho kernel: [414313.829842] ata16.00: failed command: WRITE DMA
Sep 16 06:57:29 jericho kernel: [414313.831644] ata16.00: cmd ca/00:08:10:20:00/00:00:00:00:00/e0 tag 14 dma 4096 out
Sep 16 06:57:29 jericho kernel: [414313.831644]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 06:57:29 jericho kernel: [414313.835296] ata16.00: status: { DRDY }
Sep 16 06:57:29 jericho kernel: [414313.837123] ata16: hard resetting link
Sep 16 06:57:29 jericho kernel: [414313.837126] ata16: nv: skipping hardreset on occupied port
Sep 16 06:57:29 jericho kernel: [414314.304029] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 06:57:29 jericho kernel: [414314.328139] ata16.00: configured for UDMA/133
Sep 16 06:57:29 jericho kernel: [414314.328144] ata16.00: device reported invalid CHS sector 0
Sep 16 06:57:29 jericho kernel: [414314.328153] sd 8:0:0:0: [sdc] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 16 06:57:29 jericho kernel: [414314.328156] sd 8:0:0:0: [sdc] Sense Key : Aborted Command [current] [descriptor]
Sep 16 06:57:29 jericho kernel: [414314.328159] sd 8:0:0:0: [sdc] Add. Sense: No additional sense information
Sep 16 06:57:29 jericho kernel: [414314.328161] sd 8:0:0:0: [sdc] CDB:
Sep 16 06:57:29 jericho kernel: [414314.328163] Write(10): 2a 00 00 00 20 10 00 00 08 00
Sep 16 06:57:29 jericho kernel: [414314.328171] blk_update_request: I/O error, dev sdc, sector 8208
Sep 16 06:57:29 jericho kernel: [414314.329585] blk_update_request: I/O error, dev sdc, sector 8208
Sep 16 06:57:29 jericho kernel: [414314.330926] md: super_written gets error=-5, uptodate=0
Sep 16 06:57:29 jericho kernel: [414314.330929] md/raid:md127: Disk failure on sdc1, disabling device.
Sep 16 06:57:29 jericho kernel: [414314.330929] md/raid:md127: Operation continuing on 3 devices.
Sep 16 06:57:29 jericho kernel: [414314.333578] ata16: EH complete
Sep 16 06:57:29 jericho kernel: [414314.373252] RAID conf printout:
Sep 16 06:57:29 jericho kernel: [414314.373257]  --- level:5 rd:4 wd:3
Sep 16 06:57:29 jericho kernel: [414314.373260]  disk 0, o:1, dev:sdd1
Sep 16 06:57:29 jericho kernel: [414314.373262]  disk 1, o:1, dev:sdb1
Sep 16 06:57:29 jericho kernel: [414314.373264]  disk 2, o:0, dev:sdc1
Sep 16 06:57:29 jericho kernel: [414314.373266]  disk 3, o:1, dev:sdf1
Sep 16 06:57:29 jericho kernel: [414314.380018] RAID conf printout:
Sep 16 06:57:29 jericho kernel: [414314.380020]  --- level:5 rd:4 wd:3
Sep 16 06:57:29 jericho kernel: [414314.380023]  disk 0, o:1, dev:sdd1
Sep 16 06:57:29 jericho kernel: [414314.380025]  disk 1, o:1, dev:sdb1
Sep 16 06:57:29 jericho kernel: [414314.380027]  disk 3, o:1, dev:sdf1
Sep 16 07:00:05 jericho kernel: [414469.860026] ata16.00: limiting speed to UDMA/100:PIO4
Sep 16 07:00:05 jericho kernel: [414469.860030] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 16 07:00:05 jericho kernel: [414469.861715] ata16.00: failed command: FLUSH CACHE EXT
Sep 16 07:00:05 jericho kernel: [414469.863353] ata16.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 15
Sep 16 07:00:05 jericho kernel: [414469.863353]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 16 07:00:05 jericho kernel: [414469.866547] ata16.00: status: { DRDY }
Sep 16 07:00:05 jericho kernel: [414469.868102] ata16: hard resetting link
Sep 16 07:00:05 jericho kernel: [414469.868104] ata16: nv: skipping hardreset on occupied port
Sep 16 07:00:05 jericho kernel: [414470.336034] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 07:00:05 jericho kernel: [414470.360140] ata16.00: configured for UDMA/100
Sep 16 07:00:05 jericho kernel: [414470.360144] ata16.00: retrying FLUSH 0xea Emask 0x4
Sep 16 07:00:20 jericho kernel: [414485.360021] ata16.00: qc timeout (cmd 0xea)
Sep 16 07:00:20 jericho kernel: [414485.360027] ata16.00: FLUSH failed Emask 0x4
Sep 16 07:00:20 jericho kernel: [414485.360031] ata16: hard resetting link
Sep 16 07:00:20 jericho kernel: [414485.360034] ata16: nv: skipping hardreset on occupied port
Sep 16 07:00:21 jericho kernel: [414485.828025] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 07:00:21 jericho kernel: [414485.852139] ata16.00: configured for UDMA/100
Sep 16 07:00:21 jericho kernel: [414485.852143] ata16.00: retrying FLUSH 0xea Emask 0x4
Sep 16 07:00:36 jericho kernel: [414500.852020] ata16.00: qc timeout (cmd 0xea)
Sep 16 07:00:36 jericho kernel: [414500.852025] ata16.00: FLUSH failed Emask 0x4
Sep 16 07:00:36 jericho kernel: [414500.852029] ata16.00: limiting speed to UDMA/100:PIO3
Sep 16 07:00:36 jericho kernel: [414500.852034] ata16: hard resetting link
Sep 16 07:00:36 jericho kernel: [414500.852036] ata16: nv: skipping hardreset on occupied port
Sep 16 07:00:36 jericho kernel: [414501.320024] ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 16 07:00:36 jericho kernel: [414501.344138] ata16.00: configured for UDMA/100
Sep 16 07:00:36 jericho kernel: [414501.344142] ata16.00: retrying FLUSH 0xea Emask 0x4
Sep 16 07:01:06 jericho kernel: [414531.344021] ata16.00: qc timeout (cmd 0xea)
Sep 16 07:01:06 jericho kernel: [414531.344026] ata16.00: FLUSH failed Emask 0x4
Sep 16 07:01:06 jericho kernel: [414531.344029] ata16.00: disabled
Sep 16 07:01:06 jericho kernel: [414531.344036] ata16.00: device reported invalid CHS sector 0
Sep 16 07:01:06 jericho kernel: [414531.344043] ata16: hard resetting link
Sep 16 07:01:07 jericho kernel: [414532.224025] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 16 07:01:07 jericho kernel: [414532.224040] ata16: EH complete
Sep 16 07:01:07 jericho kernel: [414532.224059] blk_update_request: I/O error, dev sdc, sector 0
Sep 16 07:01:07 jericho kernel: [414532.225326] sd 8:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 16 07:01:07 jericho kernel: [414532.225328] sd 8:0:0:0: [sdc] Sense not available.
Sep 16 07:01:07 jericho kernel: [414532.225349] sd 8:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 16 07:01:07 jericho kernel: [414532.225351] sd 8:0:0:0: [sdc] Sense not available.
So, any advice on (best case) recovering without rebooting the system? Or, failing that, how to restart the system without physically having to pull the power?

Last edited by Sidus; 09-16-2015 at 03:16 AM.
 
Old 09-16-2015, 10:01 AM   #2
smallpond
Senior Member
 
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: CentOS 6 & 7
Posts: 3,025

Rep: Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806Reputation: 806
SMART can be configured to be non-intrusive. It is probably a good idea not to automatically run the drives self-tests, though. This may be the cause of one problem.

Some drive/controller combinations work well with NCQ and some do not. Try disabling that and see if it helps. Kernel command line parameter is

Code:
libata.force=noncq
 
Old 09-16-2015, 10:51 AM   #3
Sidus
LQ Newbie
 
Registered: Apr 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
Thanks, I'll run with that setting and see if it improves.

I've found that SMART on it's own hardly ever lets me know about a failure in advance. My script runs the offline/long tests and extracts the parameters from the report. These help me see gradual decay much earlier. See a few lines of my history tracking:

Code:
                     R   S   S   R   S   P   S   P   R   E   R   C   H   A   T   H   C   O   U   H   T   T  
                     a   p   t   e   e   o   p   o   u   n   e   o   i   i   e   a   u   f   D   e   o   o  
                     w   i   a   a   e   w   i   w   n   d   p   m   g   r   m   r   r   f   M   a   t   t  
                     .   n   r   l   k   e   n   e   t   -   o   m   h   f   p   d   r   l   A   d   a   a  
                     R   .   t   l   .   r   .   r   i   t   r   a   .   l   e   w   e   i   .   .   l   l  
                     e   U   .   o   E   .   R   .   m   o   t   n   F   o   r   a   n   n   C   F   .   .  
                     a   p   S   c   r   O   e   C   e   -   e   d   l   w   a   r   t   e   R   l   L   L  
                     d   .   t   a   r   n   t   y   .   E   d   .   y   .   t   e   .   .   C   y   B   B  
                     .   T   o   t   o   .   r   c   B   n   .   T   .   T   u   .   P   U   .   i   A   A  
                     E   i   p   e   r   H   y   l   a   d   U   i   W   e   r   E   e   n   E   n   s   s  
                     r   m   .   d   .   o   .   e   d   .   n   m   r   m   e   C   n   c   r   g   .   .  
                     r   e   C   .   R   u   C   .   .   E   c   e   i   p   .   C   d   o   r   .   W   R  
                     o       o   S   a   r   o   C   B   r   o   o   t   e   C   .   i   r   o   H   r   e  
                     r       u   e   t   s   u   o   l   r   r   u   e   r   e   R   n   r   r   o   i   a  
                     .       n   c   e       n   u   o   o   r   t   s   a   l   e   g   e   .   u   t   d  
                     R       t   t           t   n   c   r   e           t   s   c   .   c   C   r   t      
                     a           o               t   k       c           u   i   o   S   t   o   s   e      
                     t           r                           t           r   u   v   e   a   u       n      
                     e           .                                       e   s   e   c   b   n              
                                 C                                       .       r   t   l   t              
                                 t                                       C       e   o   e                  
                                                                         e       d   r                      
                                                                         l                                  
                    --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
15-01-27 18:10:40 S 102 098 100 100 073 095 100 100 099 100 100 100 100 059 041 036 100 100 200 100 100 100 
15-01-28 00:01:16 S 104 098 100 100 073 095 100 100 099 100 100 100 100 059 041 037 100 100 200 100 100 100 
15-01-28 06:20:03 O 105 098 100 100 073 095 100 100 099 100 100 100 100 061 039 038 100 100 200 100 100 100 
15-01-28 12:20:03 O 108 098 100 100 073 095 100 100 099 100 100 100 100 060 040 038 100 100 200 100 100 100 
15-01-28 18:20:03 O 108 098 100 100 073 095 100 100 099 100 100 100 100 060 040 035 100 100 200 100 100 100 
15-01-29 00:01:15 S 108 098 100 100 073 095 100 100 099 100 100 100 100 060 040 033 100 100 200 100 100 100 
15-01-29 06:20:03 O 109 098 100 100 073 095 100 100 099 100 100 100 100 061 039 034 100 100 200 100 100 100
I've defined reasonable parameters, and once the script sees degradation, I get an email notice. Works pretty well, except that right now I'm causing more downtime than I'm saving...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Raid 5 - mdadm - superblock recovery - please help! pasha_suse Linux - Server 3 06-11-2010 02:42 PM
mdadm RAID 0 Recovery? romeo_tango Linux - Hardware 11 06-10-2010 09:19 PM
mdadm raid 5 recovery / reassemble Ciesko Linux - Server 1 04-15-2010 01:53 PM
mdadm - Recovery bibble_235 Linux - Hardware 3 01-06-2010 04:04 PM
RAID10 Recovery Issue - mdadm segfault marc2112 Linux - Server 2 02-15-2009 09:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 10:49 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration