On Thu, 23 Oct 2014 17:44:46 +0200 > Piotr Pawłow <pp@xxxxxxxxxxx> wrote: > >> On 23.10.2014 16:24, Roman Mamedov wrote: >>> I was under impression that the "Transaction commit:" setting in 'btrfs sub >>> del' finally allows us to make it not return until all free space from the >>> snapshots that are being deleted, is completely freed up. >> >> This is not what "commit-each" or "commit-after" options do. These are >> only to make sure, that the deletion is commited and the subvolume >> doesn't reappear after a crash. > > But is that not already ensured by a regular 'sync', or 'btrfs fi sync’? They could have same effects.. but doing ’sync’ is much more heavy than options.. > >> You probably want "subvolume sync" command, introduced in btrfs-progs 3.17: >> >> btrfs subvolume sync <path> [<subvol-id>...] >> Wait until given subvolume(s) are completely removed from the >> filesystem. > > Oh right, *that*'s the one I was thinking of. > > -- > With respect, > Roman > -- > 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 Best Regards, Wang Shilong -- 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
