public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: nscott@aconex.com
To: Bhagi rathi <jahnu77@gmail.com>
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: TAKE 972756 - Implement fallocate.
Date: Wed, 7 Nov 2007 20:35:21 +1100 (EST)	[thread overview]
Message-ID: <56697.192.168.3.1.1194428121.squirrel@mail.aconex.com> (raw)
In-Reply-To: <cc7060690711062142h3668e831o8fc49bdb5a1615bf@mail.gmail.com>

> Since size log change and data I/O are not binded, it is always possible
> that size can reach to the
> disk before I/O reaching to the disk.

Not clear what that has to do with whether partial blocks are zeroed or not?
Can you give a specific series of steps that would demonstrate a problem?
(preferably with a test case)

> Also, the other problem is because
> of
> speculative allocation.
> A write-back allocation can leady to allocation of delayed extents into
> real
> and gets pruned only
> close of the file.
> Before that, we get fallocate, it allocates the exents,
> but the extents residing
> because of delayed allocation write-back will not have zero'ed content.

Again, I think a test case demonstrating the problem would go a long way
to helping explain the issue.

The preallocation code and ioctl interface have been in XFS forever on
Linux - are you reporting problems you've actually observed here, or
are these rather "potential issues" that you foresee from code analysis?

cheers.

--
Nathan

  reply	other threads:[~2007-11-07  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02  2:43 TAKE 972756 - Implement fallocate David Chinner
2007-11-05 18:42 ` Bhagi rathi
2007-11-06  0:12   ` David Chinner
2007-11-06 17:27     ` Bhagi rathi
2007-11-06 19:04       ` Eric Sandeen
2007-11-06 20:41       ` David Chinner
2007-11-06 22:38         ` Nathan Scott
2007-11-07  5:42           ` Bhagi rathi
2007-11-07  9:35             ` nscott [this message]
2007-12-10 17:50 ` Eric Sandeen

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=56697.192.168.3.1.1194428121.squirrel@mail.aconex.com \
    --to=nscott@aconex.com \
    --cc=dgc@sgi.com \
    --cc=jahnu77@gmail.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