From: "Manish Katiyar" <mkatiyar@gmail.com>
To: "Lars Täuber" <taeuber@bbaw.de>
Cc: "Theodore Tso" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: undelete still opened file
Date: Fri, 17 Oct 2008 19:32:50 +0530 [thread overview]
Message-ID: <ea11fea30810170702t295fe37dw43e33e0105cbe73@mail.gmail.com> (raw)
In-Reply-To: <20081017153957.28a4dd67.taeuber@bbaw.de>
On Fri, Oct 17, 2008 at 7:09 PM, Lars Täuber <taeuber@bbaw.de> wrote:
> Hi Theodore,
>
>
> Theodore Tso <tytso@mit.edu> schrieb:
>> On Fri, Oct 17, 2008 at 02:33:11PM +0200, Lars Täuber wrote:
>> > Is the space of the file on the underlying block device already
>> > marked as free? Or does this happen after all processes have closed
>> > all file descriptors pointing to the file?
>>
>> No, the space on the file is not yet marked as free. *However* for
>> ext3 and ext4, the inode has been placed on the orphaned inode list,
>> so that if the system crashes, part of the journal recovery process
>> will at that point free the blocks.
>
> not that it is a way I would go, but theoretically: I could provoke a crash and mount the ext3 filesystem as ext2 and restore the file?
Errr.... If I read the code correctly, once deleted the inode is added
to the orphan list and on recovery this orphan list is traversed and
iput will be called on each of the inodes. So even a crash will not
restore your inode on the contrary *it will make sure that the inode
is deleted*.
>
>> > I really want to undo the deletion. (get a link/name connected to
>> > the root inode of the file again) Is there a way to do this?
>>
>> Not currently using ext3/ext4, no.
Isn't it possible to some extent using ext3grep for ext3 ????
There would have to be an entirely
>> new system call or other userspace interface for something like this.
>
> Is this planned?
>
> But a solution should be independent of the real filesystem.
No as I said...depending on the nature of filesystem it may be write
in place or it might write to a new block every time like logfs. So
it is very much filesystem dependant.
Thanks -
Manish
>Because the file is still somewhere in the ram and represented in linux vfs, isn't it?
> It only needs to be copied/recreated on to a (different) filesystem somehow.
>
> Regards
> Lars
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-17 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 10:08 undelete still opened file Lars Täuber
2008-10-17 10:33 ` Manish Katiyar
2008-10-17 12:33 ` Lars Täuber
2008-10-17 13:24 ` Theodore Tso
2008-10-17 13:39 ` Lars Täuber
2008-10-17 14:02 ` Manish Katiyar [this message]
2008-10-17 16:14 ` Theodore Tso
2008-10-20 7:23 ` Lars Täuber
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=ea11fea30810170702t295fe37dw43e33e0105cbe73@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=taeuber@bbaw.de \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox