Re: Fedora 20 nfs
On Thu, 2013-10-17 at 19:18 -0700, T.C. Hollingsworth wrote: > On Thu, Oct 17, 2013 at 12:06 AM, Mike Chambers wrote: > > With the fix above, the really wait script now works. Rebooted twice to > > be sure and the nfs dir got mounted both times as it should. Thanks for > > that :) > > > > So it is nm-online that is saying it's online when really it's not? > > Then obviously everything else tries to do it's thing since network > > should be up? > > Yup. > > > Guess I need to change systemd bug to nm-online or whatever > > bug/component that falls under. > > It's just NetworkManager. I went ahead and moved your bug and added a > comment explaining what we figured out here. I saw that, and big thanks for the help. Wish a lot of problems and/or issues got figured out like that or close. Sometimes (few but not the majority) people spend way too much energy arguing/complaining/whinning when they could had just helped the person that had the issue. Not everyone is a developer/programmer, some (as myself) are more power users that want to help test and what not and just need some guidance or pointed in the right direction, obviously as long as they do their point and get info or whatever the helper needs to help diagnose and not just state something wrong and leave. Anyway, big thanks and putting your name on my contact list!! (j/k lol) -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Thu, Oct 17, 2013 at 2:09 PM, Eric Blake wrote: > Well, now it's failing to mount on boot: Did you change anything yet? That kind of looks like the same exact bug Mike is running into. But "bg" mounts are supposed to keep trying to mount in a loop, and automounts ought not to even try to mount until you access them, so you shouldn't even be running into that?? -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Thu, Oct 17, 2013 at 12:06 AM, Mike Chambers wrote: > With the fix above, the really wait script now works. Rebooted twice to > be sure and the nfs dir got mounted both times as it should. Thanks for > that :) > > So it is nm-online that is saying it's online when really it's not? > Then obviously everything else tries to do it's thing since network > should be up? Yup. > Guess I need to change systemd bug to nm-online or whatever > bug/component that falls under. It's just NetworkManager. I went ahead and moved your bug and added a comment explaining what we figured out here. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On 10/14/2013 04:59 PM, T.C. Hollingsworth wrote: >> nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 > > Okay, so the "bg" option is a little different from what most people > refer to as automounting, in that it just repeatedly attempts to mount > the share until it succeeds, whereas true automounting waits until you > attempt to access the mount to even try to mount it. Of course, this > distinction matters very little to _you_, but it might indicate what > systemd is getting wrong here. > > I'm curious as to whether systemd even tracks the mount properly in > this case. Does `systemctl status mnt-backup.mount` indicate success > or failure? Well, now it's failing to mount on boot: # systemctl status mnt-backup.mount -l mnt-backup.mount - /mnt/backup Loaded: loaded (/etc/fstab) Active: failed (Result: exit-code) since Mon 2013-10-14 15:01:58 MDT; 2 days ago Where: /mnt/backup What: nas:/backup Oct 14 15:01:58 office mount[1403]: mount.nfs: mount system call failed Oct 14 15:01:58 office systemd[1]: mnt-backup.mount mount process exited, code=exited status=32 Oct 14 15:01:58 office systemd[1]: Failed to mount /mnt/backup. Oct 14 15:01:58 office systemd[1]: Unit mnt-backup.mount entered failed state. > > If it indicates success, systemd definitely should be tearing down the > mount on shutdown. (systemd by design is supposed to reverse > Before/After deps for stop operations.) Definitely file a bug in this > instance. > > If it indicates failure, systemd isn't getting informed that this > mount actually succeeds. You could file a bug against systemd > regarding this, but their answer might just be "use real automounting > if you want this to work properly." To do that, switch your "bg" mount > option for "x-systemd.automount" and see if it gets unmounted properly > on shutdown afterwards. > > Their answer could just as easily be "yeah, we need to fix this", so > please do file the bug anyway, if only for the benefit of others who > might run into this. I'll probably wait to reproduce it succeeding at boot before filing a BZ about failing at shutdown... -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Wed, 2013-10-16 at 17:10 -0700, T.C. Hollingsworth wrote: > On Tue, Oct 15, 2013 at 8:33 AM, Mike Chambers wrote: > > Tried your script but got an exit code, ugh can't remember it now. > > That was my fault, sorry. The quoting was screwed up and an escape > character was transposed. (I blame Monday. :-p) > > The correct line should be: > > ExecStart=/bin/bash -c "until ifconfig p5p1 | grep '192\.168'; do > continue; done" > > (Also make sure it's all on one line despite my mailer's insistence > that it should be two. ;-) With the fix above, the really wait script now works. Rebooted twice to be sure and the nfs dir got mounted both times as it should. Thanks for that :) So it is nm-online that is saying it's online when really it's not? Then obviously everything else tries to do it's thing since network should be up? Guess I need to change systemd bug to nm-online or whatever bug/component that falls under. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Tue, Oct 15, 2013 at 8:33 AM, Mike Chambers wrote: > Tried your script but got an exit code, ugh can't remember it now. That was my fault, sorry. The quoting was screwed up and an escape character was transposed. (I blame Monday. :-p) The correct line should be: ExecStart=/bin/bash -c "until ifconfig p5p1 | grep '192\.168'; do continue; done" (Also make sure it's all on one line despite my mailer's insistence that it should be two. ;-) Also, come to think of it, skipping right to a ping test might be most accurate: ExecStart=/bin/bash -c "until ping -c1 8.8.8.8; do continue; done" Feel free to swap out Google's IP address for your NFS server or something if you'd like. >> 3.) NM-wait-online is working fine, but systemd isn't waiting for it >> for some reason. > > I think above is the problem, but can't swear to it.' sti Actually, looking at the log you posted in that bug, NM-wait-online is in fact returning successfully before systemd attempts to mount your NFS share, so it is indeed one of: 1.) The `nm-online` tool lies. 2.) NFS is failing for some other random reason other than the network not being up. Either way, it's not a systemd bug. Fixing really-wait-online.service as described above will narrow down whether it's 1 or 2. If it's 1, you'll already have a temporary fix working and can complain to the NetworkManager folks. If NFS mounts still fail, it is most definitely not the network, so file a bug against nfs-utils and let them try and troubleshoot their obtuse error output. > Got confused on your above temp fix. So adding home-download.mount to the > end of the Before line, in my wait.online service file? Shouldn't be necessary. As I said above, your logs indicate systemd is in fact doing what it is supposed to without this hack. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Tue, 2013-10-15 at 10:33 -0500, Mike Chambers wrote: > On Mon, 2013-10-14 at 14:18 -0700, T.C. Hollingsworth wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1019415 One thing that has happened or noticed, was just *1* time my nfs dir got auto mounted. It looks like either NM got configured 1st/earlier or systemd actually waited until NM was configured then did it's thing. In both cases, I was using the default NM-wait-online.service so had official services running before filing the bug. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, 2013-10-14 at 14:18 -0700, T.C. Hollingsworth wrote: > 1.) DHCP on your network is slw and NetworkManager-wait-online is > timing out after the default 30s waiting for it. My dhcp server is a cisco linksys e3000 wire/wireless router that I have been using for year or two now, and it works fine. Worked just fine on F19 with no issues of this nature. > > 2.) NetworkManager-wait-online is just stupid and doesn't wait for > DHCP to complete. Tried your script but got an exit code, ugh can't remember it now. > > 3.) NM-wait-online is working fine, but systemd isn't waiting for it > for some reason. I think above is the problem, but can't swear to it.' > > I believe something in the logs would indicate if it's 1. If that's > the case, you can increase the timeout by copying > /usr/lib/systemd/system/NetworkManager-wait-online.service to > /etc/systemd/system/ (so rpm doesn't overwrite your changes on > updates) and increasing the `-t` argument to `nm-online` in that file. Changed it to 120 secs but still no go. Heck there was only 8 seconds between trying to mount the nfs share and dhcp getting configured. > > If it's 2, file a bug against NetworkManager, which ships the > `nm-online` program that is being stupid. :-p If it's 3, systemd > obviously deserves the bug. > > Well, lets try a more systemd-esque hack that will also identify > whether the problem is 2 or 3 as described above. Drop something like > this in /etc/systemd/system/really-wait-online.service: > -- > [Unit] > Description=Really wait for the damn network > Requisite=NetworkManager.service > After=NetworkManager.service > Wants=network.target > Before=network.target network-online.target > > [Service] > Type=oneshot > ExecStart=/bin/bash -c 'until ifconfig p5p1 | grep '192.\168'; do > continue; done' > TimeoutSec=120 > > [Install] > WantedBy=multi-user.target > -- > > Remember to adjust the network interface and grep string to something > that makes sense for your network, and run `systemctl daemon-reload && > systemctl enable really-wait-online.service` to enable it when you're > done. (And if you're aware of a better method for figuring out DHCP is > done than grepping the output of `ifconfig`, feel free to use it. ;-) > > If mounting works after that, NM-wait-online is really the culprit and > NetworkManager deserves the bug. If mounting still fails, systemd is > not ordering things right and deserves the bug. > > And if systemd is to blame, fix your system nao by explicitly ordering > your little wait-online service before the mount unit (e.g. > mnt-foo.mount) discussed upthread. Just add said mount unit to the > end of the Before line in that file. > Got confused on your above temp fix. So adding home-download.mount to the end of the Before line, in my wait.online service file? -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, Oct 14, 2013 at 2:41 PM, Eric Blake wrote: > Dunno. Whatever I got by installing F17 with anaconda then > incrementally upgrading through F18, F19, and now F20, and where I set > up my /etc/fstab by copying the same configuration that worked for me > since F12 pre-systemd days. So it might not be ideal, but it's one of > those "it works well enough for me that I'm not going to waste time > tweaking it unless it breaks first" situations. Except that it's > noticeably broken enough at shutdown that I bothered to ask on the list :) > > The corresponding /etc/fstab entry: > > nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 Okay, so the "bg" option is a little different from what most people refer to as automounting, in that it just repeatedly attempts to mount the share until it succeeds, whereas true automounting waits until you attempt to access the mount to even try to mount it. Of course, this distinction matters very little to _you_, but it might indicate what systemd is getting wrong here. I'm curious as to whether systemd even tracks the mount properly in this case. Does `systemctl status mnt-backup.mount` indicate success or failure? If it indicates success, systemd definitely should be tearing down the mount on shutdown. (systemd by design is supposed to reverse Before/After deps for stop operations.) Definitely file a bug in this instance. If it indicates failure, systemd isn't getting informed that this mount actually succeeds. You could file a bug against systemd regarding this, but their answer might just be "use real automounting if you want this to work properly." To do that, switch your "bg" mount option for "x-systemd.automount" and see if it gets unmounted properly on shutdown afterwards. Their answer could just as easily be "yeah, we need to fix this", so please do file the bug anyway, if only for the benefit of others who might run into this. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On 10/14/2013 03:27 PM, T.C. Hollingsworth wrote: > On Mon, Oct 14, 2013 at 9:04 AM, Eric Blake wrote: >> I've got a similar problem - I've got my laptop set up to automount an >> NFS share over wifi, and frequently hit a hang during system shutdown >> because systemd allows Networkmanager (and the wifi) to be taken down >> before NFS is fully unmounted, where the system then stalls for several >> minutes waiting for the NFS unmount that is impossible at that point. I >> have no idea where to look at adding a dependency that says that yes, my >> wifi network connection really must have a longer lifetime on BOTH sides >> of the NFS mount point. > > Are you using systemd's automounting logic or plain ol' autofs? Dunno. Whatever I got by installing F17 with anaconda then incrementally upgrading through F18, F19, and now F20, and where I set up my /etc/fstab by copying the same configuration that worked for me since F12 pre-systemd days. So it might not be ideal, but it's one of those "it works well enough for me that I'm not going to waste time tweaking it unless it breaks first" situations. Except that it's noticeably broken enough at shutdown that I bothered to ask on the list :) The corresponding /etc/fstab entry: nas:/backup /mnt/backup nfs bg,user,_netdev 0 0 # systemctl list-dependencies mnt-backup.mount mnt-backup.mount ├─-.mount ├─system.slice └─network-online.target └─NetworkManager-wait-online.service -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, Oct 14, 2013 at 9:04 AM, Eric Blake wrote: > I've got a similar problem - I've got my laptop set up to automount an > NFS share over wifi, and frequently hit a hang during system shutdown > because systemd allows Networkmanager (and the wifi) to be taken down > before NFS is fully unmounted, where the system then stalls for several > minutes waiting for the NFS unmount that is impossible at that point. I > have no idea where to look at adding a dependency that says that yes, my > wifi network connection really must have a longer lifetime on BOTH sides > of the NFS mount point. Are you using systemd's automounting logic or plain ol' autofs? -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Mon, Oct 14, 2013 at 8:56 AM, Mike Chambers wrote: > Ok, think I've figured out the problem, but might be beyond my expertise > to fix it.. > > 1 - Network Manager is set to come online/start > 2 - Network Manger wait-online shows in log as well here. > 3 - Network Manger device itself shows up (as in I guess drivers and > assigned what name it is called, p5p1 is my wired ethernet). > 4 - Systemd tries here to mount the remote nfs directory, which fails > 5 - Network Manger actually configures itself, via dhcp, to get it's > network settings, such as IP, dns, etc.. > > So it seems, via /var/log/messages that nfs is trying to get mounted > BEFORE the network is completely configured. There are several possibilities here: 1.) DHCP on your network is slw and NetworkManager-wait-online is timing out after the default 30s waiting for it. 2.) NetworkManager-wait-online is just stupid and doesn't wait for DHCP to complete. 3.) NM-wait-online is working fine, but systemd isn't waiting for it for some reason. I believe something in the logs would indicate if it's 1. If that's the case, you can increase the timeout by copying /usr/lib/systemd/system/NetworkManager-wait-online.service to /etc/systemd/system/ (so rpm doesn't overwrite your changes on updates) and increasing the `-t` argument to `nm-online` in that file. If it's 2, file a bug against NetworkManager, which ships the `nm-online` program that is being stupid. :-p If it's 3, systemd obviously deserves the bug. > So no idea which one is wrong, either mounting gets done alot later > (guess I could add to rc.local again like used to until fixed?), or NM > needs to be configured a lot earlier. Well, lets try a more systemd-esque hack that will also identify whether the problem is 2 or 3 as described above. Drop something like this in /etc/systemd/system/really-wait-online.service: -- [Unit] Description=Really wait for the damn network Requisite=NetworkManager.service After=NetworkManager.service Wants=network.target Before=network.target network-online.target [Service] Type=oneshot ExecStart=/bin/bash -c 'until ifconfig p5p1 | grep '192.\168'; do continue; done' TimeoutSec=120 [Install] WantedBy=multi-user.target -- Remember to adjust the network interface and grep string to something that makes sense for your network, and run `systemctl daemon-reload && systemctl enable really-wait-online.service` to enable it when you're done. (And if you're aware of a better method for figuring out DHCP is done than grepping the output of `ifconfig`, feel free to use it. ;-) If mounting works after that, NM-wait-online is really the culprit and NetworkManager deserves the bug. If mounting still fails, systemd is not ordering things right and deserves the bug. And if systemd is to blame, fix your system nao by explicitly ordering your little wait-online service before the mount unit (e.g. mnt-foo.mount) discussed upthread. Just add said mount unit to the end of the Before line in that file. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On 10/14/2013 09:56 AM, Mike Chambers wrote: > On Sun, 2013-10-13 at 18:24 -0700, T.C. Hollingsworth wrote: > >> One thing I forgot that's always an issue...do you use NetworkManager >> or ye olde network service? If it's the former, try running >> `systemctl enable NetworkManager-wait-online` and rebooting. >> Sometimes systemd tries to mount stuff before NM gets the network up. >> (I thought they had fixed this to just do the right thing when remote >> FSes were in the mix nowadays, but maybe I'm mistaken. Or it broke >> again with F20??) > > Ok, think I've figured out the problem, but might be beyond my expertise > to fix it.. > > 1 - Network Manager is set to come online/start > 2 - Network Manger wait-online shows in log as well here. > 3 - Network Manger device itself shows up (as in I guess drivers and > assigned what name it is called, p5p1 is my wired ethernet). > 4 - Systemd tries here to mount the remote nfs directory, which fails > 5 - Network Manger actually configures itself, via dhcp, to get it's > network settings, such as IP, dns, etc.. > > So it seems, via /var/log/messages that nfs is trying to get mounted > BEFORE the network is completely configured. > > So no idea which one is wrong, either mounting gets done alot later > (guess I could add to rc.local again like used to until fixed?), or NM > needs to be configured a lot earlier. I've got a similar problem - I've got my laptop set up to automount an NFS share over wifi, and frequently hit a hang during system shutdown because systemd allows Networkmanager (and the wifi) to be taken down before NFS is fully unmounted, where the system then stalls for several minutes waiting for the NFS unmount that is impossible at that point. I have no idea where to look at adding a dependency that says that yes, my wifi network connection really must have a longer lifetime on BOTH sides of the NFS mount point. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sun, 2013-10-13 at 18:24 -0700, T.C. Hollingsworth wrote: > One thing I forgot that's always an issue...do you use NetworkManager > or ye olde network service? If it's the former, try running > `systemctl enable NetworkManager-wait-online` and rebooting. > Sometimes systemd tries to mount stuff before NM gets the network up. > (I thought they had fixed this to just do the right thing when remote > FSes were in the mix nowadays, but maybe I'm mistaken. Or it broke > again with F20??) Ok, think I've figured out the problem, but might be beyond my expertise to fix it.. 1 - Network Manager is set to come online/start 2 - Network Manger wait-online shows in log as well here. 3 - Network Manger device itself shows up (as in I guess drivers and assigned what name it is called, p5p1 is my wired ethernet). 4 - Systemd tries here to mount the remote nfs directory, which fails 5 - Network Manger actually configures itself, via dhcp, to get it's network settings, such as IP, dns, etc.. So it seems, via /var/log/messages that nfs is trying to get mounted BEFORE the network is completely configured. So no idea which one is wrong, either mounting gets done alot later (guess I could add to rc.local again like used to until fixed?), or NM needs to be configured a lot earlier. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sun, Oct 13, 2013 at 8:02 AM, Mike Chambers wrote: > Got this from the logs just after a reboot a few mins ago... > > Oct 13 09:58:45 scrappy systemd: Starting NFS file locking service > Oct 13 09:58:45 scrappy mount: mount.nfs4: mount system call failed > Oct 13 09:58:45 scrappy systemd: home-download.mount mount process > exited, code=exited status=32 `man 8 mount` sez an exit code of 32 means "mount failed". Very helpful. >:-( > Oct 13 09:58:45 scrappy systemd: Failed to mount /home/download. > Oct 13 09:58:45 scrappy systemd: Dependency failed for Remote File > Systems. > Oct 13 09:58:48 scrappy rsyslogd: log message from journal doesn't have > MESSAGE > Oct 13 09:58:45 scrappy systemd: Unit home-download.mount entered failed > state. One thing I forgot that's always an issue...do you use NetworkManager or ye olde network service? If it's the former, try running `systemctl enable NetworkManager-wait-online` and rebooting. Sometimes systemd tries to mount stuff before NM gets the network up. (I thought they had fixed this to just do the right thing when remote FSes were in the mix nowadays, but maybe I'm mistaken. Or it broke again with F20??) Also, double-check your network connection settings and make sure the "system connection" box is checked. I'm pretty sure this is the default (or maybe even not configurable) with GNOME, but other desktops' NM UIs sometimes don't set this, so the network doesn't come up on boot by default. If all that fails, is the above just the output from `systemctl status`? `journalctl -b` might reveal some messages from the kernel that systemctl's magic log grepper might not be picking up. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sun, 2013-10-13 at 09:48 -0500, Mike Chambers wrote: > Hrm, I checked the mount part as T.C. suggested (of course the nfs share > is already mounted, manually mind you) and that looked fine. > > Then I decided to check this... > > [root@scrappy ~]# systemctl status remote-fs.target > remote-fs.target - Remote File Systems >Loaded: loaded (/usr/lib/systemd/system/remote-fs.target; enabled) >Active: inactive (dead) > Docs: man:systemd.special(7) > > Oct 12 10:08:27 scrappy.mtchambers.com systemd[1]: Dependency failed for > Remote File Systems. > > scrappy=nfs client/workstation that I am on now and try to do the > mounting from. Got this from the logs just after a reboot a few mins ago... Oct 13 09:58:45 scrappy systemd: Starting NFS file locking service Oct 13 09:58:45 scrappy mount: mount.nfs4: mount system call failed Oct 13 09:58:45 scrappy systemd: home-download.mount mount process exited, code=exited status=32 Oct 13 09:58:45 scrappy systemd: Failed to mount /home/download. Oct 13 09:58:45 scrappy systemd: Dependency failed for Remote File Systems. Oct 13 09:58:48 scrappy rsyslogd: log message from journal doesn't have MESSAGE Oct 13 09:58:45 scrappy systemd: Unit home-download.mount entered failed state. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sun, 2013-10-13 at 14:02 +0100, Adam Williamson wrote: > On Sat, 2013-10-12 at 17:33 -0700, T.C. Hollingsworth wrote: > > On Sat, Oct 12, 2013 at 8:05 AM, Mike Chambers wrote: > > > On Thu, 2013-10-10 at 11:34 +0200, Adam Williamson wrote: > > >> Check 'remote-fs.target': this is the systemd target that controls > > >> mounting anything considered a 'remote' filesystem, similar to the old > > >> 'netfs' service. > > > > > > Looked and it is there, but not sure what to look for besides being > > > there. Any particular info that should be there? Or can someone take a > > > look after a fresh install that might know the program better to see if > > > it's missing something? > > > > Actually, you need to check the status of the mount unit itself. > > (Which is required by remote-fs.target.) > > What I was suggesting is that he should check remote-fs.target is > enabled. You're correct that checking the mount units may also be > useful, though. Hrm, I checked the mount part as T.C. suggested (of course the nfs share is already mounted, manually mind you) and that looked fine. Then I decided to check this... [root@scrappy ~]# systemctl status remote-fs.target remote-fs.target - Remote File Systems Loaded: loaded (/usr/lib/systemd/system/remote-fs.target; enabled) Active: inactive (dead) Docs: man:systemd.special(7) Oct 12 10:08:27 scrappy.mtchambers.com systemd[1]: Dependency failed for Remote File Systems. scrappy=nfs client/workstation that I am on now and try to do the mounting from. -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sat, 2013-10-12 at 17:33 -0700, T.C. Hollingsworth wrote: > On Sat, Oct 12, 2013 at 8:05 AM, Mike Chambers wrote: > > On Thu, 2013-10-10 at 11:34 +0200, Adam Williamson wrote: > >> Check 'remote-fs.target': this is the systemd target that controls > >> mounting anything considered a 'remote' filesystem, similar to the old > >> 'netfs' service. > > > > Looked and it is there, but not sure what to look for besides being > > there. Any particular info that should be there? Or can someone take a > > look after a fresh install that might know the program better to see if > > it's missing something? > > Actually, you need to check the status of the mount unit itself. > (Which is required by remote-fs.target.) What I was suggesting is that he should check remote-fs.target is enabled. You're correct that checking the mount units may also be useful, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Sat, Oct 12, 2013 at 8:05 AM, Mike Chambers wrote: > On Thu, 2013-10-10 at 11:34 +0200, Adam Williamson wrote: >> Check 'remote-fs.target': this is the systemd target that controls >> mounting anything considered a 'remote' filesystem, similar to the old >> 'netfs' service. > > Looked and it is there, but not sure what to look for besides being > there. Any particular info that should be there? Or can someone take a > look after a fresh install that might know the program better to see if > it's missing something? Actually, you need to check the status of the mount unit itself. (Which is required by remote-fs.target.) They're named by switching out slashes for for dashes in the mount point. For instance, if you have a nfs share mounted on /mnt/foo, it's mount unit is named "mnt-foo.mount" and you can find out what's going on with it by running `systemctl status mnt-foo.mount`. You can run just plain `systemctl` for a list of units if you need to. -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
No problems here using the tweeked syscon/nfs: # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) RPCNFSDARGS="-V2" The server is running 3.11.4.-301 64 bit. There is a 15 second delay on clients the first time an NFS share is mounted. On 10/12/2013 08:05 AM, Mike Chambers wrote: On Thu, 2013-10-10 at 11:34 +0200, Adam Williamson wrote: On Wed, 2013-10-09 at 09:47 -0500, Mike Chambers wrote: Did a test install of F20 64bit on my normal workstation/desktop. Problem seems to be that after I setup nfs to mount, it won't do it automatically on boot. And this usually works just fine out of the box up to F19. I have to mount the directory manually once the system is booted. Is there a particular nfs service that isn't starting/working that would do this for me or something else? Check 'remote-fs.target': this is the systemd target that controls mounting anything considered a 'remote' filesystem, similar to the old 'netfs' service. Looked and it is there, but not sure what to look for besides being there. Any particular info that should be there? Or can someone take a look after a fresh install that might know the program better to see if it's missing something? [mike@scrappy ~]$ more /lib/systemd/system/remote-fs.target # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Remote File Systems Documentation=man:systemd.special(7) After=remote-fs-pre.target DefaultDependencies=no Conflicts=shutdown.target [Install] WantedBy=multi-user.target -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Thu, 2013-10-10 at 11:34 +0200, Adam Williamson wrote: > On Wed, 2013-10-09 at 09:47 -0500, Mike Chambers wrote: > > Did a test install of F20 64bit on my normal workstation/desktop. > > > > Problem seems to be that after I setup nfs to mount, it won't do it > > automatically on boot. And this usually works just fine out of the box > > up to F19. I have to mount the directory manually once the system is > > booted. > > > > Is there a particular nfs service that isn't starting/working that > > would do this for me or something else? > > Check 'remote-fs.target': this is the systemd target that controls > mounting anything considered a 'remote' filesystem, similar to the old > 'netfs' service. Looked and it is there, but not sure what to look for besides being there. Any particular info that should be there? Or can someone take a look after a fresh install that might know the program better to see if it's missing something? [mike@scrappy ~]$ more /lib/systemd/system/remote-fs.target # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Remote File Systems Documentation=man:systemd.special(7) After=remote-fs-pre.target DefaultDependencies=no Conflicts=shutdown.target [Install] WantedBy=multi-user.target -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On Wed, 2013-10-09 at 09:47 -0500, Mike Chambers wrote: > Did a test install of F20 64bit on my normal workstation/desktop. > > Problem seems to be that after I setup nfs to mount, it won't do it > automatically on boot. And this usually works just fine out of the box > up to F19. I have to mount the directory manually once the system is > booted. > > Is there a particular nfs service that isn't starting/working that > would do this for me or something else? Check 'remote-fs.target': this is the systemd target that controls mounting anything considered a 'remote' filesystem, similar to the old 'netfs' service. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 20 nfs
On 10/09/13 22:47, Mike Chambers wrote: > Did a test install of F20 64bit on my normal workstation/desktop. > > Problem seems to be that after I setup nfs to mount, it won't do it > automatically on boot. And this usually works just fine out of the box > up to F19. I have to mount the directory manually once the system is > booted. > > Is there a particular nfs service that isn't starting/working that > would do this for me or something else? > > Just installed F20-TC2 64 bit in a VM. Added the following to the fstab 192.168.0.55:/myhome /home/egreshko/misty nfs4defaults0 0 Edited the idmap.conf and rebooted. The mount worked as expected. No need to make any changes to systemd. -- Getting tired of non-Fedora discussions and self-serving posts -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 20 nfs
Did a test install of F20 64bit on my normal workstation/desktop. Problem seems to be that after I setup nfs to mount, it won't do it automatically on boot. And this usually works just fine out of the box up to F19. I have to mount the directory manually once the system is booted. Is there a particular nfs service that isn't starting/working that would do this for me or something else? -- Mike Chambers Madisonville, KY "Best little town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
