Sponsored Content
Operating Systems Linux Red Hat Automounter floods ioctl and futex error messages Post 302610419 by jim mcnamara on Wednesday 21st of March 2012 08:32:39 AM
Old 03-21-2012
futex objects are used to coordinate access to something. When a futex is negative it's cooperating process(es) are in a wait state, in the case of a file system it is probably code waiting for io requests to be queued. Note the -1 in the output. This means the process checking the futex is sleeping, then waking up checking the futex and going back to sleep. Polling is the term you want. The select() system call does this for example, if you want to understand polling - read the select man page. This appears to be mostly harmless.


ioctl is the primary inquiry and control interface between processes and filesystem drivers. EAGAIN is a valid return code meaning the resource is offline, not available, busy, waiting, etc. but anyway is not able to answer. This may be very like kids in a car asking the same question every 2 minutes: 'are we there yet?'

Find out what process those pids are, then read up on what those processes do.

IMO something is possibly wasting some cpu cycles and the resources required to move a process sleep/wake (like realtime timer), and depending on your configuration this may be of little importance. You may need some kind of upgrade/patch or configuration change. It is not really "normal" AFAIK.

admin_xor implied the workround: do not automount.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

automounter

I have this question in my study guide could anyone please help me with the answer and (explicit) explanation. hostname: HOSTONE automounter file: /etc/auto.home entry: scps HOSTTWO:/export/home/scps commands executed on HOSTONE, mark all commands where the automounter will be invoked. ... (3 Replies)
Discussion started by: almendrita
3 Replies

2. Programming

ioctl()

UNIX, gnu cc compiler, SUN Ultra 60 Hello, this is my first post, so please bear with me. I'm currently developing a test environment for a network subsystem that, when live, accesses databases and other network elements. However, my test environment will be run offline, so I need to fake... (4 Replies)
Discussion started by: j_t_kim
4 Replies

3. UNIX for Dummies Questions & Answers

automounter

Hi ALL, Does anyone know how automounting can be disabled in solaris? (I need to mount the home directory on to a sun machine from another machine. So I run something like mount another_machine:/home /home (on my sun) however i get an error saying device busy) I was told automouting... (1 Reply)
Discussion started by: rkap
1 Replies

4. AIX

NIS and automounter...

Have an AIX 5.2 box. I had automounter already setup to control /home using /etc/auto_home as an indirect automount map. Then we added NIS. We have it working, but for some reason, the NIS table auto.home seems to override /etc/auto_home entries. Of course, there are some duplicates... (2 Replies)
Discussion started by: Garry_Garrett
2 Replies

5. Solaris

Inappropriate ioctl for device, format error

When I try to format a slice in Solaris 10 I get the follow error : -bash-3.00# mkfs /dev/dsk/c1d0s5 18877824 Can not determine partition size: Inappropriate ioctl for device Some format command output:.... AVAILABLE DISK SELECTIONS: 0. c1d0 <DEFAULT cyl 38735 alt 2 hd 64 sec 63>... (2 Replies)
Discussion started by: spoonman
2 Replies

6. UNIX for Advanced & Expert Users

ioctl : strace

Hi All, int ioctl(int d, int request, ...); Can somebody tell me how does ioctl decides the input parameter: "request". Sometimes, its SNDCTL_TMR_TIMEBASE or TCGETS or FIONREAD...etc. What is the pattern?? I am asking this coz my strace returns this: ... (1 Reply)
Discussion started by: angad.makkar
1 Replies

7. Solaris

fssnap ioctl error

For some reason when I try to take a snapshot of the root slice on a particular machine I get an ioctl 22 error. I can't seem to find much on the problem by searching the internet other than some realtime processes such as ntp that use mlock can cause this to happen. I tried running it with truss... (2 Replies)
Discussion started by: ilikecows
2 Replies

8. IP Networking

Naming services + Automounter

Hi gurus, I am trying to understand the enviroment which we are using. The fact that I am asking is that this is production enviroment and I cannot change anything to experiment. Following servers are somehow related to each other, please help me figure out if my conclusions are correct. -... (0 Replies)
Discussion started by: wakatana
0 Replies

9. Red Hat

How to mount NFS using automounter(autofs)?

I have an nfs at 192.168.1.10:/home/vm1/Desktop/nfs and will like to mount locally to /home/vm1/Desktop/nfs-mount using automounter...need help doing do What i did $cat /etc/auto.master /home/vm1/Desktop /etc/auto.nfs $cat /etc/auto.nfs nfs-bind -fstype=nfs ... (3 Replies)
Discussion started by: nokia3310
3 Replies
GET_ROBUST_LIST(2)						Linux System Calls						GET_ROBUST_LIST(2)

NAME
get_robust_list, set_robust_list - get/set list of robust futexes SYNOPSIS
#include <linux/futex.h> #include <sys/types.h> #include <syscall.h> long get_robust_list(int pid, struct robust_list_head **head_ptr, size_t *len_ptr); long set_robust_list(struct robust_list_head *head, size_t len); Note: There are no glibc wrappers for these system calls; see NOTES. DESCRIPTION
These system calls deal with per-thread robust futex lists. These lists are managed in user space: the kernel knows only about the loca- tion of the head of the list. A thread can inform the kernel of the location of its robust futex list using set_robust_list(). The address of a thread's robust futex list can be obtained using get_robust_list(). The purpose of the robust futex list is to ensure that if a thread accidentally fails to unlock a futex before terminating or calling execve(2), another thread that is waiting on that futex is notified that the former owner of the futex has died. This notification con- sists of two pieces: the FUTEX_OWNER_DIED bit is set in the futex word, and the kernel performs a futex(2) FUTEX_WAKE operation on one of the threads waiting on the futex. The get_robust_list() system call returns the head of the robust futex list of the thread whose thread ID is specified in pid. If pid is 0, the head of the list for the calling thread is returned. The list head is stored in the location pointed to by head_ptr. The size of the object pointed to by **head_ptr is stored in len_ptr. Permission to employ get_robust_list() is governed by a ptrace access mode PTRACE_MODE_READ_REALCREDS check; see ptrace(2). The set_robust_list() system call requests the kernel to record the head of the list of robust futexes owned by the calling thread. The head argument is the list head to record. The len argument should be sizeof(*head). RETURN VALUE
The set_robust_list() and get_robust_list() system calls return zero when the operation is successful, an error code otherwise. ERRORS
The set_robust_list() system call can fail with the following error: EINVAL len does not equal sizeof(struct robust_list_head). The get_robust_list() system call can fail with the following errors: EPERM The calling process does not have permission to see the robust futex list of the thread with the thread ID pid, and does not have the CAP_SYS_PTRACE capability. ESRCH No thread with the thread ID pid could be found. EFAULT The head of the robust futex list can't be stored at the location head. VERSIONS
These system calls were added in Linux 2.6.17. NOTES
These system calls are not needed by normal applications. No support for them is provided in glibc. In the unlikely event that you want to call them directly, use syscall(2). A thread can have only one robust futex list; therefore applications that wish to use this functionality should use the robust mutexes pro- vided by glibc. In the initial implementation, a thread waiting on a futex was notified that the owner had died only if the owner terminated. Starting with Linux 2.6.28, notification was extended to include the case where the owner performs an execve(2). The thread IDs mentioned in the main text are kernel thread IDs of the kind returned by clone(2) and gettid(2). SEE ALSO
futex(2), pthread_mutexattr_setrobust(3) Documentation/robust-futexes.txt and Documentation/robust-futex-ABI.txt in the Linux kernel source tree COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2017-09-15 GET_ROBUST_LIST(2)
All times are GMT -4. The time now is 06:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy