Messages in this thread | | | From | "Jordan Mendelson" <> | Subject | RE: HELP 2.1.108/SMP: Oops + Trace, inode 08:11/62243 still has locks! | Date | Mon, 27 Jul 1998 16:42:14 -0400 |
| |
> 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.
Device is:
Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738 Type: Direct-Access ANSI SCSI revision: 02
It is my main Squid cache disk... (Squid was the process listed in the Oops). The file matching that name is /06/05/00060535:
62243 -rw-r--r-- 1 www www 14505 Jul 11 20:18 00060535
It is a GIF file...
Jordan
-- Jordan Mendelson : http://jordy.wserv.com Web Services, Inc. : http://www.wserv.com
- 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
| |