[Noisebridge-discuss] [RUG] Data integrity, SMART and SSD's
Jason Dusek
jason.dusek at gmail.com
Mon Dec 14 02:20:42 UTC 2009
2009/12/12 John Magolske <listmail at b79.net>:
> I'm a bit concerned about keeping the primary repository of a
> collection of data on a CF card. If some cells fail on read (is that
> possible? or do they only fail on write?) and that is rsync'd to an
> external hard-drive target, what are the chances those errors will
> be propagated without being detected? In general, what would be some
> recommended tools & strategies to ensure ongoing data integrity?
It is very important to have a few backups -- snapshots from
times past. A corrupted cell is not the only way to get an
rsync backup that is broken, after all. If you only have one
and you don't check it's integrity, you can easily find
yourself in a situation where you backup, trash something
important and then lose your drive -- leaving you with no good
copies.
Maybe `rdiff-backup` is just the thing?
http://rdiff-backup.nongnu.org/
I never back anything up since I store all my stuff in `git`
anyways; but going through the add/commit/comment/push cycle
for images or music is hard to motivate.
--
Jason Dusek
More information about the Noisebridge-discuss
mailing list