From: Paul Colquhoun <paulcol@andor.dropbear.id.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] File system meta-data indexer / checker
Date: Mon, 17 Jun 2013 17:42:25 +1000 [thread overview]
Message-ID: <8986052.mQYZKkbyGk@bluering> (raw)
In-Reply-To: <CA+Tk8fzFgKAJB422CKgCHTtXm56_qp8iR1aqte-03b6s-UvtWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
On Mon, 17 Jun 2013 00:14:17 Ciprian Dorin Craciun wrote:
> Hello all!
>
> While struggling with managing various old backups --- just
> imagine 10 or so copies of almost the same content, some with `rsync`,
> some with `rdiff-backup`, yet some others on plain ISO's, all over a
> range of a few years --- I stumbled upon the following missing piece
> in the Linux tools ecosystem: a file-system crawler that records
> **only** meta-data, like all the info available through `stat`, plus
> an assortment of hashes of the files (at least MD5 and SHA-1,2
> family), and optionally ACL's and extended attributes. Thus I was
> wondering if someone knows a tool that fits this description.
>
>
> I must say I've tried to do my homework, and below are a few tools
> that come close, but not quite...
>
> (A) `rdup` is probably the closest to what I'm searching. However
> there are a few issues:
> * it's output format is not very parsable, especially in cases
> like symlinks, and a few other special cases;
> * it doesn't escape the file names --- and from some reason I have
> files containing escape sequences in them...
> * it records only SHA-1;
> * it doesn't handle ACL's or extended attributes;
>
> (B) `mtree` from FreeBSD. I found two ports of it for Linux,
> however my main concern is how parsable is the output...
>
> (C) `md5deep` (or `sha*deep`), which only records the checksum not
> other meta-data.
>
>
> Thus, are there any other alternatives? (Just to be clear, I
> don't need a "backup" solution, just something to record file-system
> meta-data. Maybe a "meta-backup" solution... :) )
>
> Ciprian.
Have a look at 'tripwire'. It's primarily an intrusion detection tool, but it does the job
by recording file meta-data and checksums, then checking to see if they have
changed. I can't remember if it handles ACL's, as it's been a few years since I used it.
--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro
[-- Attachment #2: Type: text/html, Size: 9416 bytes --]
prev parent reply other threads:[~2013-06-17 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 21:14 [gentoo-user] File system meta-data indexer / checker Ciprian Dorin Craciun
2013-06-17 5:52 ` Florian Philipp
2013-06-17 6:00 ` Ciprian Dorin Craciun
2013-06-17 7:21 ` Peter Humphrey
2013-06-17 7:25 ` Ciprian Dorin Craciun
2013-06-17 15:56 ` Peter Humphrey
2013-06-17 16:40 ` Ciprian Dorin Craciun
2013-06-17 7:42 ` Paul Colquhoun [this message]
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=8986052.mQYZKkbyGk@bluering \
--to=paulcol@andor.dropbear.id.au \
--cc=gentoo-user@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox