From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <josef@redhat.com>
Cc: Mike Fedyk <mfedyk@mikefedyk.com>, Chris Ball <cjb@laptop.org>,
Nickolai Zeldovich <nickolai@csail.mit.edu>,
linux-btrfs@vger.kernel.org
Subject: Re: zero-length files in snapshots
Date: Fri, 12 Feb 2010 14:10:46 -0500 [thread overview]
Message-ID: <20100212191046.GA3508@infradead.org> (raw)
In-Reply-To: <20100212151940.GA4191@localhost.localdomain>
On Fri, Feb 12, 2010 at 10:19:40AM -0500, Josef Bacik wrote:
> 3) sync - this is not as obvious. sync doesn't mean anything than "start
> writing back dirty data to the fs", and returns before it's done. For btrfs
> what that means is we run through _every_ inode that has delalloc pages
> associated with them and start writeback on them. This will get most of your
> data into the current transaction, which is when the snapshot happens.
sync does return synchronously on Linux, even if that is not guaranted
by Posix.
prev parent reply other threads:[~2010-02-12 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 1:49 zero-length files in snapshots Nickolai Zeldovich
2010-02-12 3:11 ` Chris Ball
2010-02-12 4:50 ` Mike Fedyk
2010-02-12 15:19 ` Josef Bacik
2010-02-12 16:18 ` Mike Fedyk
2010-02-12 16:22 ` Josef Bacik
2010-02-12 16:27 ` Mike Fedyk
2010-02-12 16:32 ` Josef Bacik
2010-02-12 17:13 ` Mike Fedyk
2010-02-13 11:25 ` Sander
2010-02-13 19:26 ` Mike Fedyk
2010-02-19 22:22 ` Sage Weil
2010-02-25 18:57 ` Goffredo Baroncelli
2010-02-12 18:22 ` Ravi Pinjala
2010-02-12 18:45 ` Josef Bacik
2010-02-12 19:03 ` Chris Ball
2010-02-12 19:10 ` Christoph Hellwig [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=20100212191046.GA3508@infradead.org \
--to=hch@infradead.org \
--cc=cjb@laptop.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfedyk@mikefedyk.com \
--cc=nickolai@csail.mit.edu \
/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