From: Andreas Dilger <adilger@clusterfs.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: UZAIR LAKHANI <uzairr_bs1b@yahoo.com>, linux-fsdevel@vger.kernel.org
Subject: Re: How To Recover Files From ext3 Partition??
Date: Fri, 5 May 2006 10:41:47 -0600 [thread overview]
Message-ID: <20060505164147.GK6075@schatzie.adilger.int> (raw)
In-Reply-To: <20060505111807.GD4900@harddisk-recovery.com>
On May 05, 2006 13:18 +0200, Erik Mouw wrote:
> Andreas, care to elaborate? AFAICS resetting ->i_mode to 0000, setting
> ->i_links_count to 0, and setting ->i_dtime should be enough to
> uniquely mark an inode as deleted. Doing so would make an occasional
> undelete much easier to recover for Joe Sixpack (and for us a lot less
> work to reconstruct files by scavenging the whole partition for clues).
Yes, while this would mark the _inode_ unused, it does nothing to
mark the blocks unused in the block bitmaps (of which there may be
many thousand/million in a single file). So ext3 needs to be able to
mark these bitmap blocks unused when the file is unlinked/truncated.
Otherwise each crash would leak blocks that can't be recovered except
by full e2fsck.
There is another mechanism ext3 could potentially use, wherein it
walks the whole inode in advance of the truncate and creates a
(potentially) very large transaction handle to do the bitmap updates
in a single shot (and also reducing the amount of IO needed for an
unlink by 96%), but nobody has ever cared enough about it to work on
implementing this.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-05-05 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 14:18 How To Recover Files From ext3 Partition?? UZAIR LAKHANI
2006-05-04 14:38 ` Erik Mouw
2006-05-05 5:16 ` UZAIR LAKHANI
2006-05-05 11:18 ` Erik Mouw
2006-05-05 16:41 ` Andreas Dilger [this message]
2006-05-08 10:51 ` Stephen C. Tweedie
2006-05-08 12:34 ` Erik Mouw
2006-05-08 12:42 ` Stephen C. Tweedie
2006-05-08 17:41 ` Andreas Dilger
2006-05-08 13:20 ` Theodore Tso
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=20060505164147.GK6075@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=uzairr_bs1b@yahoo.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;
as well as URLs for NNTP newsgroup(s).