vfsrecycle_kid

Gotcha. Thank you for all your info on the matter. The link/issue you referenced seems to display no real information for outside users (I see is it as a bunch of empty form fields). But good to know it is officially tracked. I'll be keeping a close eye on this issue . Thanks for all the quick responses. I see DrivePool in my future (parts for the NAS will arrive in the coming weeks!)

Once again thank you for the prompt reply. Really liking the support you guys are giving. I'm a dev myself so the technical insight is appreciated. Having said that. I now understand what your workaround is suggesting. However this doesn't actually apply to my usecase. To further expand here's the current (proposed) network structure: * NAS - Windows Server, SnapRAID + DrivePool * PC1 - Windows * PC2 - Windows * PCn - Windows/Android (Various via WiFi) I'm not concerned with a PC->NAS recycle bin (though I can appreciate that I may have been vague in my description, I'm still trying to figure out how to appropriately describe my setup). The only concern with this is PC1 and PC2 will be connecting to the NAS via SMB (the DrivePool will be set to Shared on the network) as a mapped network drive. They will be interacting with the device as if it was local. With the sole exception that only permanent deletes exist in SMB world, wherein lies the issue. -- The workaround I mentioned before is simply instead of deleting via SMB, create a folder in the DrivePool (lets call it "Trash" to mimic Greyhole's name). We move it to the Trash directory (which is just a normal folder, no special designation from the OS). Then, when I run my weekly SnapRAID scripts (which is run locally on the NAS): I can run something like del X:\Trash\*.* /s snapraid.exe sync pause # Simplified the snapraid stuff just for simplicity of the post # Where X is the DrivePool letter. -- Having said all of that. It does seem the end goal is something that is not currently offered in DrivePool. But it does offer 9/10ths of what I would like, and I cannot find another solution to this problem. In which case if the feature was to come into affect as a selectable option in the future for DrivePool, I think it would be fantastic. Snapshot based "RAID" adds a lot of value to a home redundancy solution, but it has some drawbacks. I do appreciate the that the feature is not widely request and do not hold any expectation for it to be implemented. If I've misinterpreted anything you've said @Drashna, do let me know . Thanks!

First of all thank you for your quick reply. That's awesome! I'm intrigued by your solution. I'm curious what that actually accomplishes. Before I ask about that I'll re-explain what I want. When deleting (which as you said is a permanent-delete) via SMB. I'd like files moved instead to a pooled "Recycle Bin". Then technically all that's needed to be done is when a permanent delete is desired, delete from the recycle bin. This is exactly how Greyhole does it. I think Greyhole does differentiate between a normal delete vs a SMB delete, which is what makes this work for them. However that is linux and does not apply to us unfortunately. -- So having said that, doesn't seem what I want is in DrivePool unless there was an option that added something along the lines of "Intercept delete request with a Move to Recycle Bin, unless you're deleting from Recycle Bin, in which case permanently delete". -- Back to your "workaround" steps. What exactly does this accomplish. So we set a random "User" folder via the Move Dialog in Properties to the networked pool. What does your set of instructions allow me to do now? I haven't setup anything on my end hence I cannot confirm what that does. Thanks again! Apologies for the double post. I'm connected to the forum via mobile device and I cannot find the edit button. When I say the files are moved to a recycle bin I mean on the machine doing the pool. Files shouldn't be copied to the local machines recycle bin when I delete from SMB. I doubt that can be interpreted from what I said but just want to make sure I mentioned this case. Its really just a case of When I delete from the pool, move it to a recycle-bin-like directory.

Hi folks, I'm in the process of setting up a DIY NAS. I plan to use SnapRAID. Due to the nature of the RAID, deletes that are left unsynced can be problematic. See http://wiki.flexraid.com/2011/10/18/understanding-the-limitations-of-snapshot-raid/ for more information. Originally I had the following idea: 1. Pool SnapRAID content drives together (excluding parity drive) 2. On delete, move to pools recycle bin 3. Weekly schedule, run a TRUE delete on the recycle bin of the pool 4. SnapRAID sync changes. This would give minimal time between being out of sync and being in sync. Someone once brought up my exact issue on your old discussion board. http://forum.covecube.com/discussion/1076/undelete-files-deleted-via-smb/p1 However, for "next time", a number of people have recommend running other Undelete utils that create their own "recycle bin" of sorts to help prevent this sort of issue. I am not clear on what that comment means with the issue. However i'm left with the following issues. 1. SnapRAID + DrivePool might mean deletes are immediate (rather than moved to a pooled recycle bin, moves do not compromise parity) 2. FlexRAID offers essentially what I'm trying to do with drive pool (a pooled drive)....however I lose features I want out of DrivePool (SSD Landing Drive, Folder Duplication). Hopefully some input from you guys could tell me if DrivePool offers this feature, or a potential alternative solution in mitigating the "delete problem" mentioned above. I will be accessing the drive via SMB. Greyhole (a linux "equivalent" of DrivePool does this by a "Trash" feature. Instead of permanent delete, it moves there. Then eventually you run a permanent delete command or delete it from the Trash folder). https://github.com/gboudreau/Greyhole/wiki/AboutTrash Additionally in linux, there's vfs_recycle which allows you to move instead of delete on a delete request. Unfortunately that doesn't exist in Windows Samba sharing. Thanks folks for your help! edit: One annoying but potential compromise is to create a "DELETE" folder on the pool. Whenever I want to delete files, move it to that folder instead. However that requires educating users accessing the share that when they want to delete something they need to move it to a special directory. But you can't disable DELETE in NTFS without disabling MOVE (Move is just a COPY+DELETE)...so it'd really be a case where I have to trust that my users will delete files in the "move" way