On Wednesday, 15 September, 2010, David Nicol wrote: > btrfs s ... is imprecise, as the operation isn't on a subvolume, but > on the fi where the s used to be but isn't any more.
ok > > With your approval I'll go with "filesystem garbage-collection" which > can be abbrevd to > > btrfs fi g /butter 30000 || echo there should be some more space now \ > but it would have taken more than 30 sec to clean it all > > and in some imaginary future might trigger something instead of simply > waiting for something. I don't like too much "garbage-collector". It seems that you can start a "garbage collector". Instead we wait the finish of the garbage collector activity. I would like also to have the option to wait in "btrfs subvolume delete" # btrfs subvolume delete --wait /path/to/subvolume (instead of "--wait", we can use "--sync"...) In any case could you highlight the behavior of your ioctl when two snapshot deletions are performed. Does the ioctl wait the end of both the snapshot deletion ? Regards G.Baroncelli -- gpg key@ keyserver.linux.it:Goffredo Baroncelli (ghigo) <kreijackATinwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
