Author |
Message |
goaliemanpat
|
Posted: Sat Sep 15, 2007 6:54 pm |
|
Joined: Tue Jan 23, 2007 12:19 pm
Posts: 40
Location:
Swartz Creek, MI
|
I have a 300 gig hard drive that is mounted to /myth/video to hold my dvd collections. Everything is seen fine and the movies are seen when playing on the backend yet I cannot get the separate frontend to see the movie files. I followed the KMwiki guide and made a directory that was mounted to the backends /myth/ folder. When I browse through the folder the video directory is seen as if the separate hard drive wasn't there. Do I need to do something extra to get the NFS to see the hard drive mounted there?
|
|
Top |
|
 |
tjc
|
Posted: Sat Sep 15, 2007 7:06 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
You need another mount for the other file system. Make sure /myth/video is in your /etc/exports and then add another NFS mount like the one for /myth in the /etc/fstab file on the FE box.
|
|
Top |
|
 |
goaliemanpat
|
Posted: Mon Sep 17, 2007 8:37 am |
|
Joined: Tue Jan 23, 2007 12:19 pm
Posts: 40
Location:
Swartz Creek, MI
|
Ok. Thanks for the info tjc. Just to make sure I just have to edit these two files:
On the backend /etc/exports file there is a couple commented out things and then
Code: /myth *(rw) so I just add Code: /myth/video *(rw) and on the frontend /etc/fstab file i add Code: /dev/hdb1 /myth/video ext3 defaults,auto 0 2
I have to reboot both machines dont I?
Last edited by goaliemanpat on Mon Sep 17, 2007 12:25 pm, edited 1 time in total.
|
|
Top |
|
 |
kmkittre
|
Posted: Mon Sep 17, 2007 12:01 pm |
|
Joined: Tue Jul 12, 2005 8:01 am
Posts: 670
Location:
Salem, MA
|
You don't have to reboot, you just have to restart the nfs services on the backend after you manually mount:
Code: mount /dev/hdb1 /myth/video /etc/init.d/nfs-common restart /etc/init.d/nfs-kernel-server restart Let us know if this works. I remember trying to do exactly what you are doing and having trouble. This is how I ended up setting it up: backend: Code: mount /dev/hdb1 /video cd /myth ln -s /video video frontend: Code: mount <backendipaddress>:/myth /myth mount <backendipaddress>:/video /video
_________________ LinHES 8.3, 1 BE, 3 FE
|
|
Top |
|
 |
Kirk
|
Posted: Mon Sep 17, 2007 8:02 pm |
|
Joined: Mon Mar 13, 2006 2:28 am
Posts: 143
Location:
Brisbane, Australia
|
goaliemanpat wrote: and on the frontend /etc/fstab file i add Code: /dev/hdb1 /myth/video ext3 defaults,auto 0 2 No, that's like mounting a normal hard drive, you're trying to mount a share which is slightly different syntax. Instead of "partition mount-point", it's "server-share mount-point" Code: 192.168.0.1:/myth/video /myth/video nfs defaults,auto,noatime 0 0
|
|
Top |
|
 |
goaliemanpat
|
Posted: Tue Sep 18, 2007 7:33 am |
|
Joined: Tue Jan 23, 2007 12:19 pm
Posts: 40
Location:
Swartz Creek, MI
|
Thanks for your help guys. I took all your suggestions and got it working. KM community FTW lol
|
|
Top |
|
 |
goaliemanpat
|
Posted: Mon Sep 24, 2007 8:55 am |
|
Joined: Tue Jan 23, 2007 12:19 pm
Posts: 40
Location:
Swartz Creek, MI
|
Ok Ive found a new issue. Everything works fine until I have to reboot the frontend. Then I lose the mounts. Here is the contents of my /etc/fstab file on the frontend:
Code: #/etc/fstab: filesystem table. # #filesystem mountpoint type options dump pass /dev/hda1 / ext3 defaults,errors=remount-ro 0 1 #/dev/hda3 /myth ext3 defaults,auto 0 2 192.168.12.191:/myth /myth ext3 rw,auto,user,exec 0 0 192.168.12.191:/myth/video /mnt/video ext3 rw,auto,user,exec 0 0
There is also more below but it looks to just be floppy, cdrom, sb etc.
I can go into the command line and mount them no problems but did I type somethin incorrectly in the fstab so they are not mounted on boot?
|
|
Top |
|
 |
kmkittre
|
Posted: Mon Sep 24, 2007 9:27 am |
|
Joined: Tue Jul 12, 2005 8:01 am
Posts: 670
Location:
Salem, MA
|
Code: 192.168.12.191:/myth /myth ext3 rw,auto,user,exec 0 0 192.168.12.191:/myth/video /mnt/video ext3 rw,auto,user,exec 0 0 Should be: Code: 192.168.12.191:/myth /myth nfs defaults,auto,noatime 0 0 192.168.12.191:/myth/video /mnt/video nfs defaults,auto,noatime 0 0
Also, make sure that your backend has a static IP, not DHCP...
_________________ LinHES 8.3, 1 BE, 3 FE
|
|
Top |
|
 |
jmckeown2
|
Posted: Mon Sep 24, 2007 4:39 pm |
|
Joined: Sat Sep 02, 2006 9:17 am
Posts: 359
|
kmkittre wrote: Also, make sure that your backend has a static IP, not DHCP...
Technically DHCP shouldn't be a problem iff you configure the DHCP server to always give the same IP address to your mythbox. This is a pretty standard feature on home routers.
|
|
Top |
|
 |
tjc
|
Posted: Mon Sep 24, 2007 5:57 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Actually...
kmkittre wrote: Should be: Code: 192.168.12.191:/myth /myth nfs defaults,auto,noatime 0 0 192.168.12.191:/myth/video /mnt/video nfs defaults,auto,noatime 0 0 Actually... I think that should be: Code: 192.168.12.191:/myth /myth nfs defaults,auto,noatime 0 0 192.168.12.191:/myth/video /myth/video nfs defaults,auto,noatime 0 0
|
|
Top |
|
 |
kmkittre
|
Posted: Mon Sep 24, 2007 10:13 pm |
|
Joined: Tue Jul 12, 2005 8:01 am
Posts: 670
Location:
Salem, MA
|
Appreciate the suggestion, tjc, but that doesn't work for me
I'm sure it's just my naiveté, but if I try it this way it doesn't work. I have a similar setup. I purchased a 500GB sata and I didn't want to roll it up into my LVM, so I decided to just put my videos on it. I had to mount the drive outside of the /myth partition and create a symbolic link to it. If I tried to mount the drive inside the /myth partition I could access it on the backend but not on a separate frontend.
Again, maybe it can be done, but I couldn't figure it out...
_________________ LinHES 8.3, 1 BE, 3 FE
|
|
Top |
|
 |
goaliemanpat
|
Posted: Tue Sep 25, 2007 6:57 am |
|
Joined: Tue Jan 23, 2007 12:19 pm
Posts: 40
Location:
Swartz Creek, MI
|
Thanks TJC. Worked like a charm. Just noticed Kirk pretty much said the same thing a couple posts ago but in my mind its just going "well its an ext3 formatted drive so I must have to put ext3 in there " hehe
KM do you have NFS working on the backend?
|
|
Top |
|
 |
tjc
|
Posted: Tue Sep 25, 2007 6:17 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
kmkittre wrote: Appreciate the suggestion, tjc, but that doesn't work for me 
I think you missed a step somewhere then. One the BE box where the drive lives you mount it like this in /etc/fstab:
Code: /dev/hda3 /myth ext3 defaults,auto 0 2 /dev/hdb1 /myth/video ext3 defaults,auto 0 2
In your /etc/exports on the BE box you export both directories: Code: /myth 192.168.1.0/255.255.255.0(rw,subtree_check) /myth/video 192.168.1.0/255.255.255.0(rw,subtree_check)
On the remote machine you then can use something like this in your /etc/fstab there: Code: 192.168.12.191:/myth /myth nfs defaults,auto,noatime 0 0 192.168.12.191:/myth/video /myth/video nfs defaults,auto,noatime 0 0
The nohide and crossmnt options for exports also do similar things with only one export and remote mount but can have some odd issues.
Reading man exports and man nfs is highly recommended. I did my first NFS setup something like 18 years ago and still check the associated man pages whenever I'm messing with this stuff.
|
|
Top |
|
 |
kmkittre
|
Posted: Tue Sep 25, 2007 7:09 pm |
|
Joined: Tue Jul 12, 2005 8:01 am
Posts: 670
Location:
Salem, MA
|
So the "subtree_check" is what I was missing. Like I said, you could probably do it, I just didn't know how
Thanks for the tip. I'll probably leave my system as-is for now as it is working, but I'll probably change this in the next upgrade.
_________________ LinHES 8.3, 1 BE, 3 FE
|
|
Top |
|
 |
jmckeown2
|
Posted: Wed Sep 26, 2007 2:47 am |
|
Joined: Sat Sep 02, 2006 9:17 am
Posts: 359
|
tjc wrote: In your /etc/exports on the BE box you export both directories: Code: /myth 192.168.1.0/255.255.255.0(rw,subtree_check) /myth/video 192.168.1.0/255.255.255.0(rw,subtree_check)
...I did my first NFS setup something like 18 years ago...
tjc,
I'm curious, in my reading of the exports manpage, it seemed no_subtree_check was more appropriate, but I find the manpage a bit vague. It says no_subtree_check "has mild security security implications, but can improve reliability in some circumstances" but it doesn't say what implications, or what circumstances improve reliability. Anyway it seems to imply that if you are exporting the entire filesystem then subtree checks are not needed, it then seems to contradict saying in examples that /homes should have checks disabled and /usr and /var should be enabled indicitating that the frequency of file renames is the deciding factor.
Anyway, and I apologize if I'm pulling this off topic, but what does subtree checking mean to you?
|
|
Top |
|
 |