From: Dmitry Katsubo <dma_k@mail.ru>
To: linux-btrfs@vger.kernel.org
Subject: Some ideas for improvements
Date: Wed, 25 May 2016 16:45:41 +0200 [thread overview]
Message-ID: <45a47ee4db4cc92248f91f1d00e8ed03@www.centurion.link> (raw)
Dear btrfs community,
I hope btrfs developers are open for suggestions.
btrfs-scrub:
* Would be nice if 'btrfs scrub status' shows estimated finishing time
(ETA) and throughput (in Mb/s).
* Not possible to start scrub for all devices in the volume without
mounting it.
btrfs-restore:
* It does not restore special files like named pipes and devices.
* Hard-linked files are not correctly restored (they all turn into
independent replicas).
* If the file cannot be read / recovered, it is still created with zero
size (I would expect that the file is not created).
* I think that the options '-xmS' should be enabled by default
(shouldn't it be a goal to restore as much as possible?).
* Option that applies (y) to all questions (completely unattended
recovery) is missing.
--
With best regards,
Dmitry
next reply other threads:[~2016-05-25 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 14:45 Dmitry Katsubo [this message]
2016-05-25 19:03 ` Some ideas for improvements Duncan
2016-05-25 20:36 ` Nicholas D Steeves
2016-05-25 22:05 ` Duncan
2016-05-29 14:17 ` Dmitry Katsubo
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=45a47ee4db4cc92248f91f1d00e8ed03@www.centurion.link \
--to=dma_k@mail.ru \
--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).