forum.lissyara.su

• ztest для тестирования zfs:

  Код: Выделить всё

  /*
   * The objective of this program is to provide a DMU/ZAP/SPA stress test
   * that runs entirely in userland, is easy to use, and easy to extend.
   *
   * The overall design of the ztest program is as follows:
   *
   * (1) For each major functional area (e.g. adding vdevs to a pool,
   *     creating and destroying datasets, reading and writing objects, etc)
   *     we have a simple routine to test that functionality.  These
   *     individual routines do not have to do anything "stressful".
   *
   * (2) We turn these simple functionality tests into a stress test by
   *     running them all in parallel, with as many threads as desired,
   *     and spread across as many datasets, objects, and vdevs as desired.
   *
   * (3) While all this is happening, we inject faults into the pool to
   *     verify that self-healing data really works.
   *
   * (4) Every time we open a dataset, we change its checksum and compression
   *     functions.  Thus even individual objects vary from block to block
   *     in which checksum they use and whether they're compressed.
   *
   * (5) To verify that we never lose on-disk consistency after a crash,
   *     we run the entire test in a child of the main process.
   *     At random times, the child self-immolates with a SIGKILL.
   *     This is the software equivalent of pulling the power cord.
   *     The parent then runs the test again, using the existing
   *     storage pool, as many times as desired.
   *
   * (6) To verify that we don't have future leaks or temporal incursions,
   *     many of the functional tests record the transaction group number
   *     as part of their data.  When reading old data, they verify that
   *     the transaction group number is less than the current, open txg.
   *     If you add a new test, please do this if applicable.
   *
   * When run with no arguments, ztest runs for about five minutes and
   * produces no output if successful.  To get a little bit of information,
   * specify -V.  To get more information, specify -VV, and so on.
   *
   * To turn this into an overnight stress test, use -T to specify run time.
   *
   * You can ask more more vdevs [-v], datasets [-d], or threads [-t]
   * to increase the pool capacity, fanout, and overall stress level.
   *
   * The -N(okill) option will suppress kills, so each child runs to completion.
   * This can be useful when you're trying to distinguish temporal incursions
   * from plain old race conditions.
   */

• nuttcp и другие
• /usr/src/tools/regression, /usr/src/tools/test и др. в /usr/src/tools/*
• gprof, gcov и прочие GNUтые утилиты
• hwpmc(4)
• ministat(1)

rufer писал(а):кстати поставили бы на форум мод, чтоб "спасибо можно было говорить" отсюда и репутация увеличивалась...

lissyara писал(а): товарисч Гость - он гостем хочет оставться.
Даже ник не пишет - но IP одинаковые
Вычисляется по ответам - но мода такого нет