linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Koss <kossjan@gmail.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: kernelnewbies@nl.linux.org, linux-fsdevel@vger.kernel.org
Subject: Re: fragmentation && blocks "realloc"
Date: Mon, 23 Jan 2006 01:05:48 +0300	[thread overview]
Message-ID: <b97d23040601221405p228451a7n18c69780b8772710@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601222108070.17838@hermes-2.csi.cam.ac.uk>

On 1/23/06, Anton Altaparmakov <aia21@cam.ac.uk> wrote:
...
> Note that the buffers from the block device address space mapping are
> COMPLETELY separate from the buffers from a file inode address space
> mapping.  So writes from one are NOT seen in the other and you NEVER can
> mix the two forms of i/o and expect to have a working file system.  You
> will get random results and tons of weird data corruption that way.
>

Thanks a lot, this is clear for me several important things.

> That depends entirely in which function you are / which call path you are
> in at present.  Taking minix as an example, tell me the call path where
> you end up wanting to do the above and I will tell you where to get the bh
> from...  (-:
>

I told about 2.6.15.

in fs/minix/bitmap.c there is minix_new_block we come in it from get_block in
fs/minix/itree_common.c.

After analizing blocks<->file I want move some blocks to another location
and update page cache correspondingly, what should I do?

  reply	other threads:[~2006-01-22 22:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 11:47 fragmentation && blocks "realloc" Jan Koss
2006-01-20 13:34 ` Anton Altaparmakov
2006-01-20 15:46   ` Jan Koss
2006-01-20 19:22     ` Jan Koss
2006-01-20 20:11       ` Anton Altaparmakov
2006-01-21  9:42         ` Jan Koss
2006-01-21 20:28           ` Anton Altaparmakov
2006-01-22 20:58             ` Jan Koss
2006-01-22 21:32               ` Anton Altaparmakov
2006-01-22 22:05                 ` Jan Koss [this message]
2006-01-24 10:37                   ` Anton Altaparmakov
2006-02-23 21:47                     ` Nate Diller
2006-01-20 20:04     ` Anton Altaparmakov

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=b97d23040601221405p228451a7n18c69780b8772710@mail.gmail.com \
    --to=kossjan@gmail.com \
    --cc=aia21@cam.ac.uk \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).