[lkml]   [2000]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: corruption

On Sat, 2 Dec 2000, Petr Vandrovec wrote:

> Nothing new (was it meant to run remove_inode_queue() conditionaly inside
> buffer_mapped() branch? ed did it that way). First is list of buffers at
> time of destroy_inode, then process. If you want full oops trace, it is

what list of buffers? ->i_dirty_buffers one?

> available at, but last part is always
> iput. For now I'm back on test9, as I lost inetd.conf again :-( Someone
> should shoot sendmail Debian maintainer... Running update-inetd at startup
> is really bad idea, as fsck then usually removes both old and new inetd.conf,
> so I'm back on inetd.conf from 25 Aug 1999 :-(((
> Fields printed from buffer_head are b_next, b_blocknr, b_size, b_list,
> b_count, b_state and b_inode. (oops now I see that I left
> remove_inode_queue(bh) in printing loop (I copied it from
> invalidate_inode_buffers()), but it should not hurt, I believe. Dirty buffers
> should find its way to disk anyway, or not?)

When you delete the inode? Why would they? Petr, could you send me the
diff between the variant you've run and pristine 12-pre3? I'ld really
like to see what exactly was doing the printks...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

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