| To: | "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: correct use of vmtruncate()? |
| From: | Zach Brown <zach.brown@xxxxxxxxxx> |
| Date: | Wed, 30 Apr 2008 08:55:45 -0700 |
| Cc: | David Chinner <dgc@xxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-mm <linux-mm@xxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20080430072457.GB7791@skywalker> |
| References: | <20080429100601.GO108924158@xxxxxxx> <481756A3.20601@xxxxxxxxxx> <20080430072457.GB7791@skywalker> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.12 (Macintosh/20080213) |
>> This paragraph in particular reminds me of an outstanding bug with >> O_DIRECT and ext*. It isn't truncating partial allocations when a dio >> fails with ENOSPC. This was noticed by a user who saw that fsck found >> bocks outside i_size in the file that saw ENOSPC if they tried to >> unmount and check the volume after the failed write. > > This patch should be the fix I guess > http://lkml.org/lkml/2006/12/18/103 That's the thread related to the bug, yes, but that isn't the right fix as David's later messages in the thread indicate. - z |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Remove l_flushsema, Matthew Wilcox |
|---|---|
| Next by Date: | RE: Problems with xfs_grow on large LVM + XFS filesystem 20TB size check 2 failed, Lance Reed |
| Previous by Thread: | Re: correct use of vmtruncate()?, Aneesh Kumar K.V |
| Next by Thread: | Re: correct use of vmtruncate()?, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |