From: Li Zefan <lizf@cn.fujitsu.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: [PATCH 0/7] Btrfs: New inode number allocator
Date: Wed, 16 Mar 2011 16:48:55 +0800 [thread overview]
Message-ID: <4D807977.1040506@cn.fujitsu.com> (raw)
Currently btrfs stores the highest objectid of the fs tree, and it always
returns (highest+1) inode number when we create a file, so inode numbers
won't be reclaimed when we delete files, so we'll run out of inode numbers
as we keep create/delete files in 32bit machines.
This patchset aims to fix this, and it works similar to free space caching
for block groups.
I've run xfstests, and I also tested it with snapshot, balance etc.
The patchset is also available in:
git://repo.or.cz/linux-btrfs-devel.git ino-alloc
---
fs/btrfs/btrfs_inode.h | 9 +
fs/btrfs/compression.c | 5 +-
fs/btrfs/ctree.h | 29 +-
fs/btrfs/disk-io.c | 19 +
fs/btrfs/export.c | 25 +-
fs/btrfs/extent-tree.c | 50 ++--
fs/btrfs/extent_io.c | 4 +-
fs/btrfs/file-item.c | 5 +-
fs/btrfs/file.c | 27 +-
fs/btrfs/free-space-cache.c | 873 ++++++++++++++++++++++++++-----------------
fs/btrfs/free-space-cache.h | 48 +++-
fs/btrfs/inode-map.c | 428 +++++++++++++++++++++-
fs/btrfs/inode-map.h | 13 +
fs/btrfs/inode.c | 282 ++++++++------
fs/btrfs/ioctl.c | 22 +-
fs/btrfs/relocation.c | 27 +-
fs/btrfs/transaction.c | 13 +-
fs/btrfs/tree-log.c | 58 ++--
fs/btrfs/xattr.c | 8 +-
19 files changed, 1352 insertions(+), 593 deletions(-)
next reply other threads:[~2011-03-16 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 8:48 Li Zefan [this message]
2011-03-16 8:49 ` [PATCH 1/7] Btrfs: Remove unused btrfs_block_group_free_space() Li Zefan
2011-03-16 8:49 ` [PATCH 2/7] Btrfs: Use bitmap_set/clear() Li Zefan
2011-03-16 8:50 ` [PATCH 3/7] Btrfs: Make free space cache code generic Li Zefan
2011-03-16 8:50 ` [PATCH 4/7] Btrfs: Cache free inode numbers in memory Li Zefan
2011-03-16 8:50 ` [PATCH 5/7] Btrfs: Make the code for reading/writing free space cache generic Li Zefan
2011-03-16 8:51 ` [PATCH 6/7] Btrfs: Always use 64bit inode number Li Zefan
2011-03-16 8:51 ` [PATCH 7/7] Btrfs: Support reading/writing on disk free ino cache Li Zefan
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=4D807977.1040506@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=linux-btrfs@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 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.