<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NFS problems]]></title><description><![CDATA[<p dir="auto">I’m new to FOG and I’m having a bear of a time trying to get what should be a pretty basic thing working–modifying the default storage group to point to remote storage.</p>
<p dir="auto">Here’s my situation.  I’m running FOG in a Virtualbox VM (Ubuntu 12.04) on a Windows 7 platform (will later be moved to a Windows 2008R2 Server after testing).  I have a large SMB share on the Windows Server that I want to use for image storage.  I’d rather not have to get into setting up NFS on the Window Server for a variety of reasons, so I’ve mounted the SMB share on the FOG server directly (/mnt/win/fogimages).  Up to that point everything is fine.  The mount works and I can manually see/edit data on the share via command line.  The share is mounted such that the fog user is owner with 644 permissions.</p>
<p dir="auto">Now comes the FOG configuration.  Based on a variety of WIKI and other sources here is what I have done to modify the default storage group.</p>
<ol>
<li>
<p dir="auto">Edit the DefaultMember storage node settings in the web GUI.  All I did here was change the “Image Path” to point to “/mnt/win/fogimages”</p>
</li>
<li>
<p dir="auto">Updating the /var/www/fog/commons/config.php file with below:<br />
[CODE]define(‘STORAGE_DATADIR’, ‘/mnt/win/fogimages/’);<br />
define(‘STORAGE_DATADIR_UPLOAD’, ‘/mnt/win/fogimages/dev/’);[/CODE]</p>
</li>
<li>
<p dir="auto">Updating /etc/exports as such:<br />
[CODE]/mnt/win/fogimages                        *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1)<br />
/mnt/win/fogimages/dev                    *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2)[/CODE]<br />
And then restarting NFS services.</p>
</li>
</ol>
<p dir="auto">So, after all that, the web GUI reflects the proper free space and everything seems to be great.  But upon booting a client to upload an image I get the following error:[QUOTE]* Mounting File System…Failed</p>
<p dir="auto">mount: mounting 192.168.50.80:/mnt/win/fogimages/ on /images failed: Permission denied[/QUOTE]</p>
<p dir="auto">So, just for kicks I tried to mount the FOG NFS share from another Linux machine.  No go there either–it just hangs trying to mount.</p>
<p dir="auto">Can anyone give any direction?  All I want to do is use a Windows share for image storage.  A variety of blogs seem to have accomplished this in the past, so I don’t know if there is something going on with v1.0.x different than previous versions in this area.</p>
]]></description><link>http://forums.fogproject.org/topic/2983/nfs-problems</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 07:57:29 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/2983.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 03 Jun 2014 03:59:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NFS problems on Tue, 03 Jun 2014 18:59:35 GMT]]></title><description><![CDATA[<p dir="auto">I have an nfs shared through cifs, but not the other way.</p>
]]></description><link>http://forums.fogproject.org/post/23275</link><guid isPermaLink="true">http://forums.fogproject.org/post/23275</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Tue, 03 Jun 2014 18:59:35 GMT</pubDate></item><item><title><![CDATA[Reply to NFS problems on Tue, 03 Jun 2014 18:13:22 GMT]]></title><description><![CDATA[<p dir="auto">I’m thinking it may have something to do with the fact that the folder is already a remote CIFS mount.  The more I look into this it appears that there has never been support in Linux for re-exporting a CIFS share through NFS.</p>
<p dir="auto">Given that premise, is there an alternative to NFS for FOG?  Since I already have the CIFS shares, is there a way to have FOG point to a CIFS share instead of using NFS?  I’d rather not have to deal with setting up Windows NFS services–it’s pretty clear in the forums that it is something quite a few people have had problems with, and I’d rather not introduce another service that needs to be maintained.</p>
]]></description><link>http://forums.fogproject.org/post/23265</link><guid isPermaLink="true">http://forums.fogproject.org/post/23265</guid><dc:creator><![CDATA[number_one]]></dc:creator><pubDate>Tue, 03 Jun 2014 18:13:22 GMT</pubDate></item><item><title><![CDATA[Reply to NFS problems on Tue, 03 Jun 2014 17:58:03 GMT]]></title><description><![CDATA[<p dir="auto">I’ll check permissions again, but as noted in the first post I did update /etc/exports with the new locations.</p>
]]></description><link>http://forums.fogproject.org/post/23260</link><guid isPermaLink="true">http://forums.fogproject.org/post/23260</guid><dc:creator><![CDATA[number_one]]></dc:creator><pubDate>Tue, 03 Jun 2014 17:58:03 GMT</pubDate></item><item><title><![CDATA[Reply to NFS problems on Tue, 03 Jun 2014 10:36:05 GMT]]></title><description><![CDATA[<p dir="auto">Check your /etc/exports file.</p>
<p dir="auto">It’s probably set to point at /images and /images/dev</p>
<p dir="auto">Change these names to:<br />
/mnt/win/fogimages<br />
/mnt/win/fogimages/dev respectively.</p>
<p dir="auto">Also make sure the permissions are correct for these folders with:<br />
[code]touch /mnt/win/fogimages/{.mntcheck,/dev/.mntcheck}<br />
chmod 777 -R /mnt/win/fogimages[/code]</p>
<p dir="auto">Once you make the switch on the /etc/exports file  restart the nfs server with:<br />
[code]service nfs restart[/code]</p>
<p dir="auto">If you’re on ubuntu try with:<br />
[code]sudo service nfs-kernel-server restart[/code]</p>
]]></description><link>http://forums.fogproject.org/post/23157</link><guid isPermaLink="true">http://forums.fogproject.org/post/23157</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Tue, 03 Jun 2014 10:36:05 GMT</pubDate></item></channel></rss>