From: Theodore Tso <tytso@mit.edu>
To: "Lars Täuber" <taeuber@bbaw.de>
Cc: Manish Katiyar <mkatiyar@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: undelete still opened file
Date: Fri, 17 Oct 2008 12:14:32 -0400 [thread overview]
Message-ID: <20081017161432.GB8755@mit.edu> (raw)
In-Reply-To: <20081017153957.28a4dd67.taeuber@bbaw.de>
On Fri, Oct 17, 2008 at 03:39:57PM +0200, Lars Täuber wrote:
>
> 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?
>
Unless you then manually modify the orphan list to remove the inode
from the orphan list, the next time you mount the filesystem as ext3
the blocks will be released and the filesystem will be corrupted.
Also, if you provoke a crash, the filesystem will be marked as "needs
recovery" and ext2 will refuse to mount the filesystem.
The much simpler way would be to kill -STOP the process that owns the
file, copy it via "cat /proc/$pid/fd/$fd > rescue-file". and then kill
-9 the process if you don't want it to make any further changes.
> > Not currently using ext3/ext4, no. There would have to be an entirely
> > new system call or other userspace interface for something like this.
>
> Is this planned?
No, this is not planned. "rm is forever".
> But a solution should be independent of the real filesystem. 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.
No, it's not necessarily in RAM. It's on disk, in the filesystem, but
marked in such a way that if the system crashes or when the file
descriptor is closed, the inode and its contents are marked as freed
for allocation.
- Ted
--
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 16:14 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
2008-10-17 16:14 ` Theodore Tso [this message]
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=20081017161432.GB8755@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mkatiyar@gmail.com \
--cc=taeuber@bbaw.de \
/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