From: Alex Tomas <alex@clusterfs.com>
To: "Amit K. Arora" <aarora@linux.vnet.ibm.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
linux-ext4@vger.kernel.org, suparna@in.ibm.com, cmm@us.ibm.com,
suzuki@in.ibm.com, alex@clusterfs.com
Subject: Re: [RFC][Patch 2/2] Persistent preallocation in ext4
Date: Fri, 22 Dec 2006 18:31:03 +0300 [thread overview]
Message-ID: <m38xh0x808.fsf@bzzz.home.net> (raw)
In-Reply-To: <20061222151615.GA5851@amitarora.in.ibm.com> (Amit K. Arora's message of "Fri\, 22 Dec 2006 20\:46\:15 +0530")
>>>>> Amit K Arora (AKA) writes:
AKA> Above we can see that block numbers from 68 to 502 are each covered by
AKA> more than one extent (besides couple of holes, which also might be part
AKA> of the same problem).
AKA> Note: A "u" in extent[u] donates that this extent is
AKA> uninitialized, and thus was created as part of preallocation and noone
AKA> has written to it. An "i" signifies that the extent is initialized.
AKA> I am trying to solve this issue currently. Any suggestions are more than
AKA> welcome.. :)
I'd write a simple function that check given leaf for consistency
(in this case you need to check that every subsequent extent doesn't
overlap previous one) and add this check in few points (before and
after change). this worked very well, especially if all extents fit
single block.
thanks, Alex
prev parent reply other threads:[~2006-12-22 16:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 13:43 [RFC][Patch 1/1] Persistent preallocation in ext4 Amit K. Arora
2006-12-06 5:58 ` Amit K. Arora
2006-12-12 1:28 ` Mingming Cao
2006-12-12 6:23 ` Amit K. Arora
2006-12-13 0:20 ` Mingming Cao
2006-12-13 10:01 ` Amit K. Arora
2006-12-13 13:36 ` Dave Kleikamp
2006-12-13 15:38 ` Suparna Bhattacharya
2006-12-13 15:54 ` Mingming Cao
2006-12-15 12:35 ` [RFC][Patch 1/2] " Amit K. Arora
2006-12-19 11:05 ` Amit K. Arora
[not found] ` <20061219211206.GO5937@schatzie.adilger.int>
2006-12-20 6:28 ` Amit K. Arora
2006-12-27 23:30 ` Mingming Cao
2007-01-02 11:04 ` Amit K. Arora
2007-01-02 22:47 ` Mingming Cao
2007-01-09 9:05 ` Amit K. Arora
2006-12-15 12:39 ` [RFC][Patch 2/2] " Amit K. Arora
2006-12-15 23:02 ` Andreas Dilger
2006-12-16 4:30 ` Amit K. Arora
2006-12-19 11:42 ` Amit K. Arora
2006-12-19 11:54 ` Amit K. Arora
2006-12-19 21:14 ` Andreas Dilger
2006-12-19 21:23 ` Eric Sandeen
2006-12-20 8:19 ` Amit K. Arora
2006-12-22 15:16 ` Amit K. Arora
2006-12-22 15:31 ` Alex Tomas [this message]
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=m38xh0x808.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=aarora@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=suzuki@in.ibm.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).