SW RAID

Milan Roubal roubm9am na barbora.ms.mff.cuni.cz
Středa Leden 15 17:31:51 CET 2003


je to v RAIDu, normalne ho to odpojilo a pripojilo
hot-spare disk, jak poznam jestli linux keca a nebo
ten disk skutecne miri do vecnych lovist? Kdyz se neco
podobneho objevilo posledne a linux mi odpojil jinej disk,
tak jsem to projel checkerem od vyrobce a nic zleho nenasel.
Ten disk se pak vratil do masiny a bezi dodnes.

 # smartctl -a /dev/hdc
Device: WDC WD1200JB-75CRA0  Supports ATA Version 5
Drive supports S.M.A.R.T. and is enabled
Check S.M.A.R.T. Passed

General Smart Values:
Off-line data collection status: (0x00) Offline data collection activity was
     never started

Total time to complete off-line
data collection:     (   0) Seconds

Offline data collection
Capabilities:       (0x00)     Off-line data collection not supported

Smart Capablilities:           (0x0000) automatic saving of SMART data
is not implemented

Error logging capability:        (0x00) Error logging NOT supported

Vendor Specific SMART Attributes with Thresholds:
Revision Number: 0
Attribute                    Flag     Value Worst Threshold Raw Value
Device does not support Error Logging
Device does not support Self Test Logging

Zdravi
    Milan Roubal

----- Original Message -----
From: "Dan Ohnesorg" <dan na fel.cvut.cz>
To: <linux na linux.cz>
Sent: Wednesday, January 15, 2003 4:50 PM
Subject: Re: SW RAID


On Wed, 15 Jan 2003, Milan Roubal wrote:

> Ted koukam ze pri posledni chybe uz to nehlasi lost interrupt, ale zacalo
to
> hlasit toto:
>
> hdc: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> blk: queue c03f1430, I/O limit 4095Mb (mask 0xffffffff)
> hdc: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdc: status timeout: status=0xd0 { Busy }
> hdc: drive not ready for command
> ide1: reset timed-out, status=0xd0
> hdc: status timeout: status=0xd0 { Busy }
> hdc: drive not ready for command
> ide1: reset timed-out, status=0xd0
>
> lost interrupt to hazelo historicky jak jsem ted zjistil z logu.
> hodnoty v interrupts i ioprocs vypadaji vcelku normalne...
> Dokazes jeste vysvetlit co presne mysli kernel tema timeoutama?
> kde bych mel pokracovat v reseni dal? protoze po tomhle se to nestydi a
> odpoji to harddisk.

Ten disk je na 99% nekolik hodin pred smrti, zalohuj, zalohuj, zalohuj,
dokud je cas.

zdravim
dan





Další informace o konferenci Linux