[SOLVED] Fatal Error: Failed to mount NFS Volume

[ch3i]

@Quazz said:

@arnaudrigole That and also because Windows doesn’t support NFS by default.

Windows support NFS… look at Server 2008/2012 (2008 > NFS V3 et 2012 > NFS V4.1)

[Quazz]

@ch3i Server yes, clients not.

[arnaudrigole]

I’ve another problem…
haven’t the time yet to mount my NFS storage so i keep using /images default directory of FOG; but when i try to download an image on a computer it said …

**FATAL ERROR: Failed to mount NFS volume
*if you believe the filesystem is mounted, make sure you have a file called .mntcheck in the directory you are mouting on the server.
**

i don’t see any “.mntcheck” file in /images and /images/dev…
So i created it with “touch /images/.mntcheck” and “touch /images/dev/.mntcheck” but it still dont work…
Can’t deploy anything now …

[Tom Elliott]

@arnaudrigole Did you edit the /etc/exports so it’s looking at the proper directory? If the CIFS share is still mounted on the server at /srv/cifs/SRVADM/images and your Exports file is still looking at /images and /images doesn’t exist on the FOG Server, it would still have a problem.

If /srv/cifs/SRVADM/images is mounted to the folder /images AND, before the share is mounted, and you create the /images/.mntcheck /images/dev/.mntcheck files, then mount the samba over the TOP of the folder, the mounted folder needs these files so you’d have to run the same touch commands to ensure those files are present on the share as well.

I think there’s almost too much going on to properly assist.

What is going on? Are you still mounting the /srv/cifs/SRVADM/images folder?

What’s in your /etc/exports file?

What version are you running?

Where are you defining the mount?

I could also be chasing a rabbit down a hole as I’m still not sure you can NFS Export a CIFS Share either.

If you’re that worried about security, why are you using a common system that OTHER users are accessing and writing data to as your mount point for where FOG stores its images?

[arnaudrigole]

@Tom-Elliott
Thanks for your reply, mine are in your message below:

Did you edit the /etc/exports so it’s looking at the proper directory? If the CIFS share is still mounted on the server at /srv/cifs/SRVADM/images and your Exports file is still looking at /images and /images doesn’t exist on the FOG Server, it would still have a problem. > As you said before, i re-edited it so its look like default now /images and /images/dev

If /srv/cifs/SRVADM/images is mounted to the folder /images AND, before the share is mounted, and you create the /images/.mntcheck /images/dev/.mntcheck files, then mount the samba over the TOP of the folder, the mounted folder needs these files so you’d have to run the same touch commands to ensure those files are present on the share as well. > I’m afraid but i think i don’t understand… After i re-modified the /etc/exports file , i did touch commands on /images and /images/dev. I did not succeed the externalization of image storage, so i just want to go back on default configuration

I think there’s almost too much going on to properly assist. > Yes

What is going on? Are you still mounting the /srv/cifs/SRVADM/images folder? > it appears to be hard for me, i’m actually blocked by NFS and access rights… but i’ll continue to work on it but not now (FOG is currently used for production in my company)

What’s in your /etc/exports file? >** /images (ro,sync,no…default string)
/images/dev (rw,sync, … default string too)

What version are you running? > Fog 1.2.0

Where are you defining the mount? > When i did my tests for storage externalization, i wanna mount //SRVADM/FOG/Images (Windows 2008R2) on /srv/cifs/SRVADM/Images (Fog Server)

I could also be chasing a rabbit down a hole as I’m still not sure you can NFS Export a CIFS Share either. > i think i don’t understand … but i recreated a shared directory by NFS services on my Win 2008R2, and when i try to mount it as : “mount -t nfs //SRVADM:FOG/Images /srv/cifs/SRVADM/images it return me :” mount.nfs : Failed to resolve server //SRVADM: name or service not known" , tried with IP -> same.

If you’re that worried about security, why are you using a common system that OTHER users are accessing and writing data to as your mount point for where FOG stores its images? -> SRVADM is a server dedicated to IT service, we have no common data on it, but i told this only for crypto virus who infect “Everybody” shared directories

Have a good sunny day

[Quazz]

@arnaudrigole " i think i don’t understand … but i recreated a shared directory by NFS services on my Win 2008R2, and when i try to mount it as : “mount -t nfs //SRVADM:FOG/Images /srv/cifs/SRVADM/images it return me :” mount.nfs : Failed to resolve server //SRVADM: name or service not known" , tried with IP -> same."

Your syntax is incorrect, it should be something like mount -t nfs SRVADM(or ip):/FOG/Images destinationpathhere (eg mount/images after doing mkdir mount/images)

// is only used for SAMBA/CIFS paths and won’t work for other methods of connecting.

Also, as a note, NFS needs full path to the destination when you try to mount it, not just to the shared folder. Not sure if that’s the case on your end!

[Tom Elliott]

@Quazz I’m only aware of CIFS using \\ not // as the leader.

[Quazz]

@Tom-Elliott Right you are.

[george1421]

@Quazz said:

// is only used for SAMBA/CIFS paths and won’t work for other methods of connecting.

I agree, we are dealing with a unix system not windows. NFS requires unix style syntax for drive mapping required here.

[arnaudrigole]

@Quazz
Ok so, the mount cmd i type is exactly this : mount -t nfs 10.1.11.64:/FOG/Images /srv/nfs/SRVADM/Images
“FOG” directory is the one shared by NFS on the server, give full rw rights for “anybody” -> nothing returned by the cmd, seems to be OK, but when i type : cd /srv/nfs/SRVADM/images -> input/output error

i did apt-get install nfs-common too

i’m sorry but it look so complicated to mount any Windows shared directory on a linux VM…

[Quazz]

@arnaudrigole Is the FOG directory located at the root of that server? Because you need the full path!

[arnaudrigole]

@Quazz
FOG directory is located physically on E:\informatique\Service_info\FOG\Images but the NFS share is setup on FOG so nfs assistant told me the way is : \SRVADM\FOG , so i have to set:
mount -t nfs 10.1.11.64:/E:/informatique/Service_info/FOG/Images ??
thank you

[Quazz]

@arnaudrigole Do this on your linux machine:

showmount -e 10.1.11.64

I’m not sure if that works with windows server, but if it does, it should basically give you the answer.

[arnaudrigole]

@Quazz
It returns me “Export list for 10.1.11.64: /FOG (everyone)”

[Quazz]

@arnaudrigole Seems like you don’t have an export for /FOG/Images only for /FOG. Can you mount /FOG over NFS?

[arnaudrigole]

@Quazz
Ok i did
umount /srv/nfs/SRVADM/Images then
mount -t nfs 10.1.11.64:/FOG /srv/nfs/SRVADM/Images -> command seems to be ok but…
cd /srv/nfs/SRVADM/Images -> -bash: cd: /srv/nfs/SRVADM/Images/: Input/Output error

showmount -e 10.1.11.64
Export list for 10.1.11.64:
/FOG (everyone)

you right, the nfs share on Windows server is defined only on /FOG, but it still the same …

[Quazz]

@arnaudrigole I’m not experienced with AD, so I had to use some googlefu and it seems like this is an issue with AD mapping unix users.

Check out this link on what to try: http://blogs.msdn.com/b/sfu/archive/2007/04/19/mounting-nfs-share-on-nfs-client.aspx

[Sebastian Roth]

@Quazz Good catch! As well @arnaudrigole you might want to look into the article on the same blog explaining the UID mapping a little closer: http://blogs.msdn.com/b/sfu/archive/2007/04/19/sharing-folders-over-nfs.aspx

And you might want to try the ‘nolock’ option that we use with FOG usually: mount -t nfs -o nolock 10.1.11.64:/FOG /srv/nfs/SRVADM/Images

But reading your initial post again I suppose I need to tell you that even if you are able to mount the NFS share from your Linux server you won’t be able to send your images to that NFS share from your FOG client. Re-exporting NFS shares is not possible!

• NFS share (linux) <-> FOG client: works!
• NFS share (windows) <-> FOG client: works!
• NFS share (windows) <-> NFS share (linux) <-> FOG client: does not work!

So when you get the permissions correct you still need to setup both NFS share in windows correctly (default /images and /images/dev) and/or configure storage management within the web gui accordingly! Please read this as well: https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node

[arnaudrigole]

@Quazz
Thanks for your reply, but i really think that its not a complicated problem like that…
I just never setup a NFS share between unix and Windows and i think i dont setup credentials as i should.

@Sebastian-Roth
•NFS share (windows) <-> NFS share (linux) <-> FOG client: does not work!

Maybe my problem is here!?
So whats the better solution to export images of fog server on a external storage ?

Thanks

[Sebastian Roth]

@arnaudrigole Again, please read through this wiki article: https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node

It’s not officially supported but you should be able to setup FOG as a storage node on your windows server.