Messages in this thread | | | Date | Sun, 16 Jan 2000 10:17:52 +0100 (CET) | From | Mikulas Patocka <> | Subject | Re: Inode leak in dcache pruning, apparently |
| |
On Sat, 15 Jan 2000, Chip Salzenberg wrote: > According to Mikulas Patocka: > > What happens when you try to unmount filesystem? > > [...] > > If it unmounts and the number of inodes drops after umount, it's because > > pruning dcache works badly. > > BINGO! Dcache pruning must be failing. Here's the status before unmounting > one filesystem: > /proc/sys/fs/inode-nr:1200 22 > And after: > /proc/sys/fs/inode-nr:1200 171 > So apparently 151 inodes were hanging around in the dcache.
This doesn't mean anything. The cache is there - just to cache things. So if you accessed 151 files on the disk, their inodes got to cache - it's normal behaviour.
> Thank you Mikulas! Now the toughie: How to track down the pruning weakness?
Try what happens when you umount while the leak is more visible (you said that it exceeds inode-max and grows to 80000). 1200 inodes is normal...
Mikulas
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |