Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC PATCH ext3/ext4] orphan list corruption due bad inode
    • From: Vasily Averin <[email protected]>
  • Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode
    • From: Andrew Morton <[email protected]>

• Prev by Date: Linux 2.6.22-rc4
• Next by Date: Re: 2.6.22-rc3-mm1: __attribute__((weak)) considered harmful
• Previous by thread: Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode
• Next by thread: Re: [RFC PATCH ext3/ext4] orphan list corruption due bad inode
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]