From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Subject: Re: ext3 and undeletion
Date: Thu, 28 Feb 2002 16:05:52 +0100 [thread overview]
Message-ID: <20020228160552.C23019@devcon.net> (raw)
In-Reply-To: <20020226171634.GL4393@matchmail.com> <Pine.LNX.3.95.1020226130051.4315A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1020226130051.4315A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Feb 26, 2002 at 01:34:27PM -0500
On Tue, Feb 26, 2002 at 01:34:27PM -0500, Richard B. Johnson wrote:
> All the deleted files, with the correct path(s), are now in the
> top directory file the file-system ../lost+found directory. They
> are still owned by the original user, still subject to the same
> quota.
And what about:
- Luser rm's "foo.c"
- Luser starts working on new version of "foo.c"
- Luser recognizes, that the old version was better
- Luser rm's new "foo.c"
- Luser tries to unrm the old "foo.c" -> *bang*
Trust me, there /will/ be a luser who tries to do it this way. If
teaching lusers were enough, you'd have no need for an unrm at all.
Everyone would be using version control for important data, and
everything would be fine.
> The disk space can't run out because you have simply moved
> files that didn't exceed the disk space before they were moved.
But a user will end up unable to /free/ any diskspace. User tries
something, generates a /huge/ error log filling up the quota/disk,
oops, has to call sysadmin before work can go on... Five minutes
later, the fix just tried didn't work, oops, has to call admin again,
and so on. Do you /really/ want this?
And how do you want to handle temp files? If you don't exclude them
from undeletion, they will fill up your diskspace soon. For the moment
I can't think of any mechanism that identifies temp files reliably
(without API changes).
> All one needs is a compile-time switch to enable the following:
And a system wide configurable switch, and a user configurable switch
and so on.
Undeletion has /many/ implications, did you think through all of them?
Just as a personal note: personally I would simply /refuse/ to work on
a system where I end up unable to delete even files I /own/, or at
least I would end up implementing my own way of deleting files which
circumvents undeletion (there will /always/ be a way to do it).
If your employer didn't expressively forbid you to keep private data
on your work account, you are allowed to do so, at least here in
germany, and you can sue your employer if he takes actions to look
into your private data without informing you /before/ doing it (taken
strictly, if you are allowed to keep private data on your work
account, you even have to be informed explicitly that the data may be
backuped and recovered later from backup tapes). So in the end,
undeletion is also a matter of privacy, and the ability to undelete
may even pose legal problems on a company.
Andreas
--
Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
---------------------------------------------------------
+49 521 1365800 - af@devcon.net - www.devcon.net
next prev parent reply other threads:[~2002-02-28 18:27 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.n4lfl6v.h4chor@ifi.uio.no>
2002-02-25 17:06 ` ext3 and undeletion 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 [this message]
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 22:05 ` ext3 and undeletion (libtrash) Omen Wild
2002-03-05 23:04 ext3 and undeletion Rose, Billy
2002-03-06 20:03 ` Mark Mielke
2002-03-07 21:30 ` Patrick Lynch
-- strict thread matches above, loose matches on Subject: below --
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
2002-02-26 17:48 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
2002-03-04 19:17 ` James D Strandboge
2002-03-04 20:08 ` Jesse Pollard
2002-03-02 17:36 ` Pablo Alcaraz
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=20020228160552.C23019@devcon.net \
--to=aferber@techfak.uni-bielefeld.de \
--cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox