From: Chris Mason <chris.mason@oracle.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
"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 16:44:20 -0400 [thread overview]
Message-ID: <1303764241-sup-9810@think> (raw)
In-Reply-To: <1303751742-sup-4551@think>
Excerpts from Chris Mason's message of 2011-04-25 13:15:58 -0400:
> Excerpts from Li Zefan's message of 2011-04-25 04:57:47 -0400:
> > 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.
>
> Great, is this pullable from somewhere?
Sorry, you did send the link in a later email. This is the first thing
in my .40 tree.
-chris
next prev parent reply other threads:[~2011-04-25 20:44 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 ` [PATCH v2 0/7] Btrfs: New inode number allocator Li Zefan
2011-04-25 17:15 ` Chris Mason
2011-04-25 20:44 ` Chris Mason [this message]
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=1303764241-sup-9810@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).