From: Marc SCHAEFER <schaefer@alphanet.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: ext2 not NULLing deleted files?
Date: Fri, 17 Aug 2001 18:32:47 +0200 [thread overview]
Message-ID: <200108171632.SAA00941@vulcan.alphanet.ch> (raw)
In-Reply-To: <01081709381000.08800@haneman>
In article <01081709381000.08800@haneman> you wrote:
> I just recognized there's an "undelete" now for ext2 file systems [a KDE
not new.
> "The Other OS" in its professional version does of course clear the deleted
(assuming NT)
No it doesn't, and there even has been cases in the past where its
journaling filesystem was, under some conditions, extending files
with old data blocks without deleting them (a bit like the OLE `let's
put anything which is in RAM in this MS-Word file'), allowing other
users to snoop on each other's data / deleted data [no references
sorry, from memory].
Special care, as far as I understand it, must be taken when allocating
fs data blocks. The following sequence must be followed:
1. reserve them
2. clear them
3. mark them as allocated.
if 2 is too expensive, maybe it's sufficient to mark them as dirty
and zero them in memory. But what happens if the system crashes, with
the metadata to the disk (block allocated), but the data block not
yet filled/zeroed ?
Maybe some flags somewhere telling that those data blocks are allocated
but not yet committed ?
next prev parent reply other threads:[~2001-08-17 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 7:38 Enver Haase
2001-08-17 7:47 ` Robert Love
2001-08-17 17:40 ` Mark H. Wood
2001-08-17 7:56 ` Thomas Pornin
2001-08-17 8:02 ` Andreas Dilger
2001-08-17 17:55 ` Mark H. Wood
2001-08-17 20:09 ` Andreas Dilger
2001-08-21 14:19 ` Andreas Bombe
2001-08-17 16:32 ` Marc SCHAEFER [this message]
2001-08-17 17:25 ` Andreas Dilger
[not found] <01081709381000.08800@haneman.suse.lists.linux.kernel>
2001-08-17 8:03 ` Andi Kleen
2001-08-17 14:20 ` Kent Borg
2001-08-17 22:05 Jesse Pollard
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=200108171632.SAA00941@vulcan.alphanet.ch \
--to=schaefer@alphanet.ch \
--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
all inboxes | Powered by JetHome®