From: Eric Sandeen <sandeen@redhat.com>
To: forrest <forrestl@synology.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: fix extent tree corruption that incurred by hole punch
Date: Sat, 08 Dec 2012 11:31:01 -0600 [thread overview]
Message-ID: <50C37955.9090407@redhat.com> (raw)
In-Reply-To: <CAJSVwFMGZrOncF1s8xwZdDDVfYwtz_OBsKhHMGhMNZ98pQM06Q@mail.gmail.com>
On 12/4/12 6:29 AM, forrest wrote:
> This problem is easily to reproduce
>
> Create a file with size larger than 1GB.
>
> dd if=/dev/zero of=/test_file bs=1M count=1024
>
> Punch every even block in test_file, and then use debugfs to dump
> extents, followings is dumped result
>
> 2/ 2 339/340 231197 - 231197 3917597 - 3917597 1
> 2/ 2 340/340 231199 - 231199 3917599 - 3917599 1
> 0/ 2 2/ 2 231201 - 262143 3901486 30943
> 1/ 2 1/ 46 231201 - 231880 3901488 680
> 2/ 2 1/340 231201 - 231201 3917601 - 3917601 1
> 2/ 2 2/340 231203 - 231203 3917603 - 3917603 1
>
> Punch blocks #231779 ~#231201 ,
Can you explain what you mean by the above? Which blocks get punched?
-Eric
> to remove extent index, and then use
> debugfs to dump extents, followings is dumped result
next prev parent reply other threads:[~2012-12-08 17:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 12:11 [PATCH] ext4: fix extent tree corruption that incurred by hole punch Forrest Liu
2012-12-04 12:29 ` forrest
2012-12-05 6:13 ` Forrest Liu
2012-12-05 7:53 ` Ashish Sangwan
2012-12-05 8:09 ` Ashish Sangwan
2012-12-06 11:35 ` Forrest Liu
2012-12-06 13:16 ` Ashish Sangwan
2012-12-06 14:36 ` Forrest Liu
2012-12-07 5:11 ` Ashish Sangwan
2012-12-07 12:13 ` Forrest Liu
2012-12-10 6:22 ` Ashish Sangwan
2012-12-08 17:31 ` Eric Sandeen [this message]
2012-12-08 18:56 ` Forrest Liu
2012-12-06 15:45 ` Eric Sandeen
2012-12-06 15:48 ` Eric Sandeen
2012-12-07 5:53 ` Ashish Sangwan
2012-12-07 12:26 ` Forrest Liu
2012-12-07 22:17 ` Eric Sandeen
2012-12-08 19:01 ` Forrest Liu
2012-12-07 22:29 ` Theodore Ts'o
2012-12-08 19:29 ` Forrest Liu
-- strict thread matches above, loose matches on Subject: below --
2012-12-04 11:32 Forrest Liu
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=50C37955.9090407@redhat.com \
--to=sandeen@redhat.com \
--cc=forrestl@synology.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).