Date: Sat, 11 Jul 2009 16:37:20 -0400 From: Steve Bertrand <steve@ibctech.ca> To: xorquewasp@googlemail.com Cc: freebsd-questions@freebsd.org Subject: Re: ZFS scrub is finished? Message-ID: <4A58F800.4090501@ibctech.ca> In-Reply-To: <20090711202553.GA38156@logik.internal.network> References: <20090711161132.GA74849@logik.internal.network> <4A58E314.4040808@ibctech.ca> <20090711202553.GA38156@logik.internal.network>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
xorquewasp@googlemail.com wrote:
> On 2009-07-11 15:08:04, Steve Bertrand wrote:
>> Perhaps it is as simple as cron-ing something like the following (of
>> course, replace "zpool scrub" with my cat commands.
> Problem is that 'zpool scrub' immediately returns with a success
> error code if command line option parsing went OK and the specified
> pools actually exist. You have to manually check the output of 'zpool status'
> to see if the scrub executed with no errors (and that may be hours
> later).
Ok. What is your ultimate goal? Is it to:
- run the first scrub
- search for an "ok" err status upon return
- begin the second scrub
If (in your case) the first scrub fails, is it still feasible to run the
second scrub anyway? If it is, then chaining the commands together
*should* work (however, I've never tested whether '&&' will continue
upon certain 'failures', but so long as the first command _exits_, you
should be alright).
If your X doesn't finish correctly, and then you can't run Y because of
it, what would you be looking for in the following manual output to
signify error?
%zpool status
pool: storage
state: ONLINE
scrub: scrub completed after 2h50m with 0 errors on Thu Jul 9 11:56:39
2009
config:
NAME STATE READ WRITE CKSUM
storage ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ad0 ONLINE 0 0 0
ad2 ONLINE 0 0 0
ad4 ONLINE 0 0 0
ad6 ONLINE 0 0 0
errors: No known data errors
Steve
ps. I use ZFS in a limited capacity... I'm just trying to help write a
wrapper if one doesn't currently exist.
[-- Attachment #2 --]
0 *H
010 + 0 *H
00CK9AbxIUw0
*H
0b10 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
090507231610Z
100507231610Z0B10UThawte Freemail Member10 *H
steve@ibctech.ca0"0
*H
0
DZ杙<2IⵀfrsE6q?0.>
S@Œ!V?A\Q
r-aZ
Ōf/0{OYQhɏߴ
F_\Q0BF=<_.a*3epeY|t ݼcvlҷ+@piQA{2E9WN4[Z`h6VM/zPbd(G C^K6XV4j<t -0+0U0steve@ibctech.ca0U0 0
*H
æ|85aQz-*3HG .s*Fw*`HvFw;9ytƘn0taC/:WC+LÙ{Oq 1 n00CK9AbxIUw0
*H
0b10 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
090507231610Z
100507231610Z0B10UThawte Freemail Member10 *H
steve@ibctech.ca0"0
*H
0
DZ杙<2IⵀfrsE6q?0.>
S@Œ!V?A\Q
r-aZ
Ōf/0{OYQhɏߴ
F_\Q0BF=<_.a*3epeY|t ݼcvlҷ+@piQA{2E9WN4[Z`h6VM/zPbd(G C^K6XV4j<t -0+0U0steve@ibctech.ca0U0 0
*H
æ|85aQz-*3HG .s*Fw*`HvFw;9ytƘn0taC/:WC+LÙ{Oq 1 n0?0
0
*H
010 UZA10UWestern Cape10U Cape Town10U
Thawte Consulting1(0&UCertification Services Division1$0"UThawte Personal Freemail CA1+0) *H
personal-freemail@thawte.com0
030717000000Z
130716235959Z0b10 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00
*H
0 Ħ<UsUNʙZhup[v:aQP
0cZ,p+Z?qV˯<6$*+w=+>@dקe*TH<a@dr` 00U0 0CU<0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0U0)U"0 010UPrivateLabel2-1380
*H
HP.
fgCL!6-6/P p<ab:~ t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$F]_eO1d0`0v0b10 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAK9AbxIUw0 + 0 *H
1 *H
0 *H
1
090711203720Z0# *H
1onJ}=w%
u0R *H
1E0C0
*H
0*H
0
*H
@0+0
*H
(0 +71x0v0b10 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAK9AbxIUw0*H
1xv0b10 UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAK9AbxIUw0
*H
U(_[$)id95;~ұ*ټAXq&GRY/+jU0=&?
(46BaBu&T:ݽsfN¡Mn&HRh s?1<r
D|h@]`~
xSwV(6"༮e1i7g$ɯe
6uJ۸
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A58F800.4090501>
