Re: nasty inode leak in 2.1.125? details

Matthias Urlichs (smurf@noris.de)
30 Oct 1998 12:40:20 +0100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andi Kleen: "Re: TCP write fails to timeout"
Previous message: Matthias Urlichs: "Re: Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server"
Maybe in reply to: Chris Evans: "nasty inode leak in 2.1.125? details"
Next in thread: Tomasz Przygoda: "Re: nasty inode leak in 2.1.125? details"

Tomasz Przygoda <tprzyg@securities.com> writes:
> Oct 27 20:09:41 market kernel: change_root: old root has d_count=4
> Oct 27 20:09:41 market kernel: Trying to unmount old root ... <3>error
> -16
You lose the RAM of your RAM disk here.

> Is it the same story? Is it dentry leak? Should I worry?
>
No, it's not a leak, you simply have files open on the RAM disk.
Or you mounted /proc there and forgot to unmount it.

-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/

-- Lawyer, n. One skilled in circumvention of law. -- Ambrose Bierce

- 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/

Next message: Andi Kleen: "Re: TCP write fails to timeout"
Previous message: Matthias Urlichs: "Re: Strange problem with 2.0.34 NFS client and 2.1.125 (old user-space) NFS Server"
Maybe in reply to: Chris Evans: "nasty inode leak in 2.1.125? details"
Next in thread: Tomasz Przygoda: "Re: nasty inode leak in 2.1.125? details"