From: Marc MERLIN <marc@merlins.org>
To: "Wang Shilong" <wangsl.fnst@cn.fujitsu.com>,
"Holger Hoffstätte" <holger.hoffstaette@googlemail.com>,
linux-btrfs@vger.kernel.org,
"dsterba@suse.cz Sterba" <dsterba@suse.cz>
Subject: Re: Transaction commit: none (default)
Date: Wed, 18 Jun 2014 07:42:30 -0700 [thread overview]
Message-ID: <20140618144230.GC19071@merlins.org> (raw)
In-Reply-To: <20140618141932.GV23096@twin.jikos.cz>
On Wed, Jun 18, 2014 at 04:19:32PM +0200, David Sterba wrote:
> On Mon, Jun 16, 2014 at 03:09:53PM +0800, Wang Shilong wrote:
> > >>>>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.
>
> I agree the way it's now (2 lines of output per 1 subvolume) is not
> good, but I'd like to keep the information about the commit mode, even
> for the default one. So would something like this work?
>
> current:
> Delete subvolume '/mnt/subvol'
>
> new:
> Delete subvolume (no commit): '/mnt/subvol'
>
> or
> Delete subvolume (commit): '/mnt/subvol'
I like this. The old line telling me it did what I just asked it to was kind
of redundant (rm doesn't tell me "I just deleted the file you just asked me
to" unless I use -v, and neither does rmdir).
So making the single line of output more useful would alleviate that a bit.
Although in general and in the future a command should indeed not be verbose
and reply "I just did what yo asked me to" :)
(just for the record,
Note that my crontabs already have stuff like this. I really wish I didn't
need them, and hope I don't have to extend the egrep line:
btrfs-snaps weekly 2 varlocalspace | egrep -v '(Create a snapshot of|Delete subvolume)'
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-06-18 14:42 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
2014-06-16 1:47 ` Marc MERLIN
2014-06-16 7:06 ` Holger Hoffstätte
2014-06-16 7:09 ` Wang Shilong
2014-06-18 14:19 ` David Sterba
2014-06-18 14:42 ` Marc MERLIN [this message]
2014-06-17 18:15 ` 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=20140618144230.GC19071@merlins.org \
--to=marc@merlins.org \
--cc=dsterba@suse.cz \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.com \
/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.