From: Chris Ball <cjb@laptop.org>
To: Josh Berry <des@condordes.net>
Cc: David Nicol <davidnicol@gmail.com>, kreijack <kreijack@libero.it>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Updating the wiki pages adding btrfs command
Date: Wed, 15 Sep 2010 17:52:19 -0400 [thread overview]
Message-ID: <m31v8un08c.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <AANLkTinGTyujDgTqwO6R729_djEWa-aUwiJ-W0vknXgE@mail.gmail.com> (Josh Berry's message of "Wed, 15 Sep 2010 14:46:46 -0700")
Hi,
> Or make --sync the default behavior. This is probably what most
> people are expecting anyway (similar to how standard filesystem
> commands like "rm" work). Add an --aysnc option for those that
> only care about knowing when the subvolume is taken out of the
> tree.
Yeah. We've also talked about making snapshot _creation_ perform an
FS sync first by default, since otherwise you get a snapshot with stale
files, or without files that existed (not yet on disk) at creation-time.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-09-15 21:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 19:40 reserving an IOCTL number; other details David Nicol
2010-09-12 22:08 ` David Nicol
2010-09-13 17:23 ` Goffredo Baroncelli
2010-09-13 20:15 ` David Nicol
2010-09-13 20:19 ` David Nicol
2010-09-13 20:22 ` Goffredo Baroncelli
2010-09-14 19:25 ` Updating the wiki pages adding btrfs command [Was Re: reserving an IOCTL number; other details] Goffredo Baroncelli
2010-09-15 14:10 ` David Nicol
2010-09-15 17:51 ` Goffredo Baroncelli
2010-09-15 18:35 ` David Nicol
2010-09-15 19:29 ` Goffredo Baroncelli
2010-09-15 18:41 ` Josh Berry
2010-09-15 20:54 ` David Nicol
2010-09-15 21:07 ` Updating the wiki pages adding btrfs command Chris Ball
2010-09-15 21:46 ` Josh Berry
2010-09-15 21:52 ` Chris Ball [this message]
2010-09-15 22:19 ` Josh Berry
2010-09-15 22:31 ` Sage Weil
2010-09-15 22:33 ` Sage Weil
2010-09-15 22:37 ` Chris Ball
2010-09-15 23:46 ` Josh Berry
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=m31v8un08c.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=davidnicol@gmail.com \
--cc=des@condordes.net \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.