Re: Transaction commit: none (default)

[Wang Shilong <wangsl.fnst@cn.fujitsu.com>]

On 06/16/2014 03:06 PM, Holger Hoffstätte wrote:
> On Sun, 15 Jun 2014 18:47:39 -0700, Marc MERLIN wrote:
>
>> On Mon, Jun 16, 2014 at 09:35:23AM +0800, Wang Shilong wrote:
>>> 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
>> I see, thank you for the pointer.
>> In the case of my script, it's console spam that I wish I could make go
>> away, but grep -v will do that for me :)
>>
>> If it annoys other people, maybe having a -q (quiet) that removes this
>> message would be useful?
> IMHO it should be the reverse: be quiet by default and require -v, just
> as more explicit behaviour also requires additional options.
> With default options I expect default behaviour. Telling me that the
> default behaviour happened is just noise.
Fair point, Another question is that current default output has been there.
Let's Cc David, and see what is his opinion.

>
> cheers
> Holger
>
> --
> 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
>