10-16-2017
If it's a reputable storage array/SAN then, no, it shouldn't happen baring power failures and the like. Dare I suggest that the network or storage team accidently did something that they shouldn't have?
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
4. Solaris
: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
5. UNIX and Linux Applications
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
6. Linux
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
7. Solaris
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies
8. UNIX for Advanced & Expert Users
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. UNIX for Advanced & Expert Users
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 "Stale NFS file handle" error.
Thanks, (3 Replies)
Discussion started by: rveri
3 Replies
10. AIX
Hi,
We are taking the mksysb backup to NIM server's NFS mount point (/backup). We have mounted /backup to all the clients /backup and full permission. When multiple mksysb backup starting simultaneously to the NIM server's shared NFS mount point then only one backup is running and all others... (3 Replies)
Discussion started by: sunnybee
3 Replies
FSYNC(2) BSD System Calls Manual FSYNC(2)
NAME
fsync -- synchronize a file's in-core state with that on disk
SYNOPSIS
#include <unistd.h>
int
fsync(int fildes);
DESCRIPTION
fsync() causes all modified data and attributes of fildes to be moved to a permanent storage device. This normally results in all in-core
modified copies of buffers for the associated file to be written to a disk.
Note that while fsync() will flush all data from the host to the drive (i.e. the "permanent storage device"), the drive itself may not physi-
cally write the data to the platters for quite some time and it may be written in an out-of-order sequence.
Specifically, if the drive loses power or the OS crashes, the application may find that only some or none of their data was written. The
disk drive may also re-order the data so that later writes may be present, while earlier writes are not.
This is not a theoretical edge case. This scenario is easily reproduced with real world workloads and drive power failures.
For applications that require tighter guarantees about the integrity of their data, Mac OS X provides the F_FULLFSYNC fcntl. The F_FULLFSYNC
fcntl asks the drive to flush all buffered data to permanent storage. Applications, such as databases, that require a strict ordering of
writes should use F_FULLFSYNC to ensure that their data is written in the order they expect. Please see fcntl(2) for more detail.
RETURN VALUES
The fsync() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
The fsync() system call will fail if:
[EBADF] fildes is not a valid descriptor.
[EINTR] Its execution is interrupted by a signal.
[EINVAL] fildes refers to a file type (e.g., a socket) that does not support this operation.
[EIO] An I/O error occurred while reading from or writing to the file system.
If a queued I/O operation fails, fsync() may fail with any of the errors defined for read(2) or write(2).
SEE ALSO
fcntl(2), read(2), sync(2), write(2), sync(8), update(8)
HISTORY
The fsync() function call appeared in 4.2BSD.
4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution