Thorsten Pferdekämper wrote:
> Hi folks,
> 
> In my setup, two freevo boxes are connected via smb shares. This works very 
> well as long as both boxes are up and running, but problems occur when the 
> server is switched off.
> 
> Here are the details:
> 
> I have two freevo boxes. One of them (called "hera") is mainly dedicated to 
> recording, the other one ("freevobox2") is dedicated to watching recorded 
> shows, looking at pictures etc. 
> "hera" shares its directories using samba. Here is a part of 
> my /etc/samba/smb.conf:
> 
> [Recorded]
>   comment = Recorded Shows
>   writeable = no
>   locking = no
>   path = /mm/Recorded
>   public = yes
> 
> [Pictures]
>   comment = Pictures
>   writeable = no
>   locking = no
>   path = /mm/Pictures
>   public = yes
> 
> ...and so on for Videos, Music etc.
> 
> "freevobox2" automatically mounts these directories using autofs. The mount 
> point is something like /mnt/smb. This e.g. results in the recorded shows 
> being found in /mnt/smb/hera/Recorded. 
> The VIDEO_ITEMS in my local_conf.py look like that:
> 
> VIDEO_ITEMS = [ ('Frisch aufgenommen', '/mm/Recorded'),
>                 ('Noch nicht gesehen', '/mm/Videos/Noch nicht gesehen'),
>                 ('Videos', '/mm/Videos'),
>                 ('USB', '/var/run/usbmount')] 
> 
> /mm/Recorded is just a link to /mnt/smb/hera/Recorded
> /mm/Videos contains a link to /mnt/smb/hera/Videos
> 
> As I have said, everything works good as long as hera is running. If it is 
> not, everything is quite slow, even if I only move around on the initial 
> freevo screen. (It would be ok if it would be slow when I try to click on one 
> of the dead links...)
> Things are becoming worse when hera was running and I switch it off. In this 
> case, the shared directories are not unmounted (even after the timeout 
> specified in /etc/auto.master). This causes navigation on freevobox2 becoming 
> even slower up to a point where needed to reboot the system.
> (Or using the force option of umount.cifs to get rid of the dead stuff. 
> However, usually freevobox2 is only operated using an IR...)
> 
> I thought that all this could be easily solved by some more sophisticated 
> setup of autofs (etc.), but it seems that there is really a problem of 
> umounting smb/cifs file systems when the server is not up any more. 
> 
> Maybe there is someone out there who solved this problem... 

I suspect that this is related to how autofs works with samba shares.
You could try using mount instead of autofs, then when the shares are
not available at boot then they are not mounted.

You could also try using nfs instead of samba, it makes more sense for
unix mounts.

Duncan


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to