fio  

Messages by Thread

• • Re: Clang static analyzer warnings Jens Axboe
• Update Account System Administrator
• server mode and verify_dump Sitsofe Wheeler
  • Re: server mode and verify_dump Jens Axboe
  • Re: server mode and verify_dump Jens Axboe
  • Re: server mode and verify_dump Sitsofe Wheeler
  • Re: server mode and verify_dump Jens Axboe
  • Re: server mode and verify_dump Sitsofe Wheeler
  • Re: server mode and verify_dump Jens Axboe
  • Re: server mode and verify_dump Sitsofe Wheeler
  • Re: server mode and verify_dump Jens Axboe
• valgrind error "invalid read of size 4" in get_jobs_eta Bruce Cran
  • Re: valgrind error "invalid read of size 4" in get_jobs_eta Jens Axboe
• Mail. valino
• Re Mr Tan Wong
• Job Garcias
• [PATCH 1/1] verify: move meta header to generic verify_header Roman Pen
  • Re: [PATCH 1/1] verify: move meta header to generic verify_header Jens Axboe
  • Re: [PATCH 1/1] verify: move meta header to generic verify_header Sitsofe Wheeler
  • Re: [PATCH 1/1] verify: move meta header to generic verify_header Roman Peniaev
  • Re: [PATCH 1/1] verify: move meta header to generic verify_header Roman Peniaev
  • Re: [PATCH 1/1] verify: move meta header to generic verify_header Jens Axboe
• PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine Andrey Kuzmin
  • Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine Jens Axboe
  • Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine Jens Axboe
  • Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine Andrey Kuzmin
  • Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine Jens Axboe
  • Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine Andrey Kuzmin
• Loan Offer!! jschug3
• ask a question about fio john gong
  • Re: ask a question about fio Alireza Haghdoost
  • Re: ask a question about fio Kulkarni, Vasu
  • Re: ask a question about fio john gong
  • Re: ask a question about fio danielabuggie .
  • Re: ask a question about fio john gong
  • Re: ask a question about fio danielabuggie .
  • Re: ask a question about fio john gong
  • Re: ask a question about fio danielabuggie .
  • Re: ask a question about fio Alireza Haghdoost
  • Re: ask a question about fio john gong
• Logging starvation on large amount of threads Gleb Stepanov
• Starvation on large amount of threads Gleb Stepanov
• CLAIM!!!... Bingo
• gcc 5.1.1 and warnings when building fio on Linux with -flto Bruce Cran
  • Re: gcc 5.1.1 and warnings when building fio on Linux with -flto Jens Axboe
• Question about data integrity check Alireza Haghdoost
  • Fwd: Question about data integrity check Grant Grundler
  • Re: Question about data integrity check Alireza Haghdoost
  • Re: Question about data integrity check Sitsofe Wheeler
  • Re: Question about data integrity check Alireza Haghdoost
• Percentage/ETA progress indicator faulty with examples/tiobench-example.fio Bruce Cran
  • Re: Percentage/ETA progress indicator faulty with examples/tiobench-example.fio Jens Axboe
  • Re: Percentage/ETA progress indicator faulty with examples/tiobench-example.fio Bruce Cran
• t/stest failures Bruce Cran
  • Re: t/stest failures Bruce Cran
  • Re: t/stest failures Jens Axboe
• FreeBSD build broken following _Static_assert commit Bruce Cran
  • Re: FreeBSD build broken following _Static_assert commit Jens Axboe
  • Re: FreeBSD build broken following _Static_assert commit Bruce Cran
  • Re: FreeBSD build broken following _Static_assert commit Jens Axboe
  • Re: FreeBSD build broken following _Static_assert commit Bruce Cran
  • Re: FreeBSD build broken following _Static_assert commit Jens Axboe
• competime_assert failure without -O3 optimization flag expected ? Alireza Haghdoost
  • Re: competime_assert failure without -O3 optimization flag expected ? Jens Axboe
  • Re: competime_assert failure without -O3 optimization flag expected ? Alireza Haghdoost
  • Re: competime_assert failure without -O3 optimization flag expected ? Jens Axboe
  • Re: competime_assert failure without -O3 optimization flag expected ? Jens Axboe
  • Re: competime_assert failure without -O3 optimization flag expected ? Alireza Haghdoost
  • Re: competime_assert failure without -O3 optimization flag expected ? Jens Axboe
  • Re: competime_assert failure without -O3 optimization flag expected ? Alireza Haghdoost
  • Re: competime_assert failure without -O3 optimization flag expected ? Jens Axboe
  • Re: competime_assert failure without -O3 optimization flag expected ? Alireza Haghdoost
  • Re: competime_assert failure without -O3 optimization flag expected ? Jens Axboe
• [PATCH] Fix testing and setting set_options bitmap Akinobu Mita
  • Re: [PATCH] Fix testing and setting set_options bitmap Jens Axboe
• Re: query on verify_dump option Alireza Haghdoost
• Verify concentrated on first few drives Gavin Martin
  • Re: Verify concentrated on first few drives Jens Axboe
  • Re: Verify concentrated on first few drives Jens Axboe
  • Re: Verify concentrated on first few drives Gavin Martin
• what is the difference? start 2 fio instances and setting numjobs=2 .. QB
  • RE: what is the difference? start 2 fio instances and setting numjobs=2 .. Carl Zwanzig
• FIO creating empty latency log files Reed Crowe
  • Re: FIO creating empty latency log files Jens Axboe
  • Re: FIO creating empty latency log files Buttetsu Batou
  • Re: FIO creating empty latency log files Jens Axboe
  • Re: FIO creating empty latency log files Jens Axboe
  • Re: FIO creating empty latency log files Jens Axboe
  • Re: FIO creating empty latency log files DoubleDensity
  • Re: FIO creating empty latency log files Jens Axboe
• Wired Latency Reporting in the FIO results Alireza Haghdoost
• [Suggestion] Aggregated Client/Server Stats Reporting Alireza Haghdoost
  • Re: [Suggestion] Aggregated Client/Server Stats Reporting Sitsofe Wheeler
  • Re: [Suggestion] Aggregated Client/Server Stats Reporting Alireza Haghdoost
  • Re: [Suggestion] Aggregated Client/Server Stats Reporting Ben England
• Parameter Issue with 'ratemin'... FIO-User-KKV
  • RE: Parameter Issue with 'ratemin'... Hinson, Roger
  • Re: Parameter Issue with 'ratemin'... FIO-User-KKV
  • Re: Parameter Issue with 'ratemin'... Jens Axboe
• Good Day! Miss Sarah Abedi
• fio offset cycling. Adrin Fernandes
  • Re: fio offset cycling. Sitsofe Wheeler
• Re: Testing write master and multiple read clients on NFS share danielabuggie .
  • Re: Testing write master and multiple read clients on NFS share Jens Axboe
  • Re: Testing write master and multiple read clients on NFS share Michael Weinrich
• Urgent problem while using Fio to test random write performance Nan WANG
  • Re: Urgent problem while using Fio to test random write performance David Nellans
  • Re: Urgent problem while using Fio to test random write performance Sitsofe Wheeler
  • Re: Urgent problem while using Fio to test random write performance Jens Axboe
• Re: --thinktime seems not work Bruce Cran
• FIO - dedup checksums or specified blocksize does not match. Srinivasa Chamarthy
  • Re: FIO - dedup checksums or specified blocksize does not match. Jens Axboe
  • Re: FIO - dedup checksums or specified blocksize does not match. Srinivasa Chamarthy
  • Re: FIO - dedup checksums or specified blocksize does not match. Srinivasa Chamarthy
  • Re: FIO - dedup checksums or specified blocksize does not match. Srinivasa Chamarthy
• fio queue depth and windows build. Iuliu Rus
  • Re: fio queue depth and windows build. Bruce Cran
  • Re: fio queue depth and windows build. Iuliu Rus
  • Re: fio queue depth and windows build. Iuliu Rus
  • Re: fio queue depth and windows build. Alireza Haghdoost
• achieving a workload to get specific unique duplicate blocks Srinivasa Chamarthy
  • Re: achieving a workload to get specific unique duplicate blocks Jens Axboe
  • RE: achieving a workload to get specific unique duplicate blocks Ruvinsky, Konstantin
• [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based Akash Verma
• Unable to replay blktrace with mixed workload Brandon Schwartz
  • Re: Unable to replay blktrace with mixed workload Jens Axboe
  • Re: Unable to replay blktrace with mixed workload Brandon Schwartz
• [no subject] Kleber Sacilotto de Souza
• fio writing only around 50% of LUN capacity for fill_device=1 Srinivasa Chamarthy
• [PATCH] Don't export state variable Dan Ehrenberg
  • Re: [PATCH] Don't export state variable Jens Axboe
• fio trim bug Neil Durbridge
• crash reports while running IO on raid0 btrfs Srinivasa Chamarthy
  • Re: crash reports while running IO on raid0 btrfs Srinivasa Chamarthy
  • Re: crash reports while running IO on raid0 btrfs Jens Axboe
  • Re: crash reports while running IO on raid0 btrfs Jens Axboe
  • Re: crash reports while running IO on raid0 btrfs Srinivasa Chamarthy
• [PATCH] Fix mtd valgrind warning Dan Ehrenberg
  • Re: [PATCH] Fix mtd valgrind warning Jens Axboe
• lex/yacc not configured properly. Srinivasa Chamarthy
  • Re: lex/yacc not configured properly. Srinivasa Chamarthy
• [PATCH v2 0/7] Framework for NAND lifetime testing Dan Ehrenberg
  • [PATCH v2 3/7] Collect a block-wise histogram of trim and write errors Dan Ehrenberg
  • [PATCH v2 1/7] Allow trim on any file type Dan Ehrenberg
  • [PATCH v2 4/7] mtd: Add CONFIG_MTD to ./configure script Dan Ehrenberg
  • [PATCH v2 2/7] Add new trimwrite rw= mode for trims preceding writes Dan Ehrenberg
  • [PATCH v2 6/7] mtd: ioengine Dan Ehrenberg
  • [PATCH v2 7/7] mtd: example job file Dan Ehrenberg
  • [PATCH v2 5/7] mtd: Import libmtd with modifications to make it compile Dan Ehrenberg
• [PATCH 0/7] Framework for NAND lifetime testing Dan Ehrenberg
  • [PATCH 1/7] Allow trim on any file type Dan Ehrenberg
  • [PATCH 3/7] Collect a block-wise histogram of trim and write errors Dan Ehrenberg
  • [PATCH 4/7] mtd: Add CONFIG_MTD to ./configure script Dan Ehrenberg
  • [PATCH 6/7] mtd: ioengine Dan Ehrenberg
  • [PATCH 7/7] mtd: example job file Dan Ehrenberg
  • [PATCH 5/7] mtd: Import libmtd with modifications to make it compile Dan Ehrenberg
  • [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Dan Ehrenberg
  • Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Jens Axboe
  • Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Daniel Ehrenberg
  • Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Jens Axboe
  • Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Daniel Ehrenberg
  • Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Jens Axboe
• Looping blktrace binary files Brandon Schwartz
• fio filename vs directory Z Es
• FIO writes many empty files after ENOSPC from device. Srinivasa Chamarthy
• FIO not generating multiple jobs for directories Srinivasa Chamarthy
  • Re: FIO not generating multiple jobs for directories Srinivasa Chamarthy
• Generating random data with FIO on directories returning null Srinivasa Chamarthy
  • Re: Generating random data with FIO on directories returning null Matthew Eaton
  • Re: Generating random data with FIO on directories returning null Srinivasa Chamarthy
• during fio scenario with verify=meta some jobs fails Samuel Shapiro
  • Re: during fio scenario with verify=meta some jobs fails Samuel Shapiro
  • Re: during fio scenario with verify=meta some jobs fails Sitsofe Wheeler
  • Re: during fio scenario with verify=meta some jobs fails Sitsofe Wheeler
  • Re: during fio scenario with verify=meta some jobs fails Sitsofe Wheeler
  • Re: during fio scenario with verify=meta some jobs fails Samuel Shapiro
  • Re: during fio scenario with verify=meta some jobs fails Sitsofe Wheeler
  • Re: during fio scenario with verify=meta some jobs fails Samuel Shapiro
• Question regarding fio build system Raphael Philipe
• A probable minor mistake in HOWTO page Mansour Shafaei Moghaddam
  • Re: A probable minor mistake in HOWTO page Jens Axboe
  • Re: A probable minor mistake in HOWTO page Mansour Shafaei Moghaddam
  • Re: A probable minor mistake in HOWTO page Jens Axboe
  • Re: A probable minor mistake in HOWTO page Mansour Shafaei Moghaddam
• Latencies around 10 seconds for I/Os in a trace!!! Mansour Shafaei Moghaddam
  • Re: Latencies around 10 seconds for I/Os in a trace!!! Alireza Haghdoost
  • Re: Latencies around 10 seconds for I/Os in a trace!!! Mansour Shafaei Moghaddam
  • Re: Latencies around 10 seconds for I/Os in a trace!!! Alireza Haghdoost
  • Re: Latencies around 10 seconds for I/Os in a trace!!! Mansour Shafaei Moghaddam
• Need support about value IOPS Which FIO measured Nguyen Viet Dung
  • RE: Need support about value IOPS Which FIO measured Elliott, Robert (Server Storage)
  • RE: Need support about value IOPS Which FIO measured Elliott, Robert (Server Storage)
  • RE: Need support about value IOPS Which FIO measured Elliott, Robert (Server Storage)
• FIO for Android Fabio Salvati (fabiosalvati)
• FIO still returning 0 and writing file after bogus arguments Andy Moe
  • Re: FIO still returning 0 and writing file after bogus arguments Jens Axboe
• [PATCH] In gettime.c, check for ARCH_CPU_CLOCK_WRAPS only ifdef ARCH_HAVE_CPU_CLOCK Akash Verma
  • Re: [PATCH] In gettime.c, check for ARCH_CPU_CLOCK_WRAPS only ifdef ARCH_HAVE_CPU_CLOCK Jens Axboe
• Buggy behavior with zone, random IOs since specific commit Akash Verma
  • Re: Buggy behavior with zone, random IOs since specific commit Jens Axboe

• Earlier messages
• Later messages