From: Erik Mouw <erik@harddisk-recovery.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
UZAIR LAKHANI <uzairr_bs1b@yahoo.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: How To Recover Files From ext3 Partition??
Date: Mon, 8 May 2006 14:34:08 +0200 [thread overview]
Message-ID: <20060508123408.GE1875@harddisk-recovery.com> (raw)
In-Reply-To: <1147085495.5331.5.camel@sisko.sctweedie.blueyonder.co.uk>
On Mon, May 08, 2006 at 11:51:34AM +0100, Stephen C. Tweedie wrote:
> On Fri, 2006-05-05 at 10:41 -0600, Andreas Dilger wrote:
> > 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.
>
> Trouble is, there's no guarantee that that transaction would actually
> fit into the journal. Most of the time it will, but if it doesn't, then
> we deadlock or risk data corruption.
Is there some way to determine in advance if a transaction fits into
the journal? If so, we could unlink using Andreas's proposal if the
journal allows, and fall back to the old method if not.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2006-05-08 12:34 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
2006-05-08 10:51 ` Stephen C. Tweedie
2006-05-08 12:34 ` Erik Mouw [this message]
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=20060508123408.GE1875@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=adilger@clusterfs.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sct@redhat.com \
--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).