From: Li Zefan <lizf@cn.fujitsu.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] Btrfs: New inode number allocator
Date: Mon, 25 Apr 2011 17:02:21 +0800 [thread overview]
Message-ID: <4DB5389D.6040006@cn.fujitsu.com> (raw)
In-Reply-To: <4DB5378B.2070904@cn.fujitsu.com>
Li Zefan wrote:
> 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 32bits 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.
>
> More testing is appreciated!
>
> Changelog v2:
>
> - Rebased against latest btrfs-unstable tree
> - Fixed several small bugs.
>
This patchset is also available here:
git://repo.or.cz/linux-btrfs-devel.git ino-alloc
next prev parent reply other threads:[~2011-04-25 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 8:57 [PATCH v2 0/7] Btrfs: New inode number allocator Li Zefan
2011-04-25 8:58 ` [PATCH v2 2/7] Btrfs: Use bitmap_set/clear() Li Zefan
2011-04-25 8:59 ` [PATCH v2 3/7] Btrfs: Make free space cache code generic Li Zefan
2011-04-25 8:59 ` [PATCH v2 4/7] Btrfs: Cache free inode numbers in memory Li Zefan
2011-04-25 8:59 ` [PATCH v2 5/7] Btrfs: Make the code for reading/writing free space cache generic Li Zefan
2011-04-25 8:59 ` [PATCH v2 6/7] Btrfs: Always use 64bit inode number Li Zefan
2011-04-25 9:00 ` [PATCH v2 7/7] Btrfs: Support reading/writing on disk free ino cache Li Zefan
2011-04-25 9:02 ` Li Zefan [this message]
2011-04-25 17:15 ` [PATCH v2 0/7] Btrfs: New inode number allocator Chris Mason
2011-04-25 20:44 ` Chris Mason
2011-05-31 21:01 ` Johannes Hirte
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=4DB5389D.6040006@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.