Closed ytrezq closed 11 years ago
The second possibility wouldn't work well in all cases (bedup does scans at the volume level, scanning a single directory might not work well if the directory is very large like /usr). I'll probably deal with these by adding nicer error messages.
Thanks, I was also wondering if it could inpact that the volume in the example have the problem in #15.(sorry for the cross-post) But the feature I was talking about would make btrfs scaning at directory level if the path on cmd lead to a directory.
this would be nice if you have a separate temporary directory and you want the backups (1000's) it countains doesn't share the same sectors on disk.
It seems that bedup doesn't evaluate if the path are rights
step to reproduce: start bedup with an incorrect path to volume examples: case where the direcory is not a btrfs filesystem:
case of a normal directory in a btrfs filesystem:
expected operations: for the first case, the program should report that the path doesn't lead to a btrfs filesystem in any way.
In the secound case, dedup could detect the root directory (real one or subvolume) and redirect the commande to it. A secound possibilty would be to add a feature that would deduplicate the files only in the directory (copy of files with originals in the directory, located outside of it, wouldn' be deduplicated) wether this a subvolume or not.