-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question on --device parameter #40
Comments
Hi @ubenmackin TBH, I don't know the expected results :P I opened this bug #12 to validate the behaviour with RAID setup. Let me check them
Right, this is the ideal case, just passing the mount and let the tool to determine the devices. I need to re-work on this tool. |
I did quick test on RAID10. Below are the results. In short, you can use any one of the disk with
Try running it with
hopefully it show display matched chunks. You can also use
|
My BTRFS setup is RAID10, so I don't have a single device tied to my BTRFS array. I wasn't sure what I am supposed to pass in this case. Do I just pass in any device that is part of the array for the file/folder I am trying to dedupe?
For example, if I want to dedupe everything in '/mnt/ddimages', and that is part of a BTRFS pool that is comprised of 4 disks:
/dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
Would I use the command:
dduper --device /dev/sda --dir /mnt/ddimages
Will that work as expected? Or will it somehow only dedupe the files that BTRFS has stored on /dev/sda? Do I then need to run the command 4 times, once for each device?
I guess my question is why do we need to specify --device at all? Isn't that something that can be determined based on the mount that holds the file/folders specified?
The text was updated successfully, but these errors were encountered: