Amahi Forums

Hi,

Boy do I love Greyhole! So far I've been managing my Greyhole storage by using "Stickies". This way I could (kind-of) create a dummy RAID1-type setup - ie I wanted each Share to have it's own pair of disks. I therefore setup my greyhole.yml as follows:

- - Music/
- - Pictures/
- - Family_Video/
- - RecordedTV/
- - Backups/
- - /var/hda/files/drives/drive1/gh
- /var/hda/files/drives/drive2/gh
- - TV_Series/
- - /var/hda/files/drives/drive9/gh
- /var/hda/files/drives/drive10/gh
- - Films_Recorded/
- - /var/hda/files/drives/drive7/gh
- /var/hda/files/drives/drive8/gh
- - Motorsport/
- - /var/hda/files/drives/drive11/gh
- /var/hda/files/drives/drive12/gh
- - Other_TV/
- - /var/hda/files/drives/drive5/gh
- /var/hda/files/drives/drive6/gh
- - Sport/
- - /var/hda/files/drives/drive3/gh
- /var/hda/files/drives/drive4/gh

However, I've noticed that Greyhole isn't strictly adhering to these suggested stickies (I've also spotted this by looking at "tail" of greyhole's log as it's doing the copying, and noticed that the sticky list doesn't always match what I'm expecting). The result is that quite a few files now are on the "wrong" drives (compared to where I actually wanted them to go!).

My question is 2-fold:
1) Is there any error in the YML config I've set up above that's causing this problem?
2) Could this be an old known bug whereby Greyhole uses partial matching of a string for share names (eg "Motorsport" and "sport" would in the past have caused a clash), or:
a) Has that bug been fixed
b) That bug doesn't affect this issue?

I have an issue with sticky_files that looks like it might be the same as yours:

Fedora 16
Kernel; 3.2.5-3
Samba 3.6.3-78
greyhole 0.9.20-1

I have set a share as sticky in greyhole.conf:

sticky_files = My_Share/

I have not specified 'stick_into' as I don't mind. This share has num_copies = 2. The share contains a nested hierachy of folders and files.

I have three drives: Pool1, Pool2, Pool3 - gh folders in each are set as part of the pool in greyhole.conf and the LZ for My_Share is in Pool1.

After greyhole --fsck If I look in the gh folder in each of these drives I see files from My_Share in all 3 of them. It isn't a complete copy of My_Share in any of the gh.

With the above settings I would expect to see a complete version of My_Share in 2 of the gh folders of my storage drives. Is this correct?

Any idea why this is not happening?