On Feb 20, 2007, at 10:43 AM, [EMAIL PROTECTED] wrote:
If you run a 'zpool scrub preplica-1', then the persistent error log
will be cleaned up. In the future, we'll have a background scrubber
to make your life easier.
eric
Eric,
Great news! Are there any details about how thi
>
> If you run a 'zpool scrub preplica-1', then the persistent error log
> will be cleaned up. In the future, we'll have a background scrubber
> to make your life easier.
>
> eric
Eric,
Great news! Are there any details about how this will be implemented
yet? I am most curious to ho
On Feb 18, 2007, at 9:19 PM, Davin Milun wrote:
I have one that looks like this:
pool: preplica-1
state: ONLINE
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. Otherwi
I have one that looks like this:
pool: preplica-1
state: ONLINE
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
entire pool from backup.
s
Russell Blaine wrote:
The zdb object -> path trick doesn't give me a path name:
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
13 a51blvl=0 blkid=9
objectsbash-3.00# zdb -vvv mypool/rab a51b
Try 0xa51b.
--matt
The zdb object -> path trick doesn't give me a path name:
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
13 a51blvl=0 blkid=9
bash-3.00# zdb mypool | grep "ID 19,"
Dataset mypool/rab [ZPL], ID 19, cr_txg 6, last_txg 4391649, 80.3
