From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Bo Brantén" <bosse@acc.umu.se>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Question on how file tails are stored
Date: Mon, 13 Oct 2008 16:05:48 +0400 [thread overview]
Message-ID: <48F3399C.4000907@gmail.com> (raw)
In-Reply-To: <Pine.A41.4.64.0809131302350.548908@stalin.acc.umu.se>
Bo Brantén wrote:
>
> Hello,
Hello.
>
> I would like to ask you how file tails are stored on ReiserFs 3.6, am
> I right that they are stored as either one or two items but not more
> than two?
Yes, if you mean (default) "small" tail suppression policy.
Indeed, a data flow of size < blocksize can not be
split into more then 2 chunks, if you partition it by a lattice
which has a step == blocksize.
>
> Also I found this statement on the Internet:
>
> "If a tail is larger than the maximum size of a file that can fit into
> a formatted node but is smaller than the unformatted node size (4K),
> then it is stored in an unformatted node,
Right.
It fits perfectly the "small" policy .
> and a pointer to it plus a count of the space used is stored in an
> indirect item."
This looks like some not related calculation..
>
> Does this represent a third case not covered of what I said above, and
> if so how does one detect this case and find the tail data?
There is no special interfaces to access tail data.
You can try to parse debugreiserfs -d output..
Thanks,
Edward.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-13 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 0:03 rfsd 0.25.1 released Bo Brantén
2008-09-13 11:10 ` Question on how file tails are stored Bo Brantén
2008-10-13 12:05 ` Edward Shishkin [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=48F3399C.4000907@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=bosse@acc.umu.se \
--cc=reiserfs-devel@vger.kernel.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 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.