Oh, it should say retryable and normal write errors - I have permanent
errors too
/Martin
On 2 apr 2008, at 00:55, Richard Elling wrote:
Martin Englund wrote:
I've got a newly created zpool where I know (from the previous UFS)
that one of the disks has retryable write errors.
What
I've got a newly created zpool where I know (from the previous UFS) that one of
the disks has retryable write errors.
What should I do about it now? Just leave zfs to deal with it? Repair it?
If I should repair, if this procedure ok?
zpool offline z2 c5t4d0
format -d c5t4d0
repair ...
zpool
I replaced a failed disk today, and while the resilvering was running the
system crashed. Once the server was back up the resilvering continued, but
after it completed it is still in degraded mode:
weblogs # zpool status
pool: storage
state: DEGRADED
scrub: resilver completed with 0 errors
Answering my own post :)
I ran zpool scrub which solved it:
weblogs # zpool status
pool: storage
state: ONLINE
scrub: resilver completed with 0 errors on Fri Mar 7 16:01:08 2008
config:
NAMESTATE READ WRITE CKSUM
storage ONLINE 0 0 0
postings about Drobo on the web, including:
http://www.engadget.com/2007/04/09/drobo-the-worlds-first-storage-robot/
---8---
cheers,
/Martin
--
Martin Englund, Java Security Engineer, Java SE, Sun Microsystems Inc.
Email: [EMAIL PROTECTED] Time Zone: GMT+2 PGP: 1024D/AA514677
The question is not if you
