From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Marc MERLIN <marc@merlins.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Transaction commit: none (default)
Date: Mon, 16 Jun 2014 09:35:23 +0800 [thread overview]
Message-ID: <539E49DB.80305@cn.fujitsu.com> (raw)
In-Reply-To: <20140614160554.GP6584@merlins.org>
On 06/15/2014 12:05 AM, Marc MERLIN wrote:
> Taking snapshots is now output this in addition of the snapshot
> operation.
>
> Transaction commit: none (default)
>
> 1) Is that expected/normal? It looks kind of spamming/useless to me?
> 2) If it's useful, what's the use I'm not getting?
Addressed a issue that subvolumes reappear after deletetion
if poweroff happen.
http://www.spinics.net/lists/linux-btrfs/msg29547.html
>
> Thanks,
> Marc
next prev parent reply other threads:[~2014-06-16 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 16:05 Transaction commit: none (default) Marc MERLIN
2014-06-16 1:35 ` Wang Shilong [this message]
2014-06-16 1:47 ` Marc MERLIN
2014-06-16 7:06 ` Holger Hoffstätte
2014-06-16 7:09 ` Wang Shilong
2014-06-17 18:15 ` Marc MERLIN
2014-06-18 14:19 ` David Sterba
2014-06-18 14:42 ` Marc MERLIN
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=539E49DB.80305@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).