linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Berry <des@condordes.net>
To: Chris Ball <cjb@laptop.org>
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 15:19:14 -0700	[thread overview]
Message-ID: <AANLkTimvPVqMTr1Dbp_ATGHLduajHJA0KdkjF5ry7JuT@mail.gmail.com> (raw)
In-Reply-To: <m31v8un08c.fsf@pullcord.laptop.org>

On Wed, Sep 15, 2010 at 14:52, Chris Ball <cjb@laptop.org> wrote:
> Hi,
>
> =C2=A0 > Or make --sync the default behavior. =C2=A0This is probably =
what most
> =C2=A0 > people are expecting anyway (similar to how standard filesys=
tem
> =C2=A0 > commands like "rm" work). =C2=A0Add an --aysnc option for th=
ose that
> =C2=A0 > only care about knowing when the subvolume is taken out of t=
he
> =C2=A0 > tree.
>
> Yeah. =C2=A0We've also talked about making snapshot _creation_ perfor=
m an
> FS sync first by default, since otherwise you get a snapshot with sta=
le
> files, or without files that existed (not yet on disk) at creation-ti=
me.

Oh wow, I didn't know this.  Yes, sync-before-create would be nice.

*runs off to update his snapshot script*

-- Josh
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-09-15 22:19 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
2010-09-15 22:19                     ` Josh Berry [this message]
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=AANLkTimvPVqMTr1Dbp_ATGHLduajHJA0KdkjF5ry7JuT@mail.gmail.com \
    --to=des@condordes.net \
    --cc=cjb@laptop.org \
    --cc=davidnicol@gmail.com \
    --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 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).