From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from imap.thunk.org ([74.207.234.97]:58007 "EHLO imap.thunk.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752982AbbL2PPe (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 29 Dec 2015 10:15:34 -0500
Date: Tue, 29 Dec 2015 10:15:30 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: Vignesh Raman <rvignesh.raman@gmail.com>
Cc: Jan Kara <jack@suse.cz>, linux-fsdevel@vger.kernel.org
Subject: Re: Orphan inodes
Message-ID: <20151229151530.GC3248@thunk.org>
References: <CAL8k1Z40fLKJtv2E-KdsbATR26f1xQQTweNx7eMGkekfqiPDLw@mail.gmail.com>
 <20151222112143.GA18178@quack.suse.cz>
 <CAL8k1Z6Z-E3ZWXAQMPpWjy2L9VdNsZ+KhSDq6idxWp_r=DSgwA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL8k1Z6Z-E3ZWXAQMPpWjy2L9VdNsZ+KhSDq6idxWp_r=DSgwA@mail.gmail.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Tue, Dec 29, 2015 at 03:45:31PM +0530, Vignesh Raman wrote:
> Hi,
> 
> On Tue, Dec 22, 2015 at 4:51 PM, Jan Kara <jack@suse.cz> wrote:
> > It's hard to say why the fs got corrupted without more details. At least
> > full fsck output, ideally image of the corrupted filesystem obtained via
> > e2image.
> 
> The full e2fsck output is,
> 
> Pass 1: Checking inodes, blocks, and sizes
> Inodes that were part of a corrupted orphan linked list found.  Fix? yes
> 
> Inode 19387 was part of the orphaned inode list.  FIXED.
> Inode 19388 was part of the orphaned inode list.  FIXED.
> ....

(a) what kernel and distribution version are you using?

(b) can you reproduce this?  If so, how?

					- Ted