From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is "btrfs balance start" truly asynchronous?
Date: Tue, 21 Jun 2016 08:55:18 +0000 (UTC) [thread overview]
Message-ID: <pan$7df97$9174e96e$7848d28b$295d4358@cox.net> (raw)
In-Reply-To: f68639e5a41343c04fa4d76f3fb14370@www.centurion.link
Dmitry Katsubo posted on Mon, 20 Jun 2016 18:33:54 +0200 as excerpted:
> Dear btfs community,
>
> I have added a drive to existing raid1 btrfs volume and decided to
> perform balancing so that data distributes "fairly" among drives. I have
> started "btrfs balance start", but it stalled for about 5-10 minutes
> intensively doing the work. After that time it has printed something
> like "had to relocate 50 chunks" and exited. According to drive I/O,
> "btrfs balance" did most (if not all) of the work, so after it has
> exited the job was done.
>
> Shouldn't "btrfs balance start" do the operation in the background?
>From the btrfs-balance (8) manpage (from btrfs-progs-4.5.3):
start [options] <path>
start the balance operation according to the specified filters,
no filters will rewrite the entire filesystem. The process runs
in the foreground.
So the balance start operation runs in the foreground, but as explained
elsewhere in the manpage, the balance is interruptible by unmount and
will automatically restart after a remount. It can also be paused and
resumed or canceled with the appropriate btrfs balance subcommands.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-06-21 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 16:33 Is "btrfs balance start" truly asynchronous? Dmitry Katsubo
2016-06-21 8:55 ` Duncan [this message]
2016-06-21 11:24 ` Austin S. Hemmelgarn
2016-06-21 11:33 ` Hugo Mills
2016-06-21 11:51 ` Austin S. Hemmelgarn
2016-06-21 13:17 ` Graham Cobb
2016-06-21 13:44 ` Lionel Bouton
2016-06-21 23:30 ` Dmitry Katsubo
2016-06-21 12:19 ` Zygo Blaxell
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='pan$7df97$9174e96e$7848d28b$295d4358@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).