From: Andreas Dilger <adilger@sun.com>
To: ranjith kannikara <ranjithkannikara@gmail.com>
Cc: Bryan Donlan <bdonlan@gmail.com>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Help to edit inode content
Date: Tue, 12 May 2009 14:03:10 -0600 [thread overview]
Message-ID: <20090512200310.GP3209@webber.adilger.int> (raw)
In-Reply-To: <20aa8c370905120902o71ab9adflb8619e2a9ae343d0@mail.gmail.com>
On May 12, 2009 21:32 +0530, ranjith kannikara wrote:
> On Tue, May 12, 2009 at 9:26 PM, Bryan Donlan <bdonlan@gmail.com> wrote:
> > On Tue, May 12, 2009 at 11:47 AM, ranjith kannikara
> > <ranjithkannikara@gmail.com> wrote:
> >> I am a computer science engineering student. We have started a project
> >> to make an application to recover deleted files from an ext3
> >> filesystem. For that we have a doubt . Can we edit the inode content?
> >> ie the recovery will be robust if we could edit the inode contents and
> >> give the pointer address manually or through a code. The inode is
> >> being created in the kernel mode and is it possible to edit those
> >> contents if the code is allowed to have the kernel mode permissions..?
>
> But we would like to know whether it is possible to edit the inode
> because it will make the recovery easy and robust. ie he know the
> details of the inode of the file which had been deleted is it possible
> to edit the content of that inode with the pointers of the deleted
> file.?
Are you asking whether it is possible to modify the on-disk structure
of the ext3 inode? Generally that is NOT allowed because it will of
course break all existing filesystems if not done with extreme care.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-05-12 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:47 Help to edit inode content ranjith kannikara
2009-05-12 15:56 ` Bryan Donlan
2009-05-12 16:02 ` ranjith kannikara
2009-05-12 16:13 ` Manish Katiyar
2009-05-12 16:13 ` Manish Katiyar
2009-05-12 20:03 ` Andreas Dilger [this message]
2009-05-13 4:11 ` ranjith kannikara
2009-05-13 4:11 ` ranjith kannikara
2009-05-13 4:14 ` Manish Katiyar
2009-05-13 4:14 ` Manish Katiyar
2009-05-13 4:23 ` ranjith kannikara
2009-05-13 4:23 ` ranjith kannikara
2009-05-13 4:28 ` Manish Katiyar
2009-05-13 4:28 ` Manish Katiyar
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 15:43 ranjith kannikara
2009-05-12 15:39 ranjith kannikara
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=20090512200310.GP3209@webber.adilger.int \
--to=adilger@sun.com \
--cc=bdonlan@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ranjithkannikara@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.