Unexpected NFS Auto-unmount?

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

Unexpected NFS Auto-unmount?

Postby kayasaman » Sat Feb 09, 2013 0:49

Hi,

I'm new to Sabayon as of 3 days ago :) - I guess I should post in the newbee area but for some reason my NFS mounts keep auto unmounting??

I don't have autofs installed or setup so there seems to be something else causing the issue....

This is the output from dmesg:

Code: Select all

[263434.747839] ------------[ cut here ]------------
[263434.747859] WARNING: at fs/dcache.c:2620 prepend_path+0x140/0x186()
[263434.747865] Hardware name: System Product Name
[263434.747869] Root dentry has weird name <>
[263434.747873] Modules linked in: 8021q garp stp llc xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT xt_LOG xt_limit xt_addrtype xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack xt_tcpudp ipv6 iptable_filter ip_tables x_tables nvidia(PO) coretemp r8169 gpio_ich microcode lpc_ich i2c_i801 snd_hda_codec_hdmi pl2303 usbserial joydev snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd pcspkr asus_atk0110 sha512_generic sha1_generic virtio_pci virtio_blk virtio_net virtio_console virtio_balloon virtio_ring virtio xts gf128mul cryptd aes_x86_64 sha256_generic iscsi_tcp tg3 e1000 fuse zfs(P) zcommon(P) znvpair(P) zavl(P) zunicode(P) spl xfs nfs lockd auth_rpcgss nfs_acl sunrpc jfs reiserfs ext4 jbd2 ext3 jbd ext2 mbcache scsi_wait_scan sl811_hcd hid_generic xhci_hcd ohci_hcd uhci_hcd ehci_hcd sx8 imm parport pata_pcmcia pcmcia
[263434.748058] Pid: 6691, comm: wine64 Tainted: P           O 3.5.0-sabayon #1
[263434.748063] Call Trace:
[263434.748077]  [<ffffffff8102a52c>] warn_slowpath_common+0x7e/0x96
[263434.748086]  [<ffffffff8102a5d8>] warn_slowpath_fmt+0x41/0x43
[263434.748095]  [<ffffffff810ea758>] prepend_path+0x140/0x186
[263434.748102]  [<ffffffff810ecfd4>] sys_getcwd+0x18f/0x1ad
[263434.748110]  [<ffffffff810d95af>] ? do_sys_open+0x180/0x192
[263434.748120]  [<ffffffff8180dee6>] system_call_fastpath+0x1a/0x1f
[263434.748124] ---[ end trace 26d002a22ab9d3ae ]---


With system as:

Code: Select all
3.5.0-sabayon #1 SMP Sun Nov 11 10:31:31 UTC 2012 x86_64 Intel(R) Atom(TM) CPU D525 @ 1.80GHz GenuineIntel GNU/Linux


As I'm running the same build of Sabayon on 3 systems I tried upgrading my Lenovo X220 to kernel 3.7.0-sabayon but for some reason the system started overheating... lm-sensors showed temps to be above 80 degrees C which later when reverting back to kernel 3.5 managed to cool off at back down to round 50-60 degrees C.


Could anyone help me or suggest anything?


Thanks
Last edited by kayasaman on Sun Feb 17, 2013 20:23, edited 1 time in total.
kayasaman
Young Hen
 
Posts: 29
Joined: Wed Feb 06, 2013 5:14

Re: Kernel Fault?

Postby sabayonino » Sat Feb 09, 2013 12:54

Hi

nfsmount service is enabled to default

check the service
Code: Select all
# rc-update show | grep nfsmount


if you want disable nfsmount at booot
Code: Select all
# rc-update del nfsmount default


"nfsmount " mount all "nfs" filesystem in /etc/fstab
User avatar
sabayonino
Sagely Hen
 
Posts: 2513
Joined: Sun Sep 21, 2008 1:12
Location: Italy

Re: Kernel Fault?

Postby kayasaman » Sat Feb 09, 2013 13:39

Thanks for the response!

Perhaps I didn't make myself clear??

What I have is an NFS server running FreeBSD. This machine has been running for many years and is fine.

Using Fedora 16/17/18 I added nfs to auto mount at boot:

so /etc/fstab looks like this:

Code: Select all
<server_ip:/export> </mount_point> nfs defaults 0 0


The way I want this to work is to mount at boot and stay mounted. Using Fedora versions 16-18 that's exactly how the system behaved and is the same for all Linux and UNIX derrivatives.

The issue I'm facing is that the system keeps unmounting the mount points after a period of time. For example if I leave the system on over night, the next morning the mounts won't be mounted any more.... I can verify this with:

Code: Select all
df -h


This isn't the correct behaviour of NFS though, as the mounts should stay mounted until manually the command:

Code: Select all
umount <mount_point>


is run!

If it is an NFS timeout issue it should be the same for all devices having mount points connected to the same server. This isn't the case! My Sun Fire V210 box running NetBSD stays mounted; as did Fedora 17 and 18 which I had on the desktop previously.

That's what lead me to believe it could be a kernel issue as the stack trace above occurd immediately after the mount points got auto ejected.

I seem to be only having this issue with my Sabayon machines everything else works as it should...?
kayasaman
Young Hen
 
Posts: 29
Joined: Wed Feb 06, 2013 5:14

Re: Kernel Fault?

Postby kayasaman » Sat Feb 09, 2013 13:41

Hi

nfsmount service is enabled to default

check the service
CODE: SELECT ALL
# rc-update show | grep nfsmount


if you want disable nfsmount at booot
CODE: SELECT ALL
# rc-update del nfsmount default


"nfsmount " mount all "nfs" filesystem in /etc/fstab


....or sorry, did I misunderstand???


Are you saying to run:

Code: Select all
 rc-update del nfsmount default


then mount everything in fstab?

I appologize!!! It wasn't quite clear to me :)
kayasaman
Young Hen
 
Posts: 29
Joined: Wed Feb 06, 2013 5:14

Re: Kernel Fault?

Postby sabayonino » Sat Feb 09, 2013 14:40

"rc-update del <bla bla> " remove the service

but if you need nfsmount keep to the runlevel.

please paste /var/log/rc.log .

Could you try to run
Code: Select all
# /etc/init.d/nfsmount start --nodeps

and paste its output

my nfsmouunt (for my own distfiles server) is :
Code: Select all
192.168.0.8:/mirror/distfiles          /usr/portage/distfiles          nfs     defaults,vers=3,nolock,auto,rw,retry=0.10       0 0


more options for nfs if needed :
Code: Select all
# man nfs
User avatar
sabayonino
Sagely Hen
 
Posts: 2513
Joined: Sun Sep 21, 2008 1:12
Location: Italy

Re: Kernel Fault?

Postby kayasaman » Sat Feb 09, 2013 15:05

please paste /var/log/rc.log .


I can paste more if required!

Code: Select all

rc sysinit logging stopped at Sat Feb  9 00:27:00 2013


rc boot logging started at Sat Feb  9 00:27:00 2013

 * Setting system clock using the hardware clock [UTC] ...
 [ ok ]
 * Autoloaded 0 module(s)
 * Setting up the Logical Volume Manager ...
  No volume groups found
  No volume groups found
  No volume groups found
 [ ok ]
 [ ok ]
 * Checking local filesystems  ...
/dev/sda2: clean, 255495/1602496 files, 2467358/6400000 blocks
/dev/sda3: clean, 26762/640848 files, 960214/2560000 blocks
 [ ok ]
 * Remounting root filesystem read/write ...
 [ ok ]
 * Remounting filesystems ...
 [ ok ]
 * Updating /etc/mtab ...
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
 [ ok ]
 * Starting ZFS ...
 * Checking if zfs userspace tools present
 * Mounting ZFS filesystems
 * Exporting ZFS filesystems
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Cleaning /var/run ...
 [ ok ]
 * Wiping /tmp directory ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting console font [LatArCyrHeb-16] ...
 [ ok ]
 * Starting D-BUS system messagebus ...
 [ ok ]
 * Starting ConsoleKit daemon ...
 [ ok ]
 * Setting framebuffer console images ...
 [ ok ]
 * Skipping GPU Hardware Acceleration and Input devices configuration
 * Setting hostname to Sting-Ray.optiplex-networks.com ...
 [ ok ]
 * Loading iptables state and starting firewall ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
 [ ok ]
 * Loading key mappings [us] ...
 [ ok ]
 * Bringing up interface lo
 *   127.0.0.1/8 ...
 [ ok ]
 *   Adding routes
 *     127.0.0.0/8 via 127.0.0.1 ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Activating additional swap space ...
 [ ok ]
 * Initializing random number generator ...
 [ ok ]
 * Setting up lxdm-binary ...
 [ ok ]

rc boot logging stopped at Sat Feb  9 00:27:10 2013


rc default logging started at Sat Feb  9 00:27:11 2013

 * Starting syslog-ng ...
 [ ok ]
 * Starting ufw ...
 [ ok ]
 * Starting NetworkManager ...
 [ ok ]
Connecting                   1sConnecting...............
 * Marking NetworkManager as inactive. It will automatically be marked
 * as started after a network connection has been established.
 * WARNING: NetworkManager has started, but is inactive
 * Restoring Mixer Levels ...
 [ ok ]
 * Starting avahi-daemon ...
 [ ok ]
 * Running cpufreq-set --governor ondemand ...
 [ ok ]
 * Starting cupsd ...
 [ ok ]
 * Starting mdadm monitor ...
 [ ok ]
 * Starting rpcbind ...
 [ ok ]
 * Starting NFS statd ...
 [ ok ]
 * WARNING: nfsmount is scheduled to start when NetworkManager has started
 * Starting ntpd ...
 [ ok ]
 * Starting snmpd ...
 [ ok ]
 * WARNING: sshd is scheduled to start when NetworkManager has started
 * Starting vixie-cron ...
 [ ok ]
 * Starting local
 [ ok ]

rc default logging stopped at Sat Feb  9 00:27:18 2013


Could you try to run
CODE: SELECT ALL
# /etc/init.d/nfsmount start --nodeps


Code: Select all
Sting-Ray ~ # /etc/init.d/nfsmount stop
 * Unmounting NFS filesystems ...                                         [ ok ]
Sting-Ray ~ # /etc/init.d/nfsmount start --nodeps
 * Starting NFS sm-notify ...                                             [ ok ]
 * Mounting NFS filesystems ...                                           [ ok ]
Sting-Ray ~ # df -h
Filesystem               Size  Used Avail Use% Mounted on
rootfs                    25G  9.1G   14G  40% /
udev                      10M  4.0K   10M   1% /dev
/dev/sda2                 25G  9.1G   14G  40% /
tmpfs                    2.0G  768K  2.0G   1% /run
cgroup_root               10M     0   10M   0% /sys/fs/cgroup
tmpfs                    2.0G  4.0K  2.0G   1% /dev/shm
/dev/sda3                9.7G  4.3G  4.9G  47% /home
192.168.1.120:/mnt/zfs   3.6T  3.6T   16G 100% /zr
192.168.1.120:/mnt/zfs2  3.6T  3.2T   51G  99% /zr_1


my nfsmouunt (for my own distfiles server) is :
CODE: SELECT ALL
192.168.0.8:/mirror/distfiles /usr/portage/distfiles nfs defaults,vers=3,nolock,auto,rw,retry=0.10 0 0


Hmm.... whenever I mount - cross platform - I use the same fstab line which so far uptil now has worked perfectly:

Code: Select all
192.168.1.120:/mnt/zfs   /zr         nfs   defaults   0 0
192.168.1.120:/mnt/zfs2 /zr_1         nfs   defaults   0 0
kayasaman
Young Hen
 
Posts: 29
Joined: Wed Feb 06, 2013 5:14


Re: Kernel Fault?

Postby kayasaman » Sat Feb 09, 2013 15:30

your prob is " my NFS mounts keep auto unmounting ??"


Yes :) After leaving my systems for a few hours the mounts are gone?? - as stated I haven't experienced this with any other *NIX style OS so I don't know if it's Sabayon specific or if it's a kernel error causing the "unmount" sequence prematurely. Maybe if DHCP lease gets renewed? I'm not sure if it's a timeout or keepalive issue as all other systems are fine :?

I misundertood ... do you need "auto unmounting" ? When ? (if you halt/rebbot the system , "nfs" mount points are unmounted)


No no this is not the issue, this can easily be achieved with a shell script if that was desired, or reboot, or shutdown.
kayasaman
Young Hen
 
Posts: 29
Joined: Wed Feb 06, 2013 5:14

Re: Kernel Fault?

Postby sabayonino » Sat Feb 09, 2013 16:52

kayasaman wrote:
After leaving my systems for a few hours the mounts are gone??


Yes,They're gone if you turn off your system.

but "leaving my system" , do you mean "suspend" or halt your system ?

all mounting points are kept on until you turn off the system or do not specify some umount command
User avatar
sabayonino
Sagely Hen
 
Posts: 2513
Joined: Sun Sep 21, 2008 1:12
Location: Italy

Re: Kernel Fault?

Postby kayasaman » Sat Feb 09, 2013 17:25

Yes,They're gone if you turn off your system.

but "leaving my system" , do you mean "suspend" or halt your system ?


By "leaving the system" I mean that the system is powered on and not hibernating or sleeping just the screen is turned off via Power Control Panel screen saver after x minutes.

all mounting points are kept on until you turn off the system or do not specify some umount command


This is what I'm trying to explain; the exptected behaviour is as you say but with mine as per above, if I just walk away from my system while it's in run level 5 (functioning) for a few hours then come back and run:

Code: Select all
df -h


The mount points are gone.... somehow they seem to either get auto-unmounted or some else is happening which I don't quite understand. This would happen with Autofs if it was installed and setup but I haven't done so.

My network fabric is perfectly fine, all Cisco hardware running underneath with minimal load. So why do mount points dissappear after a number of hours?

I'm not sure if it even would be possible to run a tcpdump or other packet scanner as I have no idea how long it takes before the error kicks in.

Imagine it this way: I minimize my browser, walk away from the machine, go to bed, wake up the following day and the mounts have vanished. I need to then re-mount using "mount" command all over again??
kayasaman
Young Hen
 
Posts: 29
Joined: Wed Feb 06, 2013 5:14

Next

Return to Sabayon Linux General Discussion

Who is online

Users browsing this forum: No registered users and 2 guests

cron