[SOLVED]Unmounting NFS shares before network is brought down

I'm using networkd and I have enabled the network-wait-online service, so at boot-time my NFS shares are mounted after the network becomes available. That all works perfectly.
However, it doesn't work the other way around i.e. when shutting down. The network is brought down, and then systemd attempts to unmount the shares, which obviously doesn't work.
Have I missed a step?
Last edited by tomk (2014-07-04 12:31:47)

Strike0 wrote:I'm not using it, but reading your topic made me associate the "nfs-client.target" mentioned here: https://mailman.archlinux.org/pipermail … 26393.html
I checked this out too, but it has a lot of 'Wants' that I don't really need. Maybe I could fix it up, but I use autofs so I don't have this problem (the real autofs, not the systemd one).
% systemctl cat nfs-client.target
# /usr/lib/systemd/system/nfs-client.target
[Unit]
Description=NFS client services
Before=remote-fs-pre.target
Wants=remote-fs-pre.target
# Note: we don't "Wants=rpc-statd.service" as "mount.nfs" will arrange to
# start that on demand if needed.
Wants=rpc-gssd.service rpc-svcgssd.service
Wants=nfs-blkmap.service rpc-statd-notify.service
Before=rpc-gssd.service rpc-svcgssd.service nfs-blkmap.service
[Install]
WantedBy=multi-user.target
WantedBy=remote-fs.target
Last edited by WonderWoofy (2014-06-21 01:00:04)

Similar Messages

ProC dequeue process waits forever after network was brought down.

Hi all,
I want you to help me on the following issue.
Unfortunately I can not post the code right now, but I will try to explain, it is simple.
The DB and the process (ProC) which dequeues the message are on different machines.
The dequeue wait time is set to 10 sec. And of course there is a loop and an exception handling after the dequeue.
Now, if I drop the network connection between DB and ProC program while the process tries to dequeue,
the process will stuck on dequeue forever.
It does not throw any errors or something else, just waits there at DBMS_AQ.dequeue call.
Do you have any ideas what it is happening?

Hi,
I am experiencing the same problem,
Are there any important settings for time out or
other things that may prevent going through a hang problem!?
please help us

[Solved] Shutdown - systemd timing out attempting to unmount NFS

I have the following line in /etc/fstab:
192.168.1.5:/srv/nsf4/main /shares nfs noauto,nofail,x-systemd.automount,_netdev,x-systemd.device-timeout=14,size=32768,wsize=32768 0 0
This works properly in the sense that systemd does not hold up the system when booting, and it does mount the directory upon first access, however the system hangs at shutdown in a manner consistent with systemd shutting down the network before attempting to unmount the drive. Indeed, even when the system is running, I can manually run
systemctl stop NetworkManager.service
and a call to
systemctl status shares.mount
shows that the mount is still active.
I can't attach anything, but here's a pastebin of my shutdown log:
http://pastebin.com/rTJxZDF5
Also, here's what I get from systemctl show shares.mount:
http://pastebin.com/a9ZUeX6z
Finally, I will describe the debugging I have done to this point. First, if I manually unmount the share before shutting down, it shuts down immediately. I am using systemd's automount option, however the same thing happens without automount (or fstab for that matter - simply manually mounting an NFS share and shutting down results in the shutdown taking about 2-3 minutes). I also added additional items to the Require= and After= lines for shares.mount, specifically I tried adding network.target, NetworkManager.service, and wpa_supplicant.service. In each case, I did observe that manually running
systemctl stop NetworkManager.service
(for instance) now did cause the share to be unmounted, however if I shutdown the computer without manually stopping NetworkManager.service, for instance, it would still stall for 2 minutes before timing out.
Last edited by process91 (2015-04-02 02:20:37)

I have had similar problems, although on my system, I use fstab to mount the NAS to /mnt and then I use bind mounts to mount NAS folders to my home directory.
Without the bind mounts everything worked perfectly. WIth the bind mounts, the system would hang on shutdown/reboot.
Unfortunately, I only experience this problem with NetworkManager. I use Gnome, so would love the network integration, but this issue is a deal breaker for me. Currently I use systemd-networkd with a custom extension to show network connectivity in the Gnome panel. The shutdown process works flawlessly (bind mounts and NAS mounts both mounted and unmounted without issue).
Obviously not an ideal solution, but perhaps try using something other then NetworkManager to see if you still experience issues, if not, it does isolate the issue to being a NetworkManager problem.
I do want to go back to NetworkManager for the integration with my desktop aspect, but for now I am happy with a working system without it.
Cheers.

How to schedule a service to run before network goes down

Hi
I wrote a new smf service and added it to the repository.
When running with "stop" (when the system goes down) it sends an alert to another machine.
My question is :
How can I schedule that service to run just before network services go down?
another question, how can I schedule another service to run just BEFORE system is getting down?
Many Thanks
--me2unix

Dependencies appear to be really written and tested on the boot side, but they should work properly going down as well.
My first assumption is that you'd make a dependency on the network for your service. So it should be started after the network starts, and will wait for your service to quit before trying to shut down the network.
Now this would only apply to normal shutdowns. Also, there are mulitple services on the box that have network affects. You may need to read through several to understand their purpose and interaction to pick the correct one for your use. Probably the milestone/network will be the best choice.
Darren

Network stops before network shares are unmounted (fstab)

Hi,
I use fstab to set up my network shares. In my rc.conf I have "network" then "netfs". When shutting down, the network is stopped before the shares are unmounted so the system never shuts down; it just hangs trying to unmount them.
Is there another/better way to specify network shares or a fix for this issue?
Thanks

Hi,
I think my solution is better for mobile computers that are not always connecting to the same network: using networkmanager you can make a 'dispatcher'-script that only loads after connecting to a specified network. There are examples on the wiki.
This way, my laptop is not trying to connect to my home NFS-shares when I connect to my parents' network, which could be a security risk.

[SOLVED] advanced shell script for mount and unmount samba share

Good morning guys,
Today I've a very long question....
Hope in your help....:
I usually move from different network.
For one of those I need to mount some share that are under an ActiveDirectory server.
To do that I use samba.
Especially I've made and use the below shell script.
I know that it's so stupid but I'm a very newbie:
#!/bin/sh
echo "This is a custom script for mount my citrix share"
echo "Please insert user password (must a sudoer user)"
echo " "
sudo mount -t cifs -o username='myusername',password='mypassword' //host_ip/TsHome$/myusername /home/myuser/samba_share/TsHOME
sudo mount -t cifs -o username='myusername',password='mypassword' "//host_ip/direction" /home/myuser/samba_share/direction
echo " "
read -p "Press ENTER key to close this terminal"
exit
As I say the script work but it's so crude...!
I want/need to implement it whit the follow addictions:
1. print a feedback on mount: somenthing like "TsHOME is now mounted" or "unable to mount TsHOME"
2. check if the share are already mounted: to prevent accidentally multiple mount. If a share is already mounted I want to print something like "TsHOME is already mounted on /home/myuser/samba_share/TsHOME"
3. ask for share password (now it's in clear on script) - This is optinal
4. un-mount the share before reboot or shutdown command. That because I've notice that If i reboot or shutdown without manually un-mount the share the step of unmounting network file system became very slow
If it's no extremely difficult, can someone help me to write this script?
I know that man exist but I'm not a programmer and it's so difficult for me approch it.
Thank you in advance.
Ale
Last edited by Alexbit (2010-09-23 21:29:13)

Thank you very (VERY) much!
I've follow your information and.. it work!
If can be usefull to other this is the complete script:
#!/bin/sh
echo "This is a custom script for mount citrix share"
echo "****************************************"
echo " "
echo "Please insert domain password:"
read -s mypassword
echo " "
echo "|checking mount state...in share are not mounted mount it!|"
echo "+-------------------------------------------------------------------------+"
if grep "TsHome" /etc/mtab &>/dev/null; then
grep "TsHome" /etc/mtab | awk '{print "TsHome is already mounted on " $2}'
else
sudo mount -t cifs -o username='yourusername',password="$mypassword" //ipaddress/TsHome$ /home/Samba_share/TsHOME && echo "TsHOME is now mounted" || echo "unable to mount TsHOME"
fi
echo " "
if grep "direction" /etc/mtab &>/dev/null; then
grep "direction" /etc/mtab | awk '{print "direction is already mounted on " $2}'
else
sudo mount -t cifs -o username='yourusername',password="$mypassword" '//ipaddress/direction' /home/Samba_share/direction' && echo "direction pat is now mounted" || echo "unable to mount direction"
fi
echo " "
if grep "Area" /etc/mtab &>/dev/null; then
grep "Area" /etc/mtab | awk '{print "Area is already mounted on " $2}'
else
sudo mount -t cifs -o username='yourusername',password="$mypassword" '//ipaddress/Area' /home/Samba_share/Area && echo "Area is now mounted" || echo "unable to mount Area"
fi
echo " "
echo "All DONE!"
echo " "
read -p "Press ENTER key to close this terminal"
exit
I don't really well understand what I've to put in rc.local.shutdown....
I think somethings like:
#!/bin/bash
# /etc/rc.local.shutdown: Local shutdown script.
echo "This is a custom script for UN-mount citrix share"
echo "********************************************"
echo " "
echo "|check mount state: if mount then un-mount!|"
echo "+-------------------------------------------------------+"
echo " "
if grep "TsHome" /etc/mtab &>/dev/null; then
grep "TsHome" /etc/mtab | awk '{print "TsHome is NOT mounted -> going on..." $2}'
else
sudo umount /home/Samba_share/TsHOME && echo "TsHOME is now UN mounted" || echo "unable to UN-mount TsHOME"
fi
echo " "
if grep "direction" /etc/mtab &>/dev/null; then
grep "direction" /etc/mtab | awk '{print "direction is NOT mounted -> going on.." $2}'
else
sudo umount /home/Samba_share/direction && echo "direction is now UN mounted" || echo "unable to UN-mount direction pat"
fi
echo " "
if grep "Area" /etc/mtab &>/dev/null; then
grep "Area" /etc/mtab | awk '{print "Area is NOT mounted - Finished" $2}'
else
sudo umount /home/Samba_share/Area && echo "Area is now UN mounted" || echo "unable to UN-mount Area"
fi
echo " "
echo "going shutdown"
echo " "
sleep 5
I've try but it seems to ignore the IF statement... this is the output when ALL share are UNmounted:
$ sh /etc/rc.local.shutdown
This is a custom script for UN-mount citrix share
|check mount state: if mount then un-mount!|
+-------------------------------------------------------+
umount: /home/Samba_share/TsHOME: not mounted
unable to UN-mount TsHOME
umount: /home/Samba_share/direction: not mounted
unable to UN-mount direction
umount: /home/Samba_share/Area: not mounted
unable to UN-mount Area
going shutdown
Tomorrow I will test again when I'm at office.
Meanwhile can you check if I made a macroscopic mistakes?
Thank you again!
Last edited by Alexbit (2010-09-23 17:34:49)

[SOLVED] MPD through mounted NFS Share

Hi all. I am using MPD paired with Ncmpcpp, and in my configuration (for both mpd & ncmpcpp) I have the music directory set to /mnt/Shares/Music which is where I am mounting a NFS share located on the local network.
However ncmpcpp seems to be only partially reading the directory. In the server directory I have two subdirectories (mp3 and ogg) but my music player seems to only be reading the mp3 directory. I have tried updating the database through ncmpcpp, restarting the computer, restarting mpd through systemctl, and even tried using symlinks within the directory (and having "follow internal" and "follow external" symlinks set to "yes" in /etc/mpd.conf).
None of these seem to work in making mpd read the ogg directory.
Edit: Mounting through NFS automatically chowns the share to the local user, so not only did I have to sudo chown -R <user>:users the music share directory on the host I also had to reconfigure my MPD settings to run as a local user as well in order to have proper permissions for the NFS share. Prior to that it was running system wide as the MPD user. This has solved the problem completely.
Last edited by felixculpa (2012-12-26 05:24:19)

WonderWoofy wrote:
Awesome, don't forget to mark your thread as [Solved] by editing your first posts. Sorry I couldn't have been of better help to you. Glad you solved it though.
Edit: I did think it kind of odd (and unlikely) that ogg would not be an automatically supported format, but the source told me otherwise... strange.
Thanks. The Arch community is awesome and I appreciate the help I get in the forums. I am currently updating the database but it is taking quiet some time, so I am not 100% I have fixed the problem. After it is done, and if it works I will update the thread as [Solved].
Thanks again.
Edit: I forgot to mention that I was mistaken in the not reading ogg files part. It was reading only some files from both directories; it just wasn't reading the files it didn't have permission for I'm guessing.
Last edited by felixculpa (2012-12-26 03:47:46)

Custom NFS share point directory showing up on all network machines

Hi,
I'm in the process of migrating our 10.4 PowerMac server to a Mac Pro (running 10.5). I've been trying to recreate our 10.4 server setup as much as possible and so far I've only come across one annoying issue.
We have fink installed on the server and under our 10.4 setup the /sw directory was set up as an NFS automounted share point with a custom mount point of '/sw'. I.e. users logging into client machines saw a /sw directory and could work with that. This made it easier to add fink packages as I only needed to do this on one machine (the server). This setup worked very well under 10.4 and had been working stably for the last couple of years.
As we now have (for another month or two at least) a mix of intel and Power PC machines, I don't want to share out the (intel) server version of fink to all clients. In Server Admin, I have chosen to set the NFS protocol options to specify the IP address of just one client (an intel machine). I am only using NFS to share this directory. The plan is to add more client IP addresses as we get more intel machines.
This works for the one intel client machine. Logging in via the GUI or via ssh allows you to run programs located under the /sw directory. The problem is that a phantom /sw directory appears on all client machines, even though their IP addresses are not specified in Server Admin. The /sw directory has root/wheel permissions (for user/group) and attempting to list its contents returns 'Operation not permitted' (even with 'sudo ls /sw').
If I use Directory Utility to remove the connection to the Directory server on our main server, then the /sw directory becomes owned by root/admin and I can remove it (it appears empty). Reconnecting to the Directory Server changes the permissions back to root/wheel. It is also worth noting that when I first installed fink on the server (in /sw) the act of making this a share point also changed the permissions on /sw to root/wheel meaning that I couldn't access the fink programs that I had only just installed (this forced me to reinstall fink in /Volumes/Data/fink).
Has anyone else noticed this behavior? It almost seems like Server Admin is not honoring the list of IP addresses that are being listed as targets for client machines. I had planned to install fink locally on the PowerPC clients until we upgrade them to intel machines. However, I would then also have to install fink somewhere other than /sw as I can't write to that directory. I would presume that this behavior should happen on any NFS share point that is trying to automount to a custom mount point on a client. Can anyone else verify this?
Regards,
Keith

As a footnote. I have now removed my shared fink installation. It is no longer listed as an NFS sharepoint in Server Admin and running the 'showmount -e' command does not list it. However, a /sw directory is still being created on the server and on the client machines on our network.
This is perplexing and frustrating. There is no sharepoint any more. I rebooted the server but it makes no difference. I removed the /sw directory (on the server) by booting the machine in target firewire mode and removing it by using a 2nd machine. But following the restart, it appeared again.
This suggests that once you make any custom mountpoint (using NFS sharing) then you will forever be stuck with a directory at the root level of all your clients which you can not remove.
Keith

"Network Error - 53" while trying to mount NFS share in Windows Server 2008 client

CentOS | Windows 2008
I've got a CentOS 5.5 server running nfsd. On the Windows side, I'm running Windows Server 2008 R2 Enterprise. I have the "Files Services" server role enabled and both Client for NFS and Server for NFS are on.
I'm able to successfully connect/mount to the CentOS NFS share from other linux systems but am experiencing errors connecting to it from Windows. When I try to connect, I get the following:
C:\Users\fooadmin>mount -o anon 10.10.10.10:/share/ z:
Network Error - 53
Type 'NET HELPMSG 53' for more information.
(IP and share name have been changed to protect the innocent :-) )
Additional information:
I've verified low-level network connectivity between the Windows client and the NFS server with telnet (to the NFS on TCP/2049) so I know the port is open. I've further confirmed that inbound and outbound firewall ports are present and enabled.
I came across a
Microsoft tech note that suggested changing the "Provider Order" so "NFS Network" is above other items like Microsoft Windows Network. I changed this and restarted the NFS client - no luck.
I've confirmed that the share folder on the NFS server is readable/writable by all (777)
I've tried other variations of the mount command like: mount 10.10.10.10:/share/ z: and
mount 10.10.10.10:/share z: and mount -o anon mtype=hard \\10.10.10.10:/share * No luck.
As per the command output, I tried typing NET HELPMSG 53 but that doesn't tell me much. Just "The network path was not found".
I'm lost on how to proceed with troubleshooting. Any ideas?

There are usully two aspect that come to mind:
1. Syntax of mount command
2. Mismatch of NFS versions
Third reason is here
http://blogs.technet.com/b/sfu/archive/2011/11/21/getting-network-error-53-network-path-not-found-quot.aspx
Rgds
Milos

Slow unmounting NFS [SOLVED]

Hello, i need help, please.
Since i start using nfs4, when i shutdown the machine (NFS client) it takes almost 2 minutes to unmount the nfs.
This is my fstab config:
192.168.3.1:/nfs /nfs nfs rw,intr,bg,hard,rsize=65638,wsize=65536 0 0
192.168.3.1:/nfs2 /nfs2 nfs rw,intr,bg,hard,rsize=65638,wsize=65536 0 0
192.168.3.1:/nfs3 /nfs3 nfs rw,intr,bg,hard,rsize=65638,wsize=65536 0 0
192.168.3.1:/var/cache/pacman/pkg /var/cache/pacman/pkg nfs rw,intr,bg,hard,rsize=65638,wsize=65536 0 0
I already tryed to use nfs4 fs type but it didn't work. It didn't mount the nfs. Something like file not found (from server).
Thanks a lot for the help.
Last edited by amadlopes (2009-11-16 10:51:36)

I had the problem when unmount nfs at halt/reboot , it seems to work with "nolock" see ;
http://bbs.archlinux.org/viewtopic.php?id=16201
Running lastes arch/nfs and mounting a openbsd nfs share, ubuntu did not have any problems with the nfs share !!

Nautilus NFS shares listed under both Devices and Network

I have several NFS shares from my home server that I mount using fstab. I am running a fully up to date installation of Gnome 3.12. However, as my subject indicates, my NFS shares appear under both Devices and Network in Nautilus. I've done some searching and not found much about this. It is redundant and most importantly space wasting to have two lists of the same entries. Is there a way I can eliminate this duplication? Thanks.
Here is what I'm using in fstab to mount the shares:
nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,rw,rsize=32768,wsize=32768,timeo=14,hard,intr,user 0 0

I indicated that I was trying to mount several NFS shares off my home server. I should have mentioned that these are NOT NFSv4 shares. Originally, I had the mount points inside my home folder. I've since moved them in the /mnt directory and don't have duplicate entries. Well, I don't have any entries under either Network or Devices. I've made links to the directories where the NFS shares are mounted. I was more curious if this was a bug with Nautilus or my own error as having the mount points in my home directory with other file browsers such as Dolphin in KDE did not yield duplicate entries with the same fstab mount options.
I guess the long and short of it is that if you are using Nautilus, have your NFS mount points outside your home folder.
Thanks.

[SOLVED] Problem mounting nfs shares

Hello everybody,
I keep getting the following error when I try to mount an NFS share;
mount.nfs4: an incorrect mount option was specified
The corresponding line in /etc/fstab is this:
pc-francois.local:/francois /mnt/pc-francois nfs4 rw,port=2049,noauto,users,intr 0 0
showmount -e pc-francois.local gives this:
Export list for pc-francois.local:
/export/archives 192.168.1.0/24
/export/portage 192.168.1.0/24
/export/francois 10.8.0.0/24,192.168.1.0/24
/export 10.8.0.0/24,192.168.1.0/24
Finally, the nfs related modules are loaded. lsmod | grep nfs gives this:
nfsv4 129119 0
nfsd 228113 13
auth_rpcgss 41857 1 nfsd
nfs 118782 1 nfsv4
lockd 57996 2 nfs,nfsd
grace 1706 2 nfsd,lockd
sunrpc 170119 19 nfs,nfsd,auth_rpcgss,lockd,nfsv4
It works perfectly fine from other client not running on arch linux. Like indicated in the howto, I have enabled and started the services rpcbind.service,nfs-client.target and remote-fs.target
Can somebody explains what is happening ?
Last edited by FrançoisVal (2015-05-02 16:48:14)

I finally solved my problem by changing the mount options to this in fstab:
pc-francois.local:/francois /mnt/pc-francois nfs4 rw,proto=tcp,vers=4.0,noauto,users,intr 0 0
One week to find it... Maybe it wants to use nfs 4.1 by default.

[SOLVED] NFS share not mounting at boot

Hi All,
I have an NFS share listed in fstab and it doesn't mount at boot; however, when i mount -a, it mounts fine. Any thoughts?
Thanks.
Shawn
Last edited by shawn.abdushakur (2011-05-06 12:21:27)

@damnshock: Good point . Here it is:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 swap swap defaults 0 0
LABEL=arch / ext4 defaults 0 1
UUID=c1a8b2e0-bf9e-4382-ac4e-15c2aec65090 /srv/nfs ext3 defaults 0 0
/srv/nfs/shawn/Documents /home/shawn/Documents none bind
/srv/nfs/shawn/Downloads /home/shawn/Downloads none bind
/srv/nfs/shawn/Music /home/shawn/Music none bind
/srv/nfs/shawn/Pictures /home/shawn/Pictures none bind
/srv/nfs/shawn/Videos /home/shawn/Videos none bind
xbmc:/srv/nfs/watch /home/shawn/Downloads/torrents/watch nfs rsize=8192,wsize=8192,timeo=14,intr

Issue with special character in NFS shares

Hello,
I run a Ubuntu 10.04 server for serving my files via NFS. I have no problems mounting the NFS shares in my iMac (OS X 10.6.3). I can access all files, even the ones containing special characters in their names. I can copy, create, move them with no problem, both on Finder and on the Terminal.
The problem comes when I try to synchronize or backup files using backup tools. Files with accents in their names (á, é, ã, ç, etc) are simply ignored by the backup/sync tools I am using. I could reproduce the problem in different softwares like "ChronoSync" and "File Synchronization". Accents are a must have in my network.
I saw in other posts in this forum that there might be some incompatibilities with Unicode and special chars while using Mac OS X as a NFS client for a Linux NFS server. What strikes me is that Finder and Terminal work just OK.
Any clue?
Some details of my NFS configuration:
/etc/exports on my server:
/mnt/disco01 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
/mnt/disco02 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
/mnt/disco03 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
/mnt/disco04 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
On my iMac I moount them like this using Disk Utility's NFS tool:
URL: nfs://servidor/mnt/disco01
Mount point: /Network/disco01
Options: -P nosuid
Thanks for any help you can give me.

Well, I dug a little further and got a solution, although It make no sense to me.
So, the scenario is:
server URL: nfs://server/mnt/disco01
mount point: /Network/disco01
I was trying to synchronize a folder from the server called /Network/disco01/Música (meaning music in Portugueses) to a local folder /Users/shared/Música. I would use ChronoSync to keep the folders in sync, mirroring the NFS share to the local folder. ChronoSync was ignoring the folder.
After not being able to copy using the ChronoSync tool, I tried to copy the folder via the Finder. I could browse the nfs share using the finder, but not copy the files the local folder.
While trying to copy, I use Cmd-C then Cmd-V in the /User/shared/ folder. I noticed that first the Finder named the folder "Music" and then some instants after if would refuse to copy. Very strange.
I first renamed the "Música" folder on the NFS share to "Músicas", then everything worked allright, even Chronosync. Turns out that Música is the name of one of the system folder OS X creates on the user's home folder. It is actually a translation to the underlying name Music.
Why it was interfering with the copy of totally unrelated NFS and local folders I can really not understand.
More interesting, afterwards I renamed the NFS folder again to Música (without s) and it kept working.
I am happy now, but I have no clue as to why there was the problem, and why it got solved.
Hope this helps somebody in a similar situation.

CM Repository for NFS share

Hello,
We are on EP 7.0 sp14 (windows) and currently have several CM repositories pointing to external Windows File shares.
Is it possible to point CM Repository to NFS share?
Thanks,
Alex
Edited by: Alex Trosman on Jan 13, 2009 10:14 PM

Hi Ramalakshmi,
you are using a CM Repository in FSDB Mode. Am I right? If so, check the following:
1. Did you configure your Network Path? The specified user should have full access to the resource.
2. Did you configure the Root Directory? Note: The Root Directory in your Repository Manager mustn't point to the same directory of your network path!!
3. Did you configure the Root Directory for Versions? Note: The Root Directory for Versions mustn't be a subfolder of your Root Directory!! Must point to a folder which contains the subfolders "versions, workingresources, workspaces, wastebasket"!
4. Persistence Mode must be set to "FSDB"
5. Windows Landscape System must be the same as your Network Path.
Hope this helps and will solve your issue.
Best regards,
Denis

[SOLVED]Unmounting NFS shares before network is brought down

Similar Messages

Maybe you are looking for