lkml.org 
[lkml]   [1998]   [Jul]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: HELP 2.1.108/SMP: Oops + Trace, inode 08:11/62243 still has locks!
Jordan Mendelson wrote:

> >
> > Could you look up what inode was involved here? Knowing which fs
> > was involved may give information on
> > the usage pattern. These messages usually indicate a bug in the
> > fs -- inodes aren't supposed to be
> > released with any locks or dentries still attached.
>
> Exactly how would one go about doing that? I don't know of any program which
> shows me what one particular inode is.

OK, start with which fs was using the device in question. Then the inode number
can be found using ls -i or dumpe2fs if it's an ext2 volume.

Regards,
Bill




-
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.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.030 / U:0.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site