> Neil,
>
> So in his case, is there anyway to determine which files are potentially
> corrupted?
I'd like to know that, too...
--
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d--(+)@ s-:+ a- C UL++ P+>++ L+++> E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(+
On Tue, 6 Mar 2007, Dexter Filmore wrote:
xerxes:/sys/block/md0/md# cat mismatch_cnt
147248
Need to worry?
If you have a swap file on this array, then that could explain it, so
don't worry.
Nope, swap is not on the array.
Couple of loops tho.
If not... maybe worry?
I assume you did a '
> > xerxes:/sys/block/md0/md# cat mismatch_cnt
> > 147248
> > Need to worry?
>
> If you have a swap file on this array, then that could explain it, so
> don't worry.
Nope, swap is not on the array.
Couple of loops tho.
>
> If not... maybe worry?
>
> I assume you did a 'check' or 'repair' before l
On Tuesday March 6, [EMAIL PROTECTED] wrote:
> So I practiced what I learned today and scrubbed the array.
> Getting this:
>
> xerxes:/sys/block/md0/md# cat mismatch_cnt
> 147248
>
> 4x 250GB Samsung sATA, smartctl says all fine.
>
> Need to worry?
>
If you have a swap file on this array, then
So I practiced what I learned today and scrubbed the array.
Getting this:
xerxes:/sys/block/md0/md# cat mismatch_cnt
147248
4x 250GB Samsung sATA, smartctl says all fine.
Need to worry?
--
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d--(+)@ s-:+ a- C UL++ P+>++ L+++> E-- W++ N o
