Struggling to get greyhole working

[uwmad]

Hi all,

I'm a bit of a newb to this so I hope you'll be patient with me. I installed Amahi a few weeks ago and thought I set up greyhole correctly but the files never get moved out of the landing zone. I have read through pages of posts over the last few weeks but I can't find a solution. I'm guessing it's something obvious I have over looked but I'm struggling.

One odd error message, when I use the fsck command I get:
fsck from util-linux 2.23.2
e2fsck 1.42.7 (21-Jan-2013)
/dev/sda3 is mounted.
e2fsck: Cannot continue, aborting.

smb.conf: http://paste.fedoraproject.org/81377/36168601
greyhole.conf: http://paste.fedoraproject.org/81378/36169931

Appreciate the help.

[bigfoot65]

It appears you did not follow the wiki guidance correctly. You have to add your drives and number of copies per share in the greyhole.conf file.
https://wiki.amahi.org/index.php/Amahi_ ... hole_Setup

[uwmad]

apologies for being daft but haven't I done that? Do I need to include the main hard drive in the conf file? What would be the conf line for that drive, since the mount point seems to be / ?

thanks

[bigfoot65]

The only drive you can add to Greyhole is sdb1. The wiki shows how to do that as you probably noticed. You have not added anything based on the file you attached. You have not added your shares with number of copies either.

EDIT:
I obviously cannot read as I overlooked your drive and share additions. They appear to be correct. Please check the /var/log/greyhole.log file for errors.

Did you issue the command as root user?

Code: Select all

greyhole -f

[bigfoot65]

One other thought is maybe the drive and shares lines need to be farther down in the greyhole.conf file where the examples are located. I would hope that it doesn't matter, but could be a factor if things are still not working.

Also forgot to ask if you restarted Greyhole after adding the lines. If you followed the wiki guidance, then you did.

[uwmad]

thank for your help.

The only thing in the log that looks suspect is:

Feb 28 20:40:39 2 fsck: Found a share (Pictures), with path /var/hda/files/pictures, which is INSIDE a storage poo$
For your shares to use your storage pool, you just need them to have 'vfs objects = greyhole' in their (smb.conf) $

[bigfoot65]

It looks as if it is there in your smb.conf file. Did you try restarting Greyhole, then look at the log file? It should show some start up messages.

Also ensure all the files in your shares are owned by your 1st admin user:users as well. I cannot say I have seen this error before. Greyhole usually gives pretty good messages in the log file.

I presume you added those options via the dashboard and not directly to the smb.conf file, correct? Might consider restarting samba too or even reboot the server to see if that fixes it.

[uwmad]

Yes, added them via the dashboard rather than directly in the smb.conf

I restarted my server. Everything looks ok to me:

eb 28 21:46:41 7 sleep: Nothing to do... Sleeping.
Feb 28 21:46:51 7 sleep: Nothing to do... Sleeping.
Feb 28 21:45:16 6 daemon: Greyhole (version 0.9.35) daemon started.
Feb 28 21:45:16 6 daemon: Optimizing MySQL tables...
Feb 28 21:45:16 7 read_smb_spool: Processing Samba spool...
Feb 28 21:45:16 7 simplify_tasks: Simplifying pending tasks.
Feb 28 21:45:16 7 sleep: Nothing to do... Sleeping.
Feb 28 21:45:26 7 sleep: Nothing to do... Sleeping.

Not sure what you mean by ownership of the files but all of he files I've put on the server were created on my pc.

again, want to say i appreciate you helping me out.

[bigfoot65]

Yes that start up message looks normal. Change you shares copies number in greyhole.conf from 1 to max. Then as root user do greyhole - f and check log.

Glad to help. Hopefully it will work correctly now.

[ Post made via Android ]

[uwmad]

I think we are making progress. I changed the share copies to 999 and ran greyhole -f . The log reported the following;


Feb 28 22:04:50 7 sleep: Nothing to do... Sleeping.
Feb 28 22:04:59 2 fsck: Found a storage pool drive (/var/hda/files/drives/drive1/gh), which is INSIDE a share landing zone (/var/hda/files/d$
For your shares to use your storage pool, you just need them to have 'vfs objects = greyhole' in their (smb.conf) config; their location on $
Feb 28 22:05:00 7 sleep: Nothing to do... Sleeping.
Feb 28 22:05:10 7 sleep: Nothing to do... Sleeping.