From: Ian Kent <raven@themaw.net>
To: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Cc: Michal Sekletar <msekleta@redhat.com>
Subject: Re: mountbomber -- generate mount load
Date: Thu, 24 Sep 2020 09:26:37 +0800 [thread overview]
Message-ID: <598289c5e236bca151f673bc4846459ce71ac430.camel@themaw.net> (raw)
In-Reply-To: <20200923110554.agy6xevx3ll6uqh7@ws.net.home>
On Wed, 2020-09-23 at 13:05 +0200, Karel Zak wrote:
> Hi,
>
> I have created an experimental testing tool to generate a large
> number of
> mount/umount operations on a large number of mount points. The
> important feature
> is that it does not use standard mount(8) command and it does not
> parse
> anything in /proc.
This sounds great for testing large mount table and high notification
rates.
I'll certainly give a a spin as soon as I can get back to that systemd
change for high notification rate handling, I've had trouble with
various distractions lately unfortunately.
Thanks Karel.
>
> The goal is to have a standard tool to easily reproduce mount load
> without
> writing a custom shell scripts.
>
> The number of features is pretty basic and it supports only tmpfs
> now. Maybe
> later it will support other filesystems, regular block devices (or
> loopdevs)
> and more operations (like remount, execute scripts, etc.). We will
> see ...
>
> The tool creates and cleanup all stuff, you do not have create
> mountpoints, etc.
>
> It's maintained in separate branch in util-linux repository:
>
> git clone https://github.com/karelzak/util-linux.git --branch
> topic/mountbomber --single-branch
> cd util-linux
> ./autogen.sh
> ./configure
> make mountbomber
>
>
> Examples:
>
>
> # mountbomber --parallel 1 --verbose \
> --oper "mount:all,@A,umount:rand,mount:last,-
> >A(loops=2),umount:all"
>
> - one process, 100 mountpoints (default), random umount and mount
> two times
>
>
> # mountbomber --verbose --pool 10 \
> --oper
> "mount:all,@A,umount:next,mount:last,delay(500000),-
> >A(loops=200),umount:all"
>
> - 200 times umount and mount in order
>
>
> # mountbomber --pool 10000 \
> --oper
> "mount:all,@A,umount:rand,mount:last,delay(1000),-
> >A(seconds=60),umount:all"
>
>
> - 10 processes (default) repeating random umount/mount for 1
> minute on 10000 mountpoints
> - your udisks will be pretty busy :-)
>
> For more details:
>
> $ mountbomber --help
>
> there is no man page yet.
>
>
> Karel
>
prev parent reply other threads:[~2020-09-24 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:05 mountbomber -- generate mount load Karel Zak
2020-09-24 1:26 ` Ian Kent [this message]
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=598289c5e236bca151f673bc4846459ce71ac430.camel@themaw.net \
--to=raven@themaw.net \
--cc=kzak@redhat.com \
--cc=msekleta@redhat.com \
--cc=util-linux@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).