Sponsored Content
Top Forums UNIX for Advanced & Expert Users What is a file handle? for NFS troubleshooting stale issue. Post 302811475 by rveri on Thursday 23rd of May 2013 03:03:49 PM
Old 05-23-2013
What is a file handle? for NFS troubleshooting stale issue.

Experts,
Can any one please explain about a "File Handle" , what it is.
Can we see it, like an inode number.

- Also what is the significance of it in
Code:
"Stale NFS file handle"

error.

Thanks,
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NFS file handle

How can I kill mount connection(NFS , made by automount) if remote filesystem is down? I tried: fuser -ku /auto /auto: umount /auto nfs umount: ERROR: /auto is busy If I try cd /auto - I get - /auto: Stale remote file handle. I know that reboot will help but I cannot reboot this... (2 Replies)
Discussion started by: kazimir
2 Replies

2. UNIX for Advanced & Expert Users

Stale NFS file handle

Hi, I get an error saying "Stale NFS file handle" how can I solve this? Is it possible to do this with a umount/ mount command? (5 Replies)
Discussion started by: rein
5 Replies

3. Solaris

NFS file/dir disappear issue

We have bunch of Sun Sparc workstations(solaris 7 & 8) connecting to a linux file server with NFS exports. Recently we upgraded our file server from fedora core1 to redhat enterprise linux 4. And since then we are experiencing a nightmare of file/dir missing. It happens randomly, couple of times... (1 Reply)
Discussion started by: motor98
1 Replies

4. Solaris

Error Message: find: cannot open /: Stale NFS file handle

I am using the "find" command below and it respond with the error message " find: cannot open /: Stale NFS file handle" what does it mean? what can I do about it? Need advice, thanks. below are the command that I enter, the respond and the error message: root@ScripServer:/# find / -name... (1 Reply)
Discussion started by: ezsurf
1 Replies

5. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies

6. UNIX and Linux Applications

Stale NFS file handle

There are a filesystem /GWD/appbase/projects/GRIDDB Under this filesystem there is a directory called backup. But When I am trying to access the backup directory ,it is showing me the following error: # cd /GWD/appbase/projects/GRIDDB # cd backup -bash: cd: backup: Stale NFS file handle ... (3 Replies)
Discussion started by: alphasahoo
3 Replies

7. Linux

NFS file handle question

Hello All, I have a small question regarding the NFS file handles. Suppose I have a NFS client who has requested for a particular file from the NFS server.Now lets assume that I am using a NFS v2 server. So I get the filehandle for that file and I can use it. Suppose later I upgrade the server to... (0 Replies)
Discussion started by: prathamesh
0 Replies

8. UNIX for Advanced & Expert Users

How to decode nfs file handle in HP-UX?

Hi Experts, Any idea how to decode file handle in HP-UX? I am getting the following error continously in my HP-UX 11.31 box :mad: Apr 26 07:15:00 host62 su: + tty?? root-bb Apr 26 07:15:00 host62 su: + tty?? root-abcadm Apr 26 07:15:01 host62 vmunix: NFS write error on host peq9vs:... (1 Reply)
Discussion started by: vipinable
1 Replies

9. Windows & DOS: Issues & Discussions

VxWorks - W2003 issue loading file from NFS share

We recently replaced an existing Windows Server 2000 with a Windows Server 2003. The server‘s primary function is file/print in our development environment. One of the directories is shared using NFS. All compiled software is kept in this share (we use C & C++). The generated “.out” and “.ndb”... (0 Replies)
Discussion started by: BigBuff52
0 Replies

10. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
IO::Async::Handle(3pm)					User Contributed Perl Documentation				    IO::Async::Handle(3pm)

NAME
"IO::Async::Handle" - event callbacks for a non-blocking file descriptor SYNOPSIS
This class is likely not to be used directly, because subclasses of it exist to handle more specific cases. Here is an example of how it would be used to watch a listening socket for new connections. In real code, it is likely that the "Loop->listen" method would be used instead. use IO::Socket::INET; use IO::Async::Handle; use IO::Async::Loop; my $loop = IO::Async::Loop->new; my $socket = IO::Socket::INET->new( LocalPort => 1234, Listen => 1 ); my $handle = IO::Async::Handle->new( handle => $socket, on_read_ready => sub { my $new_client = $socket->accept; ... }, ); $loop->add( $handle ); For most other uses with sockets, pipes or other filehandles that carry a byte stream, the IO::Async::Stream class is likely to be more suitable. For non-stream sockets, see IO::Async::Socket. DESCRIPTION
This subclass of IO::Async::Notifier allows non-blocking IO on filehandles. It provides event handlers for when the filehandle is read- or write-ready. EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters: on_read_ready Invoked when the read handle becomes ready for reading. on_write_ready Invoked when the write handle becomes ready for writing. on_closed Optional. Invoked when the handle becomes closed. This handler is invoked before the filehandles are closed and the Handle removed from its containing Loop. The "loop" will still return the containing Loop object. PARAMETERS
The following named parameters may be passed to "new" or "configure": read_handle => IO write_handle => IO The reading and writing IO handles. Each must implement the "fileno" method. Primarily used for passing "STDIN" / "STDOUT"; see the SYNOPSIS section of "IO::Async::Stream" for an example. handle => IO The IO handle for both reading and writing; instead of passing each separately as above. Must implement "fileno" method in way that "IO::Handle" does. on_read_ready => CODE on_write_ready => CODE on_closed => CODE CODE references for event handlers. want_readready => BOOL want_writeready => BOOL If present, enable or disable read- or write-ready notification as per the "want_readready" and "want_writeready" methods. It is required that a matching "on_read_ready" or "on_write_ready" are available for any handle that is provided; either passed as a callback CODE reference or as an overridden the method. I.e. if only a "read_handle" is given, then "on_write_ready" can be absent. If "handle" is used as a shortcut, then both read and write-ready callbacks or methods are required. If no IO handles are provided at construction time, the object is still created but will not yet be fully-functional as a Handle. IO handles can be assigned later using the "set_handle" or "set_handles" methods, or by "configure". This may be useful when constructing an object to represent a network connection, before the connect(2) has actually been performed yet. METHODS
$handle->set_handles( %params ) Sets new reading or writing filehandles. Equivalent to calling the "configure" method with the same parameters. $handle->set_handle( $fh ) Shortcut for $handle->configure( handle => $fh ) $handle->close This method calls "close" on the underlying IO handles. This method will then remove the handle from its containing loop. $handle->close_read $handle->close_write Closes the underlying read or write handle, and deconfigures it from the object. Neither of these methods will invoke the "on_closed" event, nor remove the object from the Loop if there is still one open handle in the object. Only when both handles are closed, will "on_closed" be fired, and the object removed. $handle = $handle->read_handle $handle = $handle->write_handle These accessors return the underlying IO handles. $fileno = $handle->read_fileno $fileno = $handle->write_fileno These accessors return the file descriptor numbers of the underlying IO handles. $value = $handle->want_readready $oldvalue = $handle->want_readready( $newvalue ) $value = $handle->want_writeready $oldvalue = $handle->want_writeready( $newvalue ) These are the accessor for the "want_readready" and "want_writeready" properties, which define whether the object is interested in knowing about read- or write-readiness on the underlying file handle. SEE ALSO
o IO::Handle - Supply object methods for I/O handles AUTHOR
Paul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::Handle(3pm)
All times are GMT -4. The time now is 08:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy