Bug 13588
Summary: | shrink_dcache_for_umount_subtree+0x238/0x240 | ||
---|---|---|---|
Product: | File System | Reporter: | Francois Cartegnie (bugzilla77) |
Component: | NFS | Assignee: | bfields |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | akpm, alan, neilb, trondmy |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | NFS umount dcache shrink bug | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Francois Cartegnie
2009-06-20 15:03:09 UTC
Apparently a server bug. Reassigning to Bruce... cc neilb. Looks like a VFAT bug or a VFS bug. The link to NFS is purely circumstancial. During shutdown, nfsd was stopped which generated the first line, then a VFAT filesystem on /dev/sdc9 was unmounted which generated the remaining messages. Was the VFAT filesystem exported over NFS? If so, there might be a connection. If not, there is very unlikely to be a connection. If it wasn't NFS-exported, is there anything else at all unusual that might have been happening on that filesystem? There was a VFAT filesystem on /dev/sdc9, but it's access wasn't working, so I'm not sure it was mounted. Share was done on /mnt/ accessed through autofs. on server side: /mnt/disk/vfat/ (mount point for sdc9) /mnt/disk/reiser/ (mount point for sdc8) What do you mean by "its access wasn't working" ?? Access from NFS clients, or locally on the server. In what way didn't it work? Now it looks like it could be an NFSd problem, and VFAT problem, a VFS problem, or an autofs problem. The bug report mentioned a filesystem object called "bomberx". Can you tell us anything about this? Is it a file or a directory? Is it in the top level of the filesystem or deeper? If it is a file, what is it used for? Is it an executable or what? It is likely that some client will have tried to access it? -It's wasn't working in the way that it's mounted by the user, the exports are updated (*,rw), and the same uid can't still access it from a remote nfs clients (only reads empty dir). -bomberx is a picture in a subdir There have been many exports/re-exports to try to solve the problem. So, you have a file "bomberx" that's visible when you mount the filesystem, but that can't be seen on a client? (Even if you restart the server and remount from the client?) If you create other files in that same directory, are they also invisible to the client? |