From: Mike Fedyk <mfedyk@matchmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: James D Strandboge <jstrand1@rochester.rr.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext3 and undeletion
Date: Mon, 4 Mar 2002 07:33:12 -0800 [thread overview]
Message-ID: <20020304153312.GI353@matchmail.com> (raw)
In-Reply-To: <20020304021714.GB353@matchmail.com> <E16hu8q-00080A-00@the-village.bc.nu>
In-Reply-To: <E16hu8q-00080A-00@the-village.bc.nu>
On Mon, Mar 04, 2002 at 03:12:44PM +0000, Alan Cox wrote:
> > another inode after the trunc op would break unix semantics. In order to
> > work, you'd have to use a new inode (in .undelete, of course), copy, then do
> > the actual trunc call.
> > This would make truncation expensive, whereas before it was pretty fast.
> > Modifying unlink will probably suffice.
>
> You would need to hook the truncate/unlink paths in the file system. If
> you are doing it within the fs it becomes cheap (at least for ext2) - as
> you can simply reassign the data blocks to a new inode, stuff the new inode
> into the magic "stuff we deleted" directory and continue.
It may make it easier to put this part in the kernel, but is there some way
to make it filesystem generic?
Undelete on truncate isn't a high priority, but if we do have it, it would
be nice if all of the filesystems that follow unix semantics (and maybe the
others too) could use generic VFS ops for this feature.
next prev parent reply other threads:[~2002-03-04 15:33 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 17:48 ext3 and undeletion Rose, Billy
2002-02-26 17:53 ` Martin Dalecki
2002-02-26 18:03 ` Mike Fedyk
2002-02-26 17:56 ` Rik van Riel
2002-02-26 19:41 ` Andreas Dilger
2002-02-26 18:00 ` H. Peter Anvin
2002-02-26 18:15 ` Andreas Dilger
2002-02-26 18:23 ` Jakob Østergaard
2002-02-26 18:19 ` David Lang
2002-02-26 18:29 ` Andreas Ferber
2002-02-27 21:00 ` James D Strandboge
2002-02-27 21:40 ` Alan Cox
2002-02-27 22:16 ` James D Strandboge
2002-02-27 22:33 ` Alan Cox
2002-02-27 23:03 ` James D Strandboge
2002-02-28 0:29 ` James D Strandboge
2002-03-04 2:17 ` Mike Fedyk
2002-03-04 15:12 ` Alan Cox
2002-03-04 15:33 ` Mike Fedyk [this message]
2002-03-04 19:17 ` James D Strandboge
2002-03-04 20:08 ` Jesse Pollard
2002-03-02 17:36 ` Pablo Alcaraz
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 23:04 Rose, Billy
2002-03-06 20:03 ` Mark Mielke
2002-03-07 21:30 ` Patrick Lynch
2002-02-28 10:37 Randal, Phil
2002-02-26 18:39 Dana Lacoste
2002-02-26 18:47 ` Daniel Gryniewicz
2002-02-26 18:51 ` David Lang
[not found] <fa.n4lfl6v.h4chor@ifi.uio.no>
2002-02-25 17:06 ` Dan Maas
2002-02-25 17:20 ` Mike Fedyk
2002-02-25 23:33 ` Tom Rauschenbach
2002-02-26 0:27 ` Bernd Eckenfels
2002-02-26 5:53 ` H. Peter Anvin
2002-02-26 16:05 ` Mike Fedyk
2002-02-26 16:31 ` H. Peter Anvin
2002-02-26 16:40 ` Mike Fedyk
2002-02-26 16:55 ` H. Peter Anvin
2002-02-26 17:12 ` Mike Fedyk
2002-02-26 16:36 ` Martin Dalecki
2002-02-26 16:43 ` Mike Fedyk
2002-02-26 16:54 ` Martin Dalecki
2002-02-26 17:05 ` Mike Fedyk
2002-02-26 17:07 ` Martin Dalecki
2002-02-26 17:16 ` Mike Fedyk
2002-02-26 17:22 ` Rik van Riel
2002-02-26 17:38 ` Mike Fedyk
2002-02-26 18:14 ` Andreas Ferber
2002-02-26 18:55 ` Andreas Dilger
2002-02-26 22:04 ` Mike Fedyk
2002-02-26 18:34 ` Richard B. Johnson
2002-02-26 18:34 ` H. Peter Anvin
2002-02-26 18:47 ` Richard B. Johnson
2002-02-26 18:52 ` Andreas Dilger
2002-02-28 15:05 ` Andreas Ferber
2002-02-28 22:37 ` Andreas Dilger
2002-02-28 22:55 ` James D Strandboge
2002-03-01 4:44 ` Mike Fedyk
2002-03-04 16:26 ` Pavel Machek
2002-03-05 21:29 ` Andreas Ferber
2002-03-06 11:30 ` Pavel Machek
2002-03-05 22:07 ` Richard B. Johnson
2002-02-26 17:22 ` Mike Fedyk
2002-03-01 0:19 ` Rick Lindsley
2002-03-01 1:02 ` Andreas Dilger
2002-02-26 17:54 ` Andreas Dilger
2002-02-26 18:24 ` Alan Cox
2002-03-04 15:40 ` Pavel Machek
2002-02-25 18:08 ` Richard B. Johnson
2002-02-25 18:40 ` Mike Fedyk
2002-02-25 19:49 ` Andreas Dilger
2002-02-25 16:46 Rose, Billy
2002-02-25 3:27 Steven Walter
2002-02-25 5:08 ` Andreas Dilger
2002-02-25 10:16 ` Fabrice Bellet
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=20020304153312.GI353@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jstrand1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
/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