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
Date: Tue, 29 Dec 2015 10:15:30 -0500 [thread overview]
Message-ID: <20151229151530.GC3248@thunk.org> (raw)
In-Reply-To: <CAL8k1Z6Z-E3ZWXAQMPpWjy2L9VdNsZ+KhSDq6idxWp_r=DSgwA@mail.gmail.com>
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
next prev parent reply other threads:[~2015-12-29 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:37 Orphan inodes Vignesh Raman
2015-12-22 11:21 ` Jan Kara
2015-12-29 10:15 ` Vignesh Raman
2015-12-29 15:15 ` Theodore Ts'o [this message]
2015-12-31 9:25 ` Vignesh Raman
2015-12-31 16:14 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151229151530.GC3248@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rvignesh.raman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.