Bug 858378

Summary: NFS volume not mounted on boot
Product: [Fedora] Fedora Reporter: Pete Zaitcev <zaitcev>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bfields, jlayton, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-13 10:02:32 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Pete Zaitcev 2012-09-18 15:49:23 EDT
Description of problem:

After a boot, volume not mounted.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Add an NFS share in /etc/fstab (make sure it's not "noauto")
2. reboot
Actual results:

Filesystem is not mounted.

Expected results:

Filesystem is mounted.

Additional info:

# /etc/fstab
# Created by anaconda on Wed Jun 13 20:14:17 2012
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
/dev/mapper/vg_kvm--ichi-lv00 /                 ext4    defaults        1 1
UUID=65e38f15-bfb8-4eac-8f3e-bd4bf732c388 /boot ext2    defaults        1 2
/dev/mapper/vg_kvm--ichi-lvswap swap            swap    defaults        0 0
/dev/vdb		/mnt/vdb		xfs	defaults	1 2
/dev/vdc		/mnt/vdc		xfs	defaults	1 2
simbelmyne:/q/zaitcev   /q/zaitcev              nfs     noatime,nolock,defaults 1 2
simbelmyne.zaitcev.lan:/g	/mnt/g    glusterfs	defaults,_netdev,noauto 0 0

This actually started after a "yum update" in F17 before the system
was upgraded to F18 Alpha 3. There's also another box with the same
problem that has Rawhide. Probably very similar packages all across
the current F17, F18, and Rawhide.

This used to work, fstab not changed.

Running "mount /q/zaitcev" after boot succeeds.

Component may be not nfs-utils. No clue what the problem is really.
Comment 1 Steve Dickson 2012-10-13 10:02:32 EDT
I added a NFS mount entry to /etc/fstab on both a updated f17 VM and a f18 VM. The file system got mount on a reboot on both VMs... So whatever was broken has not heeled... The next time this happen, as root, type "mount -a" to see the error message.