[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTikvw7AEPdLtfc6+4KpJQHM8maACsh1+s9P6==kB@mail.gmail.com>
Date: Thu, 10 Mar 2011 13:40:13 +0800
From: Dave Young <hidave.darkstar@...il.com>
To: Allison Henderson <achender@...ux.vnet.ibm.com>
Cc: linux-ext4@...r.kernel.org
Subject: Re: [Ext4 punch hole 1/5] Ext4 Punch Hole Support: Convert Blocks to
Uninit Exts
On Tue, Mar 1, 2011 at 11:08 AM, Allison Henderson
<achender@...ux.vnet.ibm.com> wrote:
> Hi All!
>
> This is the patch series for ext4 punch hole that I have been working on.
> There is still a little more debugging that I would like to do with it,
> but I've had some requests to see the patch, so I'm sending it out a bit
> early. Any feed back is appreciated. Thx!
>
Hi, aliison
Do you have new version of the patchset which address the comments here?
If they are not ready to send to list, you can send to me, I would like to test.
I tested this patchset for kvm guest image cleanup.
Host ext4 + guest ext4
guest side use lukas's fstrim tool, host side use a modified version
of Christoph's qemu block discard patch
there's many error like following:
[62834.936374] EXT4-fs error (device sda7): ext4_ext_lookup_hole:2907:
inode #1310744: comm qemu-system-x86: bad header/extent: invalid magic
- magic 0, entries 0, max 256(0), depth 256(0)
[62834.936616] EXT4-fs error (device sda7): ext4_ext_lookup_hole:2907:
inode #1310744: comm qemu-system-x86: bad header/extent: invalid magic
- magic 0, entries 0, max 256(0), depth 256(0)
bad header/extent: invalid magic - magic 0, entries 0, max 256(0), depth 256(0)
Then host pc hangs there.
BTW, host xfs + guest ext4 works well for me.
--
Thanks
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists