From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: aelder@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: XFS Filename Hash and metadump
Date: Tue, 5 Oct 2010 23:28:33 +0200 [thread overview]
Message-ID: <201010052328.34390@zmi.at> (raw)
In-Reply-To: <1286290547.1960.3.camel@doink>
[-- Attachment #1.1: Type: Text/Plain, Size: 1006 bytes --]
On Dienstag, 5. Oktober 2010 Alex Elder wrote:
> PS Two more observations:
> - There is really no need for the characters to be truly random.
> Making the generated name unique and different from the
> original is sufficient. So (with the exception of the last
> five bytes) we can select the characters however we like.
> They could be a sequential series of names, for example,
> rather than computing a random value for each.
I was thinking the same when reading your description. Why not simply
"number" the file names from 1 to whatever count of files/dirs there is
within that dir?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-05 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 14:55 XFS Filename Hash and metadump Alex Elder
2010-10-05 21:28 ` Michael Monnerie [this message]
2010-10-07 21:41 ` Alex Elder
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=201010052328.34390@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=aelder@sgi.com \
--cc=xfs@oss.sgi.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.