From: ST <smntov@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: test btrfs scrubbing/get system's total capacity
Date: Mon, 20 Nov 2017 18:50:26 +0200 [thread overview]
Message-ID: <1511196626.1657.29.camel@gmail.com> (raw)
Hello,
1. is there a tool that I can use to test btrfs scrubbing? Namely I need
to "damage" a file, i.e. change it without changing its meta
information, so I can see how scrubbing performs... Is there something
like this?
2. I want to use Ansible to set btrfs quota on a /home subvolume as say
0.8*TotalCapacityOfRoot and then assign to it individual users'
subvolumes with certain (smaller) quatos.
2.1 Is it OK to rely on ansible_facts? Does it has correct information
about btrfs-based "/" total capacity?
2.2 If not, is there a raw command to get TotalCapacityOfRoot in -TB so
I can set it? Is there something like btrfs filesystem usage / -t
--device_size? to get only the total Device Size information?
Thank you!
ST
next reply other threads:[~2017-11-20 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 16:50 ST [this message]
2017-11-20 19:22 ` test btrfs scrubbing/get system's total capacity Chris Murphy
2017-11-20 22:57 ` Duncan
2017-11-21 1:22 ` Qu Wenruo
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=1511196626.1657.29.camel@gmail.com \
--to=smntov@gmail.com \
--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).