From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Cancel filesystem balance.
Date: 12 Nov 2010 12:25:00 +0100 [thread overview]
Message-ID: <B$jNZIPD1uB@helmut.hullen.de> (raw)
In-Reply-To: <20101112090755.GA16221@attic.humilis.net>
Hallo, Sander,
Du meintest am 12.11.10:
>> Given that there's been at least 1 report of it taking 12 hours
>> to balance a non-trivial amount of data I suspect putting this
>> operation into the background by default and having the cancel
>> option might be a better plan.
>>
>> Thoughts ?
> My humble opinion: I very much like the way mdadm works, with the
> progress bar in /proc/mdstat if an array is rebuilding for example.
Hmmm - it blocks the console for a long time.
I prefer running those long time jobs via "at"; all messages go into a
mail to root (or whoever has started the job).
"balance" seems to produce a logfile entry every 40 seconds, that may be
about 1500 lines for a 1 TByte job.
A progress bar produces similar messages, but they aren't as good
readable in an e-mail ...
I know those long and nearly unreadable mails p.e. from "squidGuard" ...
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2010-11-12 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 0:36 [PATCH v2 0/2] Balance management, kernel side Hugo Mills
2010-11-09 22:43 ` [PATCH v2 1/2] Balance progress monitoring Hugo Mills
2010-11-09 22:52 ` [PATCH v2 2/2] Cancel filesystem balance Hugo Mills
2010-11-12 1:33 ` Li Zefan
2010-11-12 4:28 ` Chris Samuel
2010-11-12 8:08 ` Helmut Hullen
2010-11-12 9:07 ` Sander
2010-11-12 9:26 ` Andreas Philipp
2010-11-12 11:25 ` Helmut Hullen [this message]
2010-11-12 12:04 ` Sander
2010-11-12 11:36 ` Hugo Mills
2010-11-12 17:59 ` Hugo Mills
2011-03-20 8:52 ` [PATCH v2 0/2] Balance management, kernel side Andreas Philipp
2011-03-20 11:37 ` Hugo Mills
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='B$jNZIPD1uB@helmut.hullen.de' \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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.