Hide Forgot
Description of Problem: After I reboot the server for a file system mounted via NFS, I get an "I/O error" when trying to access certain directories on the file system. Jan 22 02:01:07 indonesia kernel: nfs_refresh_inode: inode number mismatch Jan 22 02:01:07 indonesia kernel: expected (0x155/0x80), got (0x160/0x80) is written to the system log when this happens. The problem typically occurs for only one or two of the directories on a file system where I can access everything else without any problems. I've even seen cases where 'ls <mount point>' fails, but I can read _all_ sub directories of <mount point>' 'umount' of the file system will fail with "Device or resource busy" even when no processes appear to have any of its files open (i.e. 'fuser -m <mount point>' doesn't report anything. This means that the problem cannot be resolved by "service netfs restart" - a full reboot of the client is necessary. Version-Release number of selected component (if applicable): 0.3.1-13.7.2.1 How Reproducible: A bit hard to say, really, but I have never restarted a server without getting this problem on some directory of some client. Steps to Reproduce: 1. Boot NFS server 2. mount <server>:<filesystem> <mount point> on a client (I usually do this /etc/fstab + netfs service, of course...) 3. Do some work on the client, but don't touch the server. 4. Reboot server 5. Access files under <mount point> Actual Results: "I/O error" on file access. "Device or resource busy" on umount or netfs restart Expected Results: NFS client survives server reboot as long as the filesystem layout is unchanged. If problems somehow occur after all, they may at least be resolved by "mount -o remount", "service netfs restart" or similar.
I get this on Red Hat 7.3 as well. Note that <mount point> access typically fails, while <mount point>/<sub directory> is typically OK. For example, % ls /u ls: /u: Input/output error % ls /u/ent bilde/ china/ diverse/ hafjell2000/ Julbord2001/ lyd/ tekst/ video/
Staled out. Sorry.