Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Tags: Architectures Distributions Performance Style Tests
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

Architectures Distributions Performance Style Tests
Kash Pande
(#7947) relatime is always turned on temporarily for zfs root

this will modify the dracut mount routine (non-systemd) to
inspect the 'relatime' and 'atime' local/default/inherited
properties and enable one or the other depending on config.

if relatime=on this will override atime=off. can't use
both relatime and atime together.

Signed-off-by: Kash Pande <kash@tripleback.net>

Pull-request: #7948 part 1/1
Kash Pande
(#7947) relatime is always turned on temporarily for zfs root

this will modify the dracut mount routine (non-systemd) to
inspect the 'relatime' and 'atime' local/default/inherited
properties and enable one or the other depending on config.

if relatime=on this will override atime=off. can't use
both relatime and atime together.

Signed-off-by: Kash Pande <kash@tripleback.net>

Pull-request: #7948 part 2/2
Kash Pande
(Fixes #7287) modprobe zfs during dracut mount

Signed-off-by: Kash Pande <kash@tripleback.net>

Pull-request: #7948 part 1/2
Gregor Kopka
Zpool iostat: remove latency/queue scaling (#7694)

Bandwidth and iops are average per second while *_wait are averages
per request for latency or, for queue depths, an instantaneous
measurement at the end of an interval (according to man zpool).

When calculating the first two it makes sense to do
x/interval_duration (x being the increase in total bytes or number of
requests over the duration of the interval, interval_duration in
seconds) to 'scale' from amount/interval_duration to amount/second.

But applying the same math for the latter (*_wait latencies/queue) is
wrong as there is no interval_duration component in the values (these
are time/requests to get to average_time/request or already an
absulute number).

This bug leads to the only correct continuous *_wait figures for both
latencies and queue depths from 'zpool iostat -l/q' being with
duration=1 as then the wrong math cancels itself (x/1 is a nop).

This removes temporal scaling from latency and queue depth figures.
Closes: #7694

Signed-off-by: Gregor Kopka <gregor@kopka.net>

Pull-request: #7945 part 1/1
Gregor Kopka
Zpool iostat: remove latency/queue scaling (#7694)

Bandwidth and iops are average per second while *_wait are averages
per request for latency or, for queue depths, an instantaneous
measurement at the end of an interval (according to man zpool).

When calculating the first two it makes sense to do
x/interval_duration (x being the increase in total bytes or number of
requests over the duration of the interval, interval_duration in
seconds) to 'scale' from amount/interval_duration to amount/second.

But applying the same math for the latter (*_wait latencies/queue) is
wrong as there is no interval_duration component in the values (these
are time/requests to get to average_time/request or already an
absulute number).

This bug leads to the only correct continuous *_wait figures for
both latencies and queue depths from 'zpool iostat -l' are with
duration=1 as then the wrong math cancels itself (x/1 is a nop).

This removes temporal scaling from latency and queue depth figures.
Closes: #7694

Signed-off-by: Gregor Kopka <gregor@kopka.net>

Pull-request: #7945 part 1/1
  • Debian 8 arm (BUILD): cloning zfs -  stdio
  • Debian 8 ppc64 (BUILD): cloning zfs -  stdio
  • Debian 8 ppc (BUILD): cloning zfs -  stdio
  • Ubuntu 16.04 aarch64 (BUILD): cloning zfs -  stdio
  • Ubuntu 16.04 i386 (BUILD): cloning zfs -  stdio
Prakash Surya
WIP: Concurrent modifications to "/etc/dfs/sharetab" does not work

Signed-off-by: Prakash Surya <prakash.surya@delphix.com>

Requires-builders: all

Pull-request: #7944 part 1/1
Prakash Surya
WIP: Concurrent modifications to "/etc/dfs/sharetab" does not work

Pull-request: #7944 part 1/1
Brian Behlendorf
Fix statfs(2) for 32-bit user space

When handling a 32-bit statfs() system call the returned fields,
although 64-bit in the kernel, must be limited to 32-bits or an
EOVERFLOW error will be returned.

This is less of an issue for block counts since the default
reported block size in 128KiB. But since it is possible to
set a smaller block size, these values will be scaled as
needed to fit in a 32-bit unsigned long.

Unlike most other filesystems the total possible file counts
are more likely to overflow because they are calculated based
on the available free space in the pool. In order to prevent
this the reported value must be capped at 2^32-1. This is
only for statfs(2) reporting, there are no changes to the
internal ZFS limits.

Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>

Pull-request: #7937 part 1/1
Gregor Kopka
Fix flake 8 style warnings (issue #7925)

Ran zts-report.py and test-runner.py from ./tests/test-runner/bin/
through the 2to3 (https://docs.python.org/2/library/2to3.html).
Checked the result, fixed 'maxint' -> 'maxsize' that 2to3 missed.
Fixed the complaints Builtbot had.

Signed-off-by: Gregor Kopka <gregor@kopka.net>
Closes #7925

Pull-request: #7929 part 1/1
  • Amazon 2 x86_64 (BUILD): cloning zfs -  stdio
  • Debian 8 arm (BUILD): cloning zfs -  stdio
  • Debian 8 ppc64 (BUILD): cloning zfs -  stdio
  • Debian 8 ppc (BUILD): cloning zfs -  stdio
  • Ubuntu 16.04 aarch64 (BUILD): cloning zfs -  stdio
  • Ubuntu 16.04 i386 (BUILD): cloning zfs -  stdio
  • CentOS 6 x86_64 (BUILD): cloning zfs -  stdio
  • CentOS 7 x86_64 (BUILD): cloning zfs -  stdio
  • Debian 9 x86_64 (BUILD): cloning zfs -  stdio
  • Fedora 28 x86_64 (BUILD): cloning zfs -  stdio
  • Kernel.org Built-in x86_64 (BUILD): cloning zfs -  stdio
  • Ubuntu 16.04 x86_64 (BUILD): cloning zfs -  stdio
  • Ubuntu 18.04 x86_64 (BUILD): cloning zfs -  stdio
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Requires-builders: test

Pull-request: #7926 part 1/1
loli10K
Verify ZED detects physically removed L2ARC device

This commit adds a new test case to the ZFS Test Suite to verify ZED
can detect when a cache device is physically removed from a running
system.

Signed-off-by: loli10K <ezomori.nozomu@gmail.com>

Pull-request: #7926 part 1/1
Paul Dagnelie
test fix

Pull-request: #7846 part 8/8
Paul Dagnelie
Make the removal thread do more work

Pull-request: #7846 part 7/8
Paul Dagnelie
Fix various tests

Pull-request: #7846 part 6/8
Paul Dagnelie
Add params to man file, fix test #!

Pull-request: #7846 part 5/8
Paul Dagnelie
zfs_tests: get rid of Illumos dd

Illumos dd was ported to Linux because it has the stride option
that the GNU dd lacks. This option is required by some redacted
send tests. As a replacement, a new simple tool was created to
provide the needed functionality.

Pull-request: #7846 part 4/8
Paul Dagnelie
bug fixes

Pull-request: #7846 part 3/8
Paul Dagnelie
DLPX-58193 dsl_dataset_hold_obj can leak bookmarks

Reviewed at: http://reviews.delphix.com/r/39617/

Pull-request: #7846 part 2/8
Paul Dagnelie
Implement Redacted Send/Receive

Pull-request: #7846 part 1/8
Paul Dagnelie
Make the removal thread do more work

Pull-request: #7846 part 7/7
Paul Dagnelie
Fix various tests

Pull-request: #7846 part 6/7
Paul Dagnelie
Add params to man file, fix test #!

Pull-request: #7846 part 5/7
Paul Dagnelie
zfs_tests: get rid of Illumos dd

Illumos dd was ported to Linux because it has the stride option
that the GNU dd lacks. This option is required by some redacted
send tests. As a replacement, a new simple tool was created to
provide the needed functionality.

Pull-request: #7846 part 4/7
Paul Dagnelie
bug fixes

Pull-request: #7846 part 3/7
Paul Dagnelie
DLPX-58193 dsl_dataset_hold_obj can leak bookmarks

Reviewed at: http://reviews.delphix.com/r/39617/

Pull-request: #7846 part 2/7
Paul Dagnelie
Implement Redacted Send/Receive

Pull-request: #7846 part 1/7
Paul Dagnelie
zfs_tests: get rid of Illumos dd

Illumos dd was ported to Linux because it has the stride option
that the GNU dd lacks. This option is required by some redacted
send tests. As a replacement, a new simple tool was created to
provide the needed functionality.

Pull-request: #7846 part 7/7
Paul Dagnelie
Make the removal thread do more work

Pull-request: #7846 part 6/7
Paul Dagnelie
Fix various tests

Pull-request: #7846 part 5/7
Paul Dagnelie
Add params to man file, fix test #!

Pull-request: #7846 part 4/7