All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	Matt Stegman <matts@ksu.edu>,
	reiserfs-list@namesys.com
Subject: Re: reiser4 metas/bmap problem
Date: Sat, 31 Jul 2004 15:43:50 +0400	[thread overview]
Message-ID: <410B85F6.8010107@namesys.com> (raw)
In-Reply-To: <410A955D.3030101@namesys.com>

Hello

Hans Reiser wrote:
> Vladimir V. Saveliev wrote:
> 
>> Hello
>>
>> Hans Reiser wrote:
>>
>>> Andreas Dilger wrote:
>>>
>>>>
>>>>
>>>> The ext3_bmap() function flushes all file data to disk when called, 
>>>> and it
>>>> would be prudent to do the same with reiser4, since bmap users tend 
>>>> to be
>>>> important and not speed critical (e.g. lilo) and failing to do so 
>>>> can mean
>>>> not booting later.
>>>>  
>>>>
>>> Interesting point.  vs, please comment.
>>>
>> Yes, reiser4 might do something like that too. However, i am not sure 
>> how we can prevent relocation for files which were bmap-ed.
>>
>>>
>>>
>>
>>
>>
>>
> fsync first and then bmap?
> 
> 

It file will be later overwritten - flush may decide to relocate it.
So, if application which bmapped it will not re-bmap - there will be a confusion.

We need some way to mark file non-relocatable.


  parent reply	other threads:[~2004-07-31 11:43 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 [this message]
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
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=410B85F6.8010107@namesys.com \
    --to=vs@namesys.com \
    --cc=adilger@clusterfs.com \
    --cc=matts@ksu.edu \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@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.