Thanks - have run it and returns pretty quickly. Given the output (attached)
what action can I take?
Thanks
James
--
This message posted from opensolaris.orgDirty time logs:
tank
outage [300718,301073] length 356
outage [301138,301139] length 2
outage [301149,30
On Mon, 29 Mar 2010, Jim wrote:
Thanks for the suggestion, but have tried detaching but it refuses
reporting no valid replicas. Capture below.
Could you run 'zdb -ddd tank | | awk '/^Dirty/ {output=1} /^Dataset/ {output=0}
{if (output) {print}}'
This will print the dirty time log of the pool
Thanks for the suggestion, but have tried detaching but it refuses reporting no
valid replicas. Capture below.
C3P0# zpool status
pool: tank
state: DEGRADED
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
tank DEGRADED 0 0 0
raidz1 DEGRADED 0 0 0
ad4 ONLINE 0 0 0
ad6 ONLINE 0 0 0
repla
Thanks for the suggestion, but have tried detaching but it refuses reporting no
valid replicas. Capture below.
C3P0# zpool status
pool: tank
state: DEGRADED
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
tank DEGRADED
On Mon, 29 Mar 2010, Victor Latushkin wrote:
On Mar 29, 2010, at 1:57 AM, Jim wrote:
Yes - but it does nothing. The drive remains FAULTED.
Try to detach one of the failed devices:
zpool detach tank 4407623704004485413
As Victor says, the detach should work. This is a known issue and I'
On Mar 29, 2010, at 1:57 AM, Jim wrote:
> Yes - but it does nothing. The drive remains FAULTED.
Try to detach one of the failed devices:
zpool detach tank 4407623704004485413
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opens
Yes - but it does nothing. The drive remains FAULTED.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On 03/29/10 10:31 AM, Jim wrote:
I had a drive fail and replaced it with a new drive. During the resilvering
process the new drive had write faults and was taken offline. These faults were
caused by a broken SATA cable (drive checked with Manufacturers software and
all ok). New cable fixed the
I had a drive fail and replaced it with a new drive. During the resilvering
process the new drive had write faults and was taken offline. These faults were
caused by a broken SATA cable (drive checked with Manufacturers software and
all ok). New cable fixed the the failure. However, now the driv
