OpenVZ Forum


Home » Mailing lists » Devel » [RFC PATCH ext3/ext4] orphan list corruption due bad inode
Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode [message #13772 is a reply to message #13771] Tue, 05 June 2007 03:52 Go to previous messageGo to previous message
Andreas Dilger is currently offline  Andreas Dilger
Messages: 3
Registered: October 2006
Junior Member
On Jun 04, 2007 19:03 -0700, Andrew Morton wrote:
> What caused those inodes to be bad, anyway? Memory allocation failures?

This can happen if e.g. NFS has a stale file handle - it will look up
the inode by inum, but ext3_read_inode() will create a bad inode due to
i_nlink = 0.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: [Fwd: [PATCH -RSS 2/2] Fix limit check after reclaim]
Next Topic: Re: [Fwd: [PATCH -RSS 2/2] Fix limit check after reclaim]
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 10 12:32:00 GMT 2026

Total time taken to generate the page: 0.83906 seconds
Powered by FUDforum Powered by Virtuozzo Containers