Dave Cecil wrote:
>
> Daniel,
>
> >Here's the proposed mount-time tailmerging algorithm which was originally
> >posted as an attachment summarizing a series of emails between me and Stephen
> >Tweedie on this subject:
> >---
>
> [snip]
>
> first of all I admit to on
On Tue, 01 Aug 2000, Chris Mason wrote:
> On 8/1/00, 2:45:11 PM, Daniel Phillips <[EMAIL PROTECTED]>
> > writing past tail?
> > if so, unmerge tail block
> > generic file write
>
> > additions to write full page:
> > (within the per-buffer write)
> > is the file tailmerged?
> >
Daniel,
>Here's the proposed mount-time tailmerging algorithm which was originally
>posted as an attachment summarizing a series of emails between me and Stephen
>Tweedie on this subject:
>---
[snip]
first of all I admit to only just joining this list and consequentl
On Tue, 01 Aug 2000, Andreas Dilger wrote:
> You never mention what happens when a file doesn't have a tail yet,
> but then gets one...
Every file has a tail, unless it is exactly some number of blocks long. The
tail is the part at the end that doesn't fill a block completely. In my
terminolo
Chris Mason wrote:
> For reading the tail, take a look at how these functions interact:
>
> get_block
> generic_file_read
> block_read_full_page (ext2's readpage func)
>
> Putting the tail knowledge into ext2_file_read won't be enough, it won't
> cover mmaps. You have to make sure your readpage
