On Sun, 2009-05-24 at 22:13 -0400, Matt McCutchen wrote:
> On Mon, 2009-05-25 at 10:09 +0800, Daniel.Li wrote:
> > On Mon, 2009-05-25 at 09:58 +0800, Daniel.Li wrote:
> > > What if a video editor?
> > >
> > > Lots of work with video files, which is very large, about 500MB per
> > > file. Editor on
On Mon, 2009-05-25 at 10:09 +0800, Daniel.Li wrote:
> On Mon, 2009-05-25 at 09:58 +0800, Daniel.Li wrote:
> > What if a video editor?
> >
> > Lots of work with video files, which is very large, about 500MB per
> > file. Editor only delete or rearrange frames in that file.
> >
> > And then it will
On Mon, 2009-05-25 at 09:58 +0800, Daniel.Li wrote:
> On Sun, 2009-05-24 at 16:04 +0200, Mac User FR wrote:
> > Hard-linking an
> > unchanged dir takes very few place.
>
> What if a video editor?
>
> Lots of work with video files, which is very large, about 500MB per
> file. Editor only delete
On Sun, 2009-05-24 at 16:04 +0200, Mac User FR wrote:
> Hard-linking an
> unchanged dir takes very few place.
What if a video editor?
Lots of work with video files, which is very large, about 500MB per
file. Editor only delete or rearrange frames in that file.
And then it will be back up 500MB
On Fri, 2009-05-22 at 22:06 +0800, Daniel.Li wrote:
> On Fri, 2009-05-22 at 13:10 +0200, Paul Slootman wrote:
> > On Fri 22 May 2009, Daniel.Li wrote:
> > > On Fri, 2009-05-22 at 10:47 +0200, Paul Slootman wrote:
> > > > >
> > > > > access("/home/admin/test",F_OK)
> > > > >
> > > > > Result: Fail
On Sun, May 24, 2009 at 06:32:40PM +0200, Christian Hecht wrote:
> Such a tool i plan to write for Mac OS X. The first time it should
> store checksums and mod times for all files to verify.
There are various patches in the "patches" dir that deal with cached
checksums in different ways:
- check
Am 24.05.2009 um 18:01 schrieb Daniel Carrera:
Jamie Lokier wrote:
Daniel Carrera wrote:
But there is no way to distinguish between file corruption and a
legitimate change. All you can do is keep old backups for a few
days or weeks and hope that you detect the file corruption before
the b
Daniel Carrera wrote:
> Jamie Lokier wrote:
> >Daniel Carrera wrote:
> >>But there is no way to distinguish between file corruption and a
> >>legitimate change. All you can do is keep old backups for a few days or
> >>weeks and hope that you detect the file corruption before the backup
> >>rotat
Jamie Lokier wrote:
Daniel Carrera wrote:
But there is no way to distinguish between file corruption and a
legitimate change. All you can do is keep old backups for a few days or
weeks and hope that you detect the file corruption before the backup
rotation deletes all the good copies.
I'm un
Daniel Carrera wrote:
> But there is no way to distinguish between file corruption and a
> legitimate change. All you can do is keep old backups for a few days or
> weeks and hope that you detect the file corruption before the backup
> rotation deletes all the good copies.
I'm under the impress
But there is no way to distinguish between file corruption and a
legitimate change. All you can do is keep old backups for a few days or
weeks and hope that you detect the file corruption before the backup
rotation deletes all the good copies.
Christian Hecht wrote:
This can minimize the risk
This can minimize the risk, but if you don't need the corrupted file
actually, you can't detect that it is corrupted.
The corrupted file will be copied to a newer backup folder.
If you delete the old backups due to rotation, at any time the backup
is worthless because it only contains the co
A simple way to prevent this is to store the backup with a rotating
system and hard-linking files.
You can do it with rsync --link-dest=DIR option and a post-exec script
that moves the backup dir to something like backup-200905241335
In this way if the file got corrupted it won't be hard-link
This will safe you if your file is corrupted on the backup side. Rsync
will copy it then again from the source because the checksum is
different and everything is okay.
But imagine the file is corrupted on the source side. Then rsync will
copy the corrupted file again and if you delete olde
14 matches
Mail list logo
