Bug 1418312
| Summary: | NFS mounts at boot time not working under IPv6 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | dan |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | bcodding, bfields, dan, jlayton, johannbg, lnykryn, msekleta, muadda, smayhew, ssahani, s, steved, systemd-maint, todd_lewis, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-29 11:20:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
(In reply to dan from comment #0) > Description of problem: > > I have a number of filesystems mounted via fstab as part of the boot > process. All was working fine under IPv4. After switching to IPv6 for NFS, > the mounts fail at boot time. After boot, I can perform a mount -a and they > will mount fine. > > Here are the nfs related lines from /etc/fstab: > > nas469l:/share/Multimedia /mnt/Multimedia nfs noatime,intr 0 2 > nas469l:/share/homes /mnt/homes nfs noatime,intr 0 2 > nas469l:/share/Common /mnt/common nfs noatime,intr 0 2 > nas469l:/share/vmwin10pro-backup /mnt/vmwin10pro-backup nfs > noatime,intr 0 2 > nas469l:/share/ears-backup /mnt/ears-backup nfs noatime,intr 0 2 > > Here as an errors from the journal: > > ● mnt-homes.mount - /mnt/homes > Loaded: loaded (/etc/fstab; generated; vendor preset: disabled) > Active: failed (Result: exit-code) since Wed 2017-02-01 09:01:18 EST; > 6min ago > Where: /mnt/homes > What: nas469l:/share/homes > Docs: man:fstab(5) > man:systemd-fstab-generator(8) > Process: 1698 ExecMount=/usr/bin/mount nas469l:/share/homes /mnt/homes -t > nfs -o noatime,intr (code=exited, status=32) Doing the mount by had, not going through systemd, work? > This seems to indicate a name resolution error but the issue also occurs > with an /etc/hosts entry pointing to the IP address of the V6 NFS host. Even when you do the mount by hand? > > As a workaround, I can add noauto,x-systemd.automount to the fstab line and > the errors do not occur and the mount is done on demand. I've seen problem with systemd handling IPv6 addresss... Once the system it up, I can login, do a mount -a and all filesystems, including those failing at boot time, will mount properly without error. (In reply to dan from comment #2) > Once the system it up, I can login, do a mount -a and all filesystems, > including those failing at boot time, will mount properly without error. Fair enough... I'm going to switch this over to the systemd folks for them to take a look, since does not appear to be an NFS problem. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Tested under FC26, mounts are failing with dependency at boot time. However, after boot, mount -a works. From the systemd journal. Something needed at remote-fs.target is not found. mnt-vmwin10pro\x2dbackup.mount: Mount process exited, code=exited status=32 Failed to mount /mnt/vmwin10pro-backup. Dependency failed for Remote File Systems. remote-fs.target: Job remote-fs.target/start failed with result 'dependency'. mnt-vmwin10pro\x2dbackup.mount: Unit entered failed state. mnt-ears\x2dbackup.mount: Mount process exited, code=exited status=32 I'm getting the same thing on f27, kernel-4.14.6-300.fc27.x86_64, nfs-utils-2.2.1-1.rc2.fc27.x86_64. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: I have a number of filesystems mounted via fstab as part of the boot process. All was working fine under IPv4. After switching to IPv6 for NFS, the mounts fail at boot time. After boot, I can perform a mount -a and they will mount fine. Here are the nfs related lines from /etc/fstab: nas469l:/share/Multimedia /mnt/Multimedia nfs noatime,intr 0 2 nas469l:/share/homes /mnt/homes nfs noatime,intr 0 2 nas469l:/share/Common /mnt/common nfs noatime,intr 0 2 nas469l:/share/vmwin10pro-backup /mnt/vmwin10pro-backup nfs noatime,intr 0 2 nas469l:/share/ears-backup /mnt/ears-backup nfs noatime,intr 0 2 Here as an errors from the journal: ● mnt-homes.mount - /mnt/homes Loaded: loaded (/etc/fstab; generated; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2017-02-01 09:01:18 EST; 6min ago Where: /mnt/homes What: nas469l:/share/homes Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 1698 ExecMount=/usr/bin/mount nas469l:/share/homes /mnt/homes -t nfs -o noatime,intr (code=exited, status=32) Feb 01 09:01:18 zzz.com systemd[1]: Mounting /mnt/homes... Feb 01 09:01:18 zzz.com mount[1698]: mount.nfs: Failed to resolve server nas469l: Name or service not known Feb 01 09:01:18 zzz.com systemd[1]: mnt-homes.mount: Mount process exited, code=exited status=32 Feb 01 09:01:18 zzz.com systemd[1]: Failed to mount /mnt/homes. Feb 01 09:01:18 zzz.com systemd[1]: mnt-homes.mount: Unit entered failed state. This seems to indicate a name resolution error but the issue also occurs with an /etc/hosts entry pointing to the IP address of the V6 NFS host. As a workaround, I can add noauto,x-systemd.automount to the fstab line and the errors do not occur and the mount is done on demand.