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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
