Re: [gentoo-user] OT: Fighting bit rot

On Jan 9, 2013 2:06 AM, "Florian Philipp" wrote: > > Am 08.01.2013 18:41, schrieb Pandu Poluan: > > > > On Jan 8, 2013 11:20 PM, "Florian Philipp" > > wrote: > >> > > > > -- snip -- > > > [...] > >> > >> When you have completely static content, md5sum, rsync and frie

Re: [gentoo-user] OT: Fighting bit rot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/08/2013 02:27 AM, Florian Philipp wrote: > As I said above, the point is that I need to detect the error as > long as I still have a valid backup. Professional archive solutions > do this on their own but I'm looking for something suitable for >

Re: [gentoo-user] OT: Fighting bit rot

On Tue, 08 Jan 2013 20:06:25 +0100 Florian Philipp wrote: > Am 08.01.2013 18:35, schrieb Volker Armin Hemmann: > > Am Dienstag, 8. Januar 2013, 08:27:51 schrieb Florian Philipp: > >> Am 08.01.2013 00:20, schrieb Alan McKinnon: > >>> On Mon, 07 Jan 2013 21:11:35 +0100 > >>> > >>> Florian Philipp

Re: [gentoo-user] OT: Fighting bit rot

On Tue, Jan 8, 2013 at 2:06 PM, Florian Philipp wrote: > Am 08.01.2013 18:35, schrieb Volker Armin Hemmann: >> Am Dienstag, 8. Januar 2013, 08:27:51 schrieb Florian Philipp: >>> Am 08.01.2013 00:20, schrieb Alan McKinnon: On Mon, 07 Jan 2013 21:11:35 +0100 Florian Philipp wrote: >>

Re: [gentoo-user] OT: Fighting bit rot

Am 08.01.2013 18:35, schrieb Volker Armin Hemmann: > Am Dienstag, 8. Januar 2013, 08:27:51 schrieb Florian Philipp: >> Am 08.01.2013 00:20, schrieb Alan McKinnon: >>> On Mon, 07 Jan 2013 21:11:35 +0100 >>> >>> Florian Philipp wrote: Hi list! I have a use case where I am seriously co

Re: [gentoo-user] OT: Fighting bit rot

Am 08.01.2013 18:41, schrieb Pandu Poluan: > > On Jan 8, 2013 11:20 PM, "Florian Philipp" > wrote: >> > > -- snip -- > [...] >> >> When you have completely static content, md5sum, rsync and friends are >> sufficient. But if you have content that changes from time t

Re: [gentoo-user] OT: Fighting bit rot

On Jan 8, 2013 11:20 PM, "Florian Philipp" wrote: > -- snip -- > > Hmm, good idea, albeit similar to the `md5sum -c`. Either tool leaves > you with the problem of distinguishing between legitimate changes (i.e. > a user wrote to the file) and decay. > > When you have completely static content, m

Re: [gentoo-user] OT: Fighting bit rot

Am Dienstag, 8. Januar 2013, 08:27:51 schrieb Florian Philipp: > Am 08.01.2013 00:20, schrieb Alan McKinnon: > > On Mon, 07 Jan 2013 21:11:35 +0100 > > > > Florian Philipp wrote: > >> Hi list! > >> > >> I have a use case where I am seriously concerned about bit rot [1] > >> and I thought it migh

Re: [gentoo-user] OT: Fighting bit rot

On Tue, 08 Jan 2013 17:16:32 +0100 Florian Philipp wrote: > Am 08.01.2013 08:55, schrieb Alan McKinnon: > > On Tue, 08 Jan 2013 08:27:51 +0100 > > Florian Philipp wrote: > > > [...] > >> > >> As I said above, the point is that I need to detect the error as > >> long as I still have a valid back

Re: [gentoo-user] OT: Fighting bit rot

Am 08.01.2013 08:55, schrieb Alan McKinnon: > On Tue, 08 Jan 2013 08:27:51 +0100 > Florian Philipp wrote: > [...] >> >> As I said above, the point is that I need to detect the error as long >> as I still have a valid backup. Professional archive solutions do >> this on their own but I'm looking f

Re: [gentoo-user] OT: Fighting bit rot

On Tue, 08 Jan 2013 08:27:51 +0100 Florian Philipp wrote: > > This is a filesystem task, not a cronjab task. Use a filesystem that > > does proper checksumming. ZFS does it, but that is of course > > somewhat problematic on Linux. Check out the others, it will be > > something modern you need, li

Re: [gentoo-user] OT: Fighting bit rot

Am 08.01.2013 00:20, schrieb Alan McKinnon: > On Mon, 07 Jan 2013 21:11:35 +0100 > Florian Philipp wrote: > >> Hi list! >> >> I have a use case where I am seriously concerned about bit rot [1] >> and I thought it might be a good idea to start looking for it in my >> own private stuff, too. [...]

Re: [gentoo-user] OT: Fighting bit rot

On 08/01/13 04:11, Florian Philipp wrote: > Hi list! > > I have a use case where I am seriously concerned about bit rot [1] and I > thought it might be a good idea to start looking for it in my own > private stuff, too. > > Solving the problem is easy enough: > - Record checksums and timestamps f

Re: [gentoo-user] OT: Fighting bit rot

On Mon, 07 Jan 2013 21:11:35 +0100 Florian Philipp wrote: > Hi list! > > I have a use case where I am seriously concerned about bit rot [1] > and I thought it might be a good idea to start looking for it in my > own private stuff, too. > > Solving the problem is easy enough: > - Record checksum

Re: [gentoo-user] OT: Fighting bit rot

Am 07.01.2013 22:33, schrieb Michael Mol: > On Mon, Jan 7, 2013 at 3:11 PM, Florian Philipp wrote: >> Hi list! >> >> I have a use case where I am seriously concerned about bit rot [1] and I >> thought it might be a good idea to start looking for it in my own >> private stuff, too. >>[...] >> The o

Re: [gentoo-user] OT: Fighting bit rot

Am 07.01.2013 22:07, schrieb Paul Hartman: > On Mon, Jan 7, 2013 at 2:11 PM, Florian Philipp wrote: >> Hi list! >> >> I have a use case where I am seriously concerned about bit rot [1] and I >> thought it might be a good idea to start looking for it in my own >> private stuff, too. >> >> Solving t

Re: [gentoo-user] OT: Fighting bit rot

On Mon, Jan 7, 2013 at 3:11 PM, Florian Philipp wrote: > Hi list! > > I have a use case where I am seriously concerned about bit rot [1] and I > thought it might be a good idea to start looking for it in my own > private stuff, too. > > Solving the problem is easy enough: > - Record checksums and

Re: [gentoo-user] OT: Fighting bit rot

On Mon, Jan 7, 2013 at 2:11 PM, Florian Philipp wrote: > Hi list! > > I have a use case where I am seriously concerned about bit rot [1] and I > thought it might be a good idea to start looking for it in my own > private stuff, too. > > Solving the problem is easy enough: > - Record checksums and

[gentoo-user] OT: Fighting bit rot

Hi list! I have a use case where I am seriously concerned about bit rot [1] and I thought it might be a good idea to start looking for it in my own private stuff, too. Solving the problem is easy enough: - Record checksums and timestamps for each file - Check and update records via cronjob - If c