From: Andreas Dilger <adilger@sun.com>
Subject: Re: Help to read journal content
Date: Mon, 03 Aug 2009 13:54:44 -0600
Message-ID: <20090803195444.GH5432@webber.adilger.int>
References: <20aa8c370908030417he494294i890e804e6a552488@mail.gmail.com>
 <20aa8c370908030446n59325e14j41e4cc72d86a9bae@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Cc: linux-ext4@vger.kernel.org
To: ranjith kannikara <ranjithkannikara@gmail.com>
Content-disposition: inline
In-reply-to: <20aa8c370908030446n59325e14j41e4cc72d86a9bae@mail.gmail.com>
Sender: linux-ext4-owner@vger.kernel.org

On Aug 03, 2009  17:16 +0530, ranjith kannikara wrote:
> We are doing a project to make an applicatio that can recover the
> deleted data from an ext3 filesystem
> <http://sourceforge.net/projects/recoverext3/>. We ahve used the tools
> foremost and debugfs to debug the filesystem and read the journal.
> Is there any way to read the journal?
> Or How can we read the journal of a filesystem.
> The inode number of the journal is present in the ext3_super_block
> structure. But We are able to open the inode only with the help of
> these tools.
> Can someone guide us to where tio find the details of how a journal
> can be read.

Why create a new tool?  There is ext3grep which already does a lot of
this work, and it would be much better to spend your time to improve
that tool instead of spending time developing a new tool that doesn't
do anything better than any existing one.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.