On Thu, Oct 01, 2015 at 04:19:55PM +0530, Chandan Rajendra wrote: > This occurs because, > > Mount filesystem > Create subvol with ID 257 > Unmount filesystem > Mount filesystem > Delete subvol with ID 257 > btrfs_drop_snapshot() > Add root corresponding to subvol 257 into > btrfs_transaction->dropped_roots list > Create new subvol (i.e. create_subvol()) > 257 is returned as the next free objectid How is this possible? We do not intentionally reuse the subvol ids so this means that the bug is in the id assignment code. > btrfs_read_fs_root_no_name() > Finds the btrfs_root instance corresponding to the old subvol with ID 257 > in btrfs_fs_info->fs_roots_radix. > Returns error since btrfs_root_item->refs has the value of 0. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
