Cannot access share when set to be in the storage pool

[VirtualMe]

I am using Fedora 14 as Fedora 12 does not support my server's integrated graphics on the Core i3.

I've been Googling about Samba, but haven't found a solution yet. What does Greyhole do when instructed to add a share to the storage pool?

I installed Fedora, installed Amahi, and did all the system updates. I can access the shares that Amahi creates by default just fine. However, when I tell a share, say Music, to be part of the storage pool, I can no longer access it from my Windows 7 machine. Windows just says it is not accessible and I might not have permission. I can access all of the other shares just fine and when I tell Music to not be part of the storage pool, I can access it once again.

1. uname -r; rpm -q samba hda-greyhole

Code: Select all

2.6.35.6-48.fc14.x86_64 samba-3.5.6-70.fc14.x86_64 hda-greyhole-0.7.5-1.x86_64

2. fpaste /etc/samba/smb.conf; fpaste /etc/greyhole.conf

Code: Select all

http://fpaste.org/nk16/ http://fpaste.org/iWma/

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

Code: Select all

/dev/mapper/vg_server-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/mapper/vg_server-lv_home on /home type ext4 (rw) /dev/sdb1 on /var/hda/files/drives/sdb1 type ext4 (rw) /dev/sdc1 on /var/hda/files/drives/sdc1 type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) gvfs-fuse-daemon on /home/virtualme/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=virtualme) Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_server-lv_root 50G 3.6G 44G 8% / tmpfs 907M 188K 906M 1% /dev/shm /dev/sda1 485M 48M 412M 11% /boot /dev/mapper/vg_server-lv_home 241G 2.7G 226G 2% /home /dev/sdb1 917G 200M 871G 1% /var/hda/files/drives/sdb1 /dev/sdc1 917G 200M 871G 1% /var/hda/files/drives/sdc1 Greyhole Statistics =================== Storage Pool Total - Used = Free + Attic = Possible /var/hda/files/drives/sdc1/gh: 917G - 0G = 870G + 0G = 870G /var/hda/files/drives/sdb1/gh: 917G - 0G = 870G + 0G = 870G

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

Code: Select all

+----+----------------------------+--------------+---------------------+---------------------+ | id | path | minimum_free | created_at | updated_at | +----+----------------------------+--------------+---------------------+---------------------+ | 3 | /var/hda/files/drives/sdc1 | 10 | 2010-12-06 05:19:48 | 2010-12-06 05:19:48 | | 4 | /var/hda/files/drives/sdb1 | 10 | 2010-12-06 05:19:49 | 2010-12-06 05:19:49 | +----+----------------------------+--------------+---------------------+---------------------+

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

Code: Select all

http://fpaste.org/Xxfg/

6. greyhole --view-queue

Code: Select all

Greyhole Work Queue Statistics ============================== This table gives you the number of pending operations queued for the Greyhole daemon, per share. Write Delete Rename Music 0 0 0 ===== Total 0 + 0 + 0 = 0

[gboudreau]

Your problem is that the Greyhole package for Amahi isn't compatible with Fedora 14. More precisely, it's not compatible with Samba 3.5.x that F14 uses.

Here's how you can fix, and even help other F14 users too.
You'll need to compile yourself the greyhole module that is used by Samba (greyhole.so).

To do so (as root):

Code: Select all

yum -y install make mysql-server php php-mysql php-mbstring samba samba-common patch gcc rsyslog yum-utils php-pear rsync cd yumdownloader --source samba rpm -ivh samba-3.*.fc*.src.rpm cd rpmbuild/SOURCES tar zxf samba-3.*.tar.gz cd samba-3.*/source3/ curl -o modules/vfs_greyhole.c http://greyhole.googlecode.com/svn/trunk/samba-module/vfs_greyhole-samba-3.5.c ./configure curl -o Makefile-samba-3.5.patch http://greyhole.googlecode.com/svn/trunk/samba-module/Makefile-samba-3.5.patch patch -p1 < Makefile-samba-3.5.patch make cp bin/greyhole.so /usr/lib64/samba/vfs/greyhole.so service smb restart

That should fix your problem.
If it does, please send me the greyhole.so file so that I can include it in future Greyhole packages:
Just email me that file: /usr/lib64/samba/vfs/greyhole.so
Send it to: support@greyhole.net
Thanks.

[VirtualMe]

That seems to have fixed the problem.

Email sent with the greyhole.so file. Thanks!

[nephster]

I have studiously followed the above but not getting any joy as soon as shares are removed from the pool they become accessible.

1/

Code: Select all

2.6.35.9-64.fc14.x86_64 samba-3.5.6-71.fc14.x86_64 hda-greyhole-0.7.6-1.x86_64

2/
http://fpaste.org/CpOR/
http://fpaste.org/aw5M/

3/

Code: Select all

/dev/mapper/vg_athlon3700-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/mapper/vg_athlon3700-lv_home on /home type ext4 (rw) /dev/sdc1 on /var/hda/files/drives/drive6 type ext4 (rw) /dev/sdb1 on /var/hda/files/drives/drive9 type ext4 (rw) /dev/sdd1 on /var/hda/files/drives/drive10 type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) gvfs-fuse-daemon on /home/nephster/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=nephster) Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000eed2e Device Boot Start End Blocks Id System /dev/sda1 * 2048 1026047 512000 83 Linux /dev/sda2 1026048 3907028991 1953001472 8e Linux LVM Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00016497 Device Boot Start End Blocks Id System /dev/sdc1 2048 3907028991 1953513472 83 Linux Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0004ab56 Device Boot Start End Blocks Id System /dev/sdb1 2048 3907028991 1953513472 83 Linux Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00082abe Device Boot Start End Blocks Id System /dev/sdd1 2048 3907028991 1953513472 83 Linux Disk /dev/dm-0: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 4227 MB, 4227858432 bytes 255 heads, 63 sectors/track, 514 cylinders, total 8257536 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 1941.9 GB, 1941929197568 bytes 255 heads, 63 sectors/track, 236092 cylinders, total 3792830464 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_athlon3700-lv_root 50G 4.2G 43G 9% / tmpfs 1005M 124K 1005M 1% /dev/shm /dev/sda1 485M 30M 430M 7% /boot /dev/mapper/vg_athlon3700-lv_home 1.8T 3.6G 1.7T 1% /home /dev/sdc1 1.8T 196M 1.7T 1% /var/hda/files/drives/drive6 /dev/sdb1 1.8T 196M 1.7T 1% /var/hda/files/drives/drive9 /dev/sdd1 1.8T 196M 1.7T 1% /var/hda/files/drives/drive10 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 'UTC' for 'GMT/0.0/no DST' instead in /usr/bin/greyhole on line 39 Greyhole Statistics =================== Storage Pool Total - Used = Free + Attic = Possible /home/gh: awk: (FILENAME=- FNR=2) fatal: attempt to access field -3 0G - 0G = 1686G + 0G = 1686G /var/hda/files/drives/drive6/gh: 1834G - 0G = 1740G + 0G = 1740G /var/hda/files/drives/drive9/gh: 1834G - 0G = 1740G + 0G = 1740G /var/hda/files/drives/drive10/gh: 1834G - 0G = 1740G + 0G = 1740G

4/

Code: Select all

+----+-------------------------------+--------------+---------------------+---------------------+ | id | path | minimum_free | created_at | updated_at | +----+-------------------------------+--------------+---------------------+---------------------+ | 1 | /home | 10 | 2010-12-22 21:13:05 | 2010-12-22 21:13:05 | | 2 | /var/hda/files/drives/drive6 | 10 | 2010-12-22 21:13:07 | 2010-12-22 21:13:07 | | 3 | /var/hda/files/drives/drive9 | 10 | 2010-12-22 21:13:09 | 2010-12-22 21:13:09 | | 4 | /var/hda/files/drives/drive10 | 10 | 2010-12-22 21:13:11 | 2010-12-22 21:13:11 | +----+-------------------------------+--------------+---------------------+---------------------+

5/
http://fpaste.org/bGRp/

6/

Code: Select all

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 'UTC' for 'GMT/0.0/no DST' instead in /usr/bin/greyhole on line 39 Greyhole Work Queue Statistics ============================== This table gives you the number of pending operations queued for the Greyhole daemon, per share. Write Delete Rename Comedy 0 0 0 Music 0 0 0 Music Videos 0 0 0 ============ Total 0 + 0 + 0 = 0

[gboudreau]

The Samba VFS module that comes with hda-greyhole 0.7+ should be compatible with Samba 3.5, and F14).
So the above procedure to re-compile the VFS module manually shouldn't be required anymore.

Check your /var/log/samba/*.log log files for errors.
In particular, look for new lines in those files when you restart the Samba server (though the Dashboard, or from the command line).

*edit: There was an issue with all RPMs created before 0.8.3-2 that prevented them to work correctly on Fedora 14.
See my post below about 0.8.3-2 and +.

[nephster]

Hmmm - this seems to be the crux of the problem:

"The module was compiled against SMB_VFS_INTERFACE_VERSION 25,
current SMB_VFS_INTERFACE_VERSION is 27.
Please recompile against the current Samba Version!"

As a poor confused Windows user, what do I need to do? Have four lovely new 2TB discs that are waiting to be filled

[gboudreau]

Use Fedora 12, not 14.
Amahi on F14 is still in alpha, and not ready for anyone but developers.

[gboudreau]

All version of Greyhole >= 0.8.3-2 should work on Fedora 14.

You can test that version by following those instructions.