OpenVZ Forum: Devel » [RFC PATCH ext3/ext4] orphan list corruption due bad inode

Home » Mailing lists » Devel » [RFC PATCH ext3/ext4] orphan list corruption due bad inode

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

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

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]

		[RFC PATCH ext3/ext4] orphan list corruption due bad inode By: vaverin on Mon, 04 June 2007 05:19
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: Andrew Morton on Tue, 05 June 2007 02:03
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: Andreas Dilger on Tue, 05 June 2007 03:52
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: vaverin on Tue, 05 June 2007 06:11
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: Christoph Hellwig on Tue, 05 June 2007 06:13
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: vaverin on Tue, 05 June 2007 07:31
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: vaverin on Tue, 05 June 2007 06:49
		Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode By: Eric Sandeen on Tue, 05 June 2007 03:15

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:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Dec 06 19:55:30 GMT 2025

Total time taken to generate the page: 0.13051 seconds