lkml.org 
[lkml]   [1999]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Question] does iput(iget(...)) work?
> My problem is that if the inode is not active iget() still
> returns a pointer. But an iput() then gives:
>
> Feb 28 15:28:51 harpo kernel: EXT2-fs warning (device 16:07): ext2_free_blocks: bit already cleared for block 82191
> Feb 28 15:28:51 harpo kernel: EXT2-fs warning (device 16:07): ext2_free_inode: bit already cleared for inode 20409
This is strange. When you do iget() on some inode an i_count is incremented
and inode can't be deleted from disk until i_count is non-zero. Only when
inode is unlinked and last user does iput() inode is really deleted. But this
messages from ext2 say the inode is already deleted => something is
wrong. Your filesystem is corrupted or your code is wrong somehow (I can't
just now imagine how, but it might be possible)... No matter what case this
is I would run fsck on the filesystem...

Honza.


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

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