Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Younger Liu <younger.liu@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Why ocfs2 haven't implemented "steal" for local_alloc system files?
Date: Sat, 27 Jul 2013 18:27:29 +0800	[thread overview]
Message-ID: <51F3A091.4090605@huawei.com> (raw)

Hi,
  While analyzing ocfs2 block allocation, I found:
  When claiming space from inode_alloc (or extent_alloc) system files, 
if there is no enough space in inode_alloc (or extent_alloc) and 
global_bitmap, it could steal space from other slots.
  But when claiming space from local_alloc system files, and no 
enough space in local_alloc and global_bitmap, it returns -ENOSPC.

  Why ocfs2 haven't implemented "steal" for local_alloc system files?
  Is there any some reasons?

             reply	other threads:[~2013-07-27 10:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 10:27 Younger Liu [this message]
2013-08-01  3:33 ` [Ocfs2-devel] Why ocfs2 haven't implemented "steal" for local_alloc system files? Sunil Mushran
2013-08-01  7:20   ` Joel Becker
2013-08-01  8:38     ` Younger Liu
2013-08-01 16:49       ` Sunil Mushran
2013-08-01 18:57       ` Srinivas Eeda
2013-08-02  9:47         ` Younger Liu

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=51F3A091.4090605@huawei.com \
    --to=younger.liu@huawei.com \
    --cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox