From: "daniel.poelzleithner" <poelzi@poelzi.org>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
Matt Stegman <matts@ksu.edu>,
reiserfs-list@namesys.com
Subject: Re: reiser4 metas/bmap problem
Date: Fri, 30 Jul 2004 04:30:20 +0200 [thread overview]
Message-ID: <4109B2BC.4040600@poelzi.org> (raw)
In-Reply-To: <4108B029.4030008@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vladimir V. Saveliev wrote:
| reiser4 should do the same, i agree. However, reiser4 has another
| feature we call relocation (flush may allocate another disk blocks for a
| file if it finds it more optimal) which is undesirable for bmapped files.
| We will probably have to invent some woraround for that.
Whats about a flag that can be set through metas, that will prevent the
relocation ?
That would be no workaround, that would be a feature :)
regards
~ Daniel
- --
Once the philosopher stone has fallen from the tree,
~ nonsense appeared to fix the courious fear.
.. . .. ... . . .. . ... . .. . ... . . .
pgp key @ http://files.poelzi.org/pgp.txt
ED80 E53D 5269 4BB1 1E73 3A53 CBF9 A421 0A7B 003D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBCbK8y/mkIQp7AD0RAtdYAJ4nvuykJ/jt22xaab8BWfnY1qSXzQCeO31N
O/J1M9fctbmDK3SiX/Ac7IE=
=wK7J
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-30 2:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 23:26 reiser4 metas/bmap problem Matt Stegman
2004-07-29 1:25 ` Andreas Dilger
2004-07-29 7:41 ` Hans Reiser
2004-07-29 7:48 ` Vladimir V. Saveliev
2004-07-30 18:37 ` Hans Reiser
2004-07-30 19:26 ` Andreas Dilger
2004-07-31 11:43 ` Vladimir V. Saveliev
2004-07-31 17:08 ` Christophe Saout
2004-08-01 12:18 ` Vladimir V. Saveliev
2004-07-29 8:07 ` Vladimir V. Saveliev
2004-07-30 2:30 ` daniel.poelzleithner [this message]
2004-07-30 2:42 ` Andreas Dilger
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=4109B2BC.4040600@poelzi.org \
--to=poelzi@poelzi.org \
--cc=adilger@clusterfs.com \
--cc=matts@ksu.edu \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.