All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gmail.com>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Lilo requirements (Was: Re: Address space operations questions)
Date: Sun, 17 Apr 2005 22:21:04 +0200	[thread overview]
Message-ID: <8e70aacf0504171321331e44b9@mail.gmail.com> (raw)
In-Reply-To: <16980.60937.831029.982747@gargle.gargle.HOWL>

Thanks for your reply, I found the the following thing interesting on its own:

On 4/7/05, Nikita Danilov <nikita@clusterfs.com> wrote:
> Consider tools like LILO that want stable block numbers for certain
> files. In reiserfs (both v3 and v4) there is an ioctl that disables
> relocation for a given file. Besides, I do not think ->bmap() is useless
> even when block numbers are volatile, for one thing it allows user level
> to track how file is laid out (for example, to measure fragmentation).

I tried to google out what behaviour lilo requires filesystems to
exhibit without much success... is that information available
somnewhere I din't look? Is that simple enought to be explained here?

TIA

Martin

  reply	other threads:[~2005-04-17 20:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8e70aacf05032616151c958eed@mail.gmail.com>
2005-03-29 22:30 ` Address space operations questions Martin Jambor
2005-03-30 13:55   ` Nikita Danilov
2005-03-31 19:59     ` Bryan Henderson
2005-03-31 20:43       ` Zach Brown
2005-03-31 21:40         ` Bryan Henderson
2005-03-31 21:53           ` Trond Myklebust
2005-04-01  0:06             ` Bryan Henderson
2005-04-06 23:52     ` Martin Jambor
2005-04-07  8:23       ` Nikita Danilov
2005-04-17 20:21         ` Martin Jambor [this message]
2005-04-17 21:33           ` Lilo requirements (Was: Re: Address space operations questions) Nikita Danilov
2005-04-18 17:33             ` Bryan Henderson
2005-04-07 16:58       ` Address space operations - >bmap Bryan Henderson

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=8e70aacf0504171321331e44b9@mail.gmail.com \
    --to=jamborm@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nikita@clusterfs.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.