Re: [PATCH ext3/ext4] orphan list check on destroy_inode

Vasily Averin wrote:

Customers claims to ext3-related errors, investigation showed that ext3 orphan list has been corrupted and have the reference to non-ext3 inode. The following debug helps to understand the reasons of this issue.

Vasily, does your customer have this patch in place?

http://www.mail-archive.com/[email protected]/msg00889.html

If not, perhaps it could be leading to the same error, because the inode will not be properly removed from the orphan inode list when it is freed, and could then be recycled...

-Eric

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

---

• Follow-Ups:
  • Re: [PATCH ext3/ext4] orphan list check on destroy_inode
    • From: Vasily Averin <[email protected]>

• References:
  • [PATCH ext3/ext4] orphan list check on destroy_inode
    • From: Vasily Averin <[email protected]>

• Prev by Date: [PATCH] RAMFS NOMMU: missed POSIX UID/GID inode attribute checking
• Next by Date: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip
• Previous by thread: Re: [PATCH ext3/ext4] orphan list check on destroy_inode
• Next by thread: Re: [PATCH ext3/ext4] orphan list check on destroy_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]