Request for opinions - gvinum or ccd?

krad kraduk at googlemail.com
Tue Jun 2 08:52:21 UTC 2009


" You need to write a program that will just rewrite all files to make
this."

No you don't you just make sure you scrub the pools regularly once a week
for instance. This way you will hopefully see small block error way before
you have a full drive failure.  

At the end of the day if the data is super critical to you then you should
follow best practices and build an array with sufficient amount of
redundancy in for you needs.

If you cant justify getting 4+ drives to build a raidz2 or raid 10 type
scenario then the data on said array cant actually be worth much itself,
therefore I might be annoying but in the whole scale of things not that
costly if you loose it. If it were you would do thing properly in the first
place



-----Original Message-----
From: Wojciech Puchar [mailto:wojtek at wojtek.tensor.gdynia.pl] 
Sent: 01 June 2009 16:50
To: krad
Cc: 'Mike Meyer'; freebsd-hackers at freebsd.org; xorquewasp at googlemail.com
Subject: RE: Request for opinions - gvinum or ccd?

> Its all done on write, so if you update the file it will have multiple
> copies again

what is exactly what i said in the beginning.



More information about the freebsd-hackers mailing list