On Thu, Jun 20, 2013 at 2:42 PM, alessio wrote:
> Yes but... what disk? It is c6d0, I suppose, but why all disks are
> reported as degraded?
At a guess, since writes to a raidz vdev get striped across all component
disks, if it can't successfully reconstruct a block, it can't figure out
which
Yes but... what disk? It is c6d0, I suppose, but why all disks are reported as
degraded?
Christian Manal wrote:
>Am 20.06.2013 17:16, schrieb Alessio:
>> The result of the command "zpool status -v" is the following:
>>
>> pool: zpool_repos
>> state: DEGRADED
>> status: One or more devices
On 2013-06-20 19:30, Jonathan Adams wrote:
just an FYI, The disk may not be dead ... but you'll need to give it a low
level format and surface scan to check that it's not broken.
It might also be possible to invoke its own low-level diagnostics
scan via SMART interface (see smartctl; if OI var
just an FYI, The disk may not be dead ... but you'll need to give it a low
level format and surface scan to check that it's not broken.
On 20 June 2013 18:25, Christian Manal wrote:
> Am 20.06.2013 17:16, schrieb Alessio:
> > The result of the command "zpool status -v" is the following:
> >
>
>
Am 20.06.2013 17:16, schrieb Alessio:
> The result of the command "zpool status -v" is the following:
>
> pool: zpool_repos
> state: DEGRADED
> status: One or more devices has experienced an error resulting in data
> corruption. Applications may be affected.
> action: Restore the file
The result of the command "zpool status -v" is the following:
pool: zpool_repos
state: DEGRADED
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
