Amahi Forums

Posted: **Sat May 28, 2011 5:34 am**

I installed the above package last night and it seems to be causing me problems. All my shares that use greyhole pooling are unavailable via samba - I can see the HDA, and I can see the list of shares, but if I then try to access the share itself, it says it is unavailable. Happens both from XP and OSX

This seems to only happen on shares that are pooled.

I've rebooted both the hda and the clients, and it doesn't fix the problem. I've reverted back to the original version for now and all is fine again.

When accessing the failed share directory listing, a number of these errors appeared from samba

[2011/05/28 00:14:52.824149, 0] smbd/vfs.c:167(vfs_init_custom)
error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
[2011/05/28 00:14:52.824327, 0] smbd/vfs.c:309(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for greyhole
[2011/05/28 00:14:52.824624, 0] smbd/service.c:846(make_connection_snum)
vfs_init failed for service Music
[2011/05/28 00:14:52.826566, 0] smbd/vfs.c:167(vfs_init_custom)
error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
[2011/05/28 00:14:52.826736, 0] smbd/vfs.c:309(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for greyhole
[2011/05/28 00:14:52.826810, 0] smbd/service.c:846(make_connection_snum)
vfs_init failed for service Music
[2011/05/28 00:14:52.851890, 0] smbd/vfs.c:167(vfs_init_custom)
error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
[2011/05/28 00:14:52.852067, 0] smbd/vfs.c:309(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for greyhole
[2011/05/28 00:14:52.852247, 0] smbd/service.c:846(make_connection_snum)
vfs_init failed for service Music
[2011/05/28 00:14:52.854631, 0] smbd/vfs.c:167(vfs_init_custom)
error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
[2011/05/28 00:14:52.854803, 0] smbd/vfs.c:309(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for greyhole
[2011/05/28 00:14:52.854997, 0] smbd/service.c:846(make_connection_snum)
vfs_init failed for service Music
[2011/05/28 00:14:52.886096, 0] smbd/vfs.c:167(vfs_init_custom)
error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
[2011/05/28 00:14:52.886277, 0] smbd/vfs.c:309(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for greyhole
[2011/05/28 00:14:52.886372, 0] smbd/service.c:846(make_connection_snum)
vfs_init failed for service Music
[2011/05/28 00:14:52.888142, 0] smbd/vfs.c:167(vfs_init_custom)
error probing vfs module 'greyhole': NT_STATUS_UNSUCCESSFUL
[2011/05/28 00:14:52.888315, 0] smbd/vfs.c:309(smbd_vfs_init)
smbd_vfs_init: vfs_init_custom failed for greyhole
[2011/05/28 00:14:52.888422, 0] smbd/service.c:846(make_connection_snum)
vfs_init failed for service Music

Running F14 and Amahi 6.1
samba-3.5.8-76.fc14.i686

Any suggestions (Apart from wait for the official release of greyhole)?

Posted: **Sat May 28, 2011 9:51 am**

I just tried this too. as I need some of the bug fixes in 0.9.6 and 0.9.7. Similar problem - Samba doesn't work at all.

Posted: **Sat May 28, 2011 10:02 am**

I'm speculating here but it might just be that the greyhole VFS modules are installed in the wrong location and with the wrong name for Samba on Amahi to find them. I would expect them to go in /usr/lib*/samba/vfs, but I think they are in /usr/lib*/greyhole. I tried copying them but that didn't work so there may be a naming issue too.

Posted: **Sat May 28, 2011 12:57 pm**

This does seem to be the case - there should be a grehole.so symlink in /usr/lib*/samba/vfs pointing to the greyhole VFS lib; this is missing.

I've hacked things together in my case by installing 0.9.6 then replacing /usr/bin/greyhole with the one from 0.9.7; so far this looks good.

Posted: **Sun May 29, 2011 4:05 am**

You have a missing a symlink.
Uninstalling and re-installing the RPM usually fixes this.
You can also create the symlink manually:

Code: Select all

LIBDIR=/usr/lib; if [ "`uname -i`" = "x86_64" ]; then LIBDIR=/usr/lib64;fi
if [ -f ${LIBDIR}/samba/vfs/greyhole.so ]; then rm ${LIBDIR}/samba/vfs/greyhole.so; fi
SMB_VERSION="`smbd --version | awk '{print $2}' | awk -F'-' '{print $1}' | awk -F'.' '{print $1,$2}'`"
if [ "$SMB_VERSION" = "3 5" ]; then ln -s ${LIBDIR}/greyhole/greyhole-samba35.so ${LIBDIR}/samba/vfs/greyhole.so; else ln -s ${LIBDIR}/greyhole/greyhole-samba.so ${LIBDIR}/samba/vfs/greyhole.so; fi

Then verify that the symlinks are there: ls -l /usr/lib*/samba/vfs/greyhole.so

Posted: **Mon May 30, 2011 3:20 am**

Hi, I have the same issue since upgrading to latest greyhole some days ago.

(http://forums.amahi.org/viewtopic.php?f=39&t=2993)

I'd like to try un-installing and installing again.

May I have the commands to accomplish this pleases?

Is this the preferred remedy?

Or should I use the command above for a manual rebuild?

Mind you greyhole is still busy renaming 1000's of files after I've moved them down one directory as per this thread: (http://forums.amahi.org/viewtopic.php?f=39&t=2993)

Posted: **Mon May 30, 2011 5:08 am**

You can try re-installing the RPM (you can't uninstall and then install it; that would uninstall hda-platform!) using the same command you tried to update; just add a --force parameter in there:

Code: Select all

rpm -Uvh --force http://...

If that doesn't fix the symlink (check with ls command I gave above), then you can try running the other commands I mentioned; those are the commands that should be executed when the RPM installs, but somehow are not (or partially, or something).

Posted: **Mon May 30, 2011 7:03 am**

Thanks, below is copied from terminal.

Code: Select all

 
[root@padme ]# rpm -Uvh --force http://www.greyhole.net/releases/hda-greyhole-0.9.7-1.`uname -i`.rpm
Retrieving http://www.greyhole.net/releases/hda-greyhole-0.9.7-1.x86_64.rpm
Preparing...                ########################################### [100%]
   1:hda-greyhole           ########################################### [100%]
[root@padme abc]# ls -l /usr/lib*/samba/vfs/greyhole.so
lrwxrwxrwx 1 root root 39 May 30 21:51 /usr/lib64/samba/vfs/greyhole.so -> /usr/lib64/greyhole/greyhole-samba35.so
[root@padme ]#

Is this correct?

Nothing beyond /mnt/samba/sharename

How much time should this take?

I don't know what to expect so can not judge.

Many thanks in advance

Posted: **Mon May 30, 2011 7:13 am**

This is correct. The issue was that there was no symlink, and now there is one.
Try connecting to your shares now, it should work fine.

If you have issues with mount_shares_locally, please open a new thread, so you don't hijack this thread that is about the missing symlink.
(Or just restart the service, to have the shares re-mounted locally.)

Posted: **Sun Jan 01, 2012 8:17 am**

hi,

this method of fixing missing symlnks no longer works.

For one the hda-greyhole archive seems no longer available.

the wiki update instructions also seem out of date?

How may I fix the symlinks and update greyhole?

Amahi Forums

Problem with 0.9.7 hda-greyhole

Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole

Re: Problem with 0.9.7 hda-greyhole