Shares Routinely inexplicably Empty

[ralfb]

I've got a nagging greyhole problem in so far as that entire shares and files disappear from the storage pool shares.

I find shares completely empty once in a while and the way I have recovered the share so far is to find what I need in ..files/driveX/gh/sharename/ .

I've recovered missing shares/files by copying the share from ..files/driveX/gh/sharename/ to the desktop and then back into /mnt/samba/sharename.

This is unacceptable.

The other issue is that even when the entire share does not disappears, I routinely loose excel files.

My colleague may be working on an excel file on the server and the next day either one of us wants to open the file, it's gone and I need to recover in from ..files/driveX/gh/sharename/excelfile

I think for now I'd like to not use greyhole and simply use the system drive(s) (RAID1) for the shares.

How can I accomplish this?

I believe there is more involved then simply removing a share from the pool in the Amahi dashboard share settings, right?

I am also open to other solutions.

Many thanks

Ralf

uname -r; rpm -q samba hda-greyhole

2.6.35.6-45.fc14.x86_64
samba-3.5.5-68.fc14.1.x86_64
hda-greyhole-0.9.2-1.x86_64

yum -y install fpaste; fpaste /etc/samba/smb.conf; fpaste /etc/greyhole.conf

http://fpaste.org/eiqL/
Uploading (1.6KiB)...
http://fpaste.org/ghC3/

mount; fdisk -l; df -h; greyhole --stats

http://fpaste.org/J2JU/

mysql -u root -phda -e "select * from disk_pool_partitions" hda_production

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' | xargs ls -la | fpaste

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
ls: cannot access .gvfs: Permission denied
Uploading (2.8KiB)...
http://fpaste.org/E1fp/


[root@pra user]# greyhole --view-queue

PHP Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Asia/Hong_Kong' for 'HKT/8.0/no DST' instead in /usr/bin/greyhole on line 32

Greyhole Work Queue Statistics
==============================

This table gives you the number of pending operations queued for the Greyhole daemon, per share.

Write Delete Rename
Alex 0 0 0
James 0 0 0
Kimberley 0 0 0
Linda 0 0 0
Music 0 0 0
PRA Accounts 0 0 0
PRA Admin 0 0 0
PRA Data 0 0 0
PRA eMail 0 0 0
PRA Marketing 0 0 0
PRA Photos 0 0 0
PRA Reference 0 0 0
PRA Subcontractors 0 0 0
Public 0 0 0
==================
Total 0 + 0 + 0 = 0

The following is the number of pending operations that the Greyhole daemon still needs to parse.
Until it does, the nature of those operations is unknown.
Spooled operations that have been parsed will be listed above and disappear from the count below.

Spooled 32

[sandstroem]

Hi,

It seems you have problem connecting to your mysql database.

Try excecute:

Code: Select all

mysql -u root -phda -e "select * from disk_pool_partitions" hda_production

Do you still receive access denied? Paste the output.

Also, try with the credentials that greyhole use:

Code: Select all

mysql -u greyhole -pgreyhole -e "select * from settings" greyhole

Successful or access denied?