From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Denis Barbier <bouzim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Unable to parse a sentence in sync_file_range.2
Date: Mon, 14 Jun 2010 03:47:37 -0400 [thread overview]
Message-ID: <20100614074737.GA27379@infradead.org> (raw)
In-Reply-To: <AANLkTilxmxNTK9Q7B0dH9v1XH7CAUCrdcw-qFgi4yzLG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> >> ?When writing into preallocated space, many filesystems also
> >> ?require calls into the block allocator, which this system
> >> ?call does not sync out to disk.
> >>
> >> Can someone please rephrase it? ?In particular, what does 'which' refer to?
> >> Thanks.
How about:
Usually filesystems also need to update metadata when writing into
preallocated space. This system call does not guarantee the persistance
of conversions from preallocated to regularly allocated space.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-14 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 23:32 Unable to parse a sentence in sync_file_range.2 Denis Barbier
[not found] ` <cfd18e0f1002210534x54997e93g3e9323e678e22cb9@mail.gmail.com>
[not found] ` <cfd18e0f1002210534x54997e93g3e9323e678e22cb9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-14 5:48 ` Michael Kerrisk
[not found] ` <AANLkTilxmxNTK9Q7B0dH9v1XH7CAUCrdcw-qFgi4yzLG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-14 7:47 ` Christoph Hellwig [this message]
[not found] ` <20100614074737.GA27379-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2010-06-15 4:59 ` Michael Kerrisk
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=20100614074737.GA27379@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=bouzim-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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).