From: Oleg Drokin <green@namesys.com>
To: "S. Alexander Jacobson" <alex@shop.com>
Cc: reiserfs-list@namesys.com
Subject: Re: duplicate files and recent changes
Date: Thu, 6 Jun 2002 13:25:05 +0400 [thread overview]
Message-ID: <20020606132505.A2647@namesys.com> (raw)
In-Reply-To: <Pine.WNT.4.43.0206060328570.1296-100000@fanatic>
Hello!
On Thu, Jun 06, 2002 at 03:33:17AM -0400, S. Alexander Jacobson wrote:
> > Hm, you mean, each time you create a file, reiserfs should scan all
> > other files and see if there is exactly a file like you just wrote?
> > Hm, even something more complicated as you are writing to a file in
> > 4k chunks.
> > Definitely no.
> I could imagine a cheaper implementation in which
> the fs computes an MD5 hash of each file as it is
> being written. If the hash matches the
> pre-existing hash of some other file, then
> consolidate.
But MD5 may be identical for different files.
Also this buys you nothing.
You write file in chunks, once file is identical to other file,
one of the files deleted. Looks like just more extra work (but some saved space
of course).
> > > 2. Is there a fast way to get access to the file
> > > change list? It would be nice to be able to do
> > > fast backup of changed files without having to
> > > traverse entire directory trees.
> > No.
> I would presume that journalling gives access to
> this sort of recent information. It is really a
No. All kinds of metadata is journaled. Also it is possible to get
in situation where file was modified, but not journaled, because
no metadata changed. (mmaped writes coming to mind).
Also journal is not infinite, it is only 32M long.
And I presume you want some kind of info like "what have changed since
week ago".
Journal well might be overwritten many times since then.
Bye,
Oleg
next prev parent reply other threads:[~2002-06-06 9:25 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 5:30 duplicate files and recent changes S. Alexander Jacobson
2002-06-06 5:45 ` Oleg Drokin
2002-06-06 7:20 ` Robert Brockway
2002-06-06 7:40 ` S. Alexander Jacobson
2002-06-06 7:50 ` Hans Reiser
2002-06-06 7:33 ` S. Alexander Jacobson
2002-06-06 9:25 ` Oleg Drokin [this message]
2002-06-06 13:58 ` Valdis.Kletnieks
2002-06-06 17:51 ` Hubert Chan
2002-06-07 8:11 ` The Amazing Dragon
2002-06-07 15:55 ` Hubert Chan
2002-06-06 7:47 ` Hans Reiser
2002-06-06 13:54 ` Valdis.Kletnieks
2002-06-07 8:53 ` Heinz-Josef Claes
2002-06-08 12:50 ` Debian User
2002-06-08 12:47 ` Hans Reiser
2002-06-08 13:04 ` Joe Cooper
2002-06-09 12:17 ` Heinz-Josef Claes
2002-06-09 14:30 ` Heinz-Josef Claes
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:54 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 18:14 ` S. Alexander Jacobson
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 18:28 ` Richard Thornton
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 13:58 Valdis.Kletnieks
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 17:51 Hubert Chan
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:14 S. Alexander Jacobson
2002-06-06 18:28 Richard Thornton
2002-06-06 18:28 Richard Thornton
2002-06-06 18:28 Richard Thornton
2002-06-07 4:57 ` Oleg Drokin
2002-06-06 18:28 Richard Thornton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020606132505.A2647@namesys.com \
--to=green@namesys.com \
--cc=alex@shop.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.