From: Vlad Apostolov <vapo@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: review: make xfs_dm_punch_hole() atomic when punching EOF
Date: Mon, 21 May 2007 12:00:24 +1000 [thread overview]
Message-ID: <4650FD38.4080408@sgi.com> (raw)
In-Reply-To: <20070419071856.GR48531920@melbourne.sgi.com>
It is looking good Dave.
Regards,
Vlad
David Chinner wrote:
> Currently punching a hole to EOF via xfs_dm_punch_hole()
> truncates the file and then extends it. This leaves a small
> window where applications can see an incorrect file size
> while the punch is in progress. This can cause problems
> with DMF leading to premature completion of recalls and
> hence data corruption.
>
> Use the UNRESVSP ioctl rather than FREESP+setattr to punch the
> hole at EOF. This can leave specualtive allocations past EOF,
> so truncate them off so we don't leave blocks that can't be
> migrated away around in the filesystem.
>
> Cheers,
>
> Dave.
>
prev parent reply other threads:[~2007-05-21 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 7:18 review: make xfs_dm_punch_hole() atomic when punching EOF David Chinner
2007-05-21 2:00 ` Vlad Apostolov [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=4650FD38.4080408@sgi.com \
--to=vapo@sgi.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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