Whamcloud - gitweb
Ben Evans [Tue, 24 Oct 2017 15:34:06 +0000 (11:34 -0400)]
LU-7988 hsm: wake up cdt when requests are empty
The coordinator only runs once per second, we need a mechanism
to send more work when everything is done (cdt_request_count
goes to zero)
Without this, there is a hard limit of max_requests per sec
requests that can be processed, causing performance issues
with small files.
Lustre-change: https://review.whamcloud.com/29742
Lustre-commit:
7251fea8dc3c4d29e30c5a3f763c4c33d35f90a7
Signed-off-by: Ben Evans <bevans@cray.com>
Change-Id: I563666a1a3e53f0ec5908de593de71ff4d925467
Reviewed-by: Frank Zago <fzago@cray.com>
Reviewed-by: Sergey Cheremencev <cherementsev@gmail.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30538
Tested-by: Jenkins
Reviewed-by: Sergey Cheremencev <c17829@cray.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Thomas Stibor [Fri, 17 Nov 2017 14:31:39 +0000 (15:31 +0100)]
LU-10256 hsm: enable setting archive_id in hsm_set
Setting HSM flags in lfs_hsm_change_flags(...,LFS_HSM_SET)
does not allow to specify the archive_id, that is,
in llapi_hsm_state_set(path, mask, 0, 0 /* archive_id */)
archive_id = 0 is always set, which means no identifier change.
For having full flexibility (e.g. for debugging), introduce
the additional option --archive-id in hsm_set. If the option
is not provided, the default behavior (archive_id = 0) is used
and no archive identifier change is done. In addition a
test case is provided to check the functionality and shell
function get_hsm_archive_id() is modified in favor of more
robust grep for contents after pattern approach.
Lustre-change: https://review.whamcloud.com/30150
Lustre-commit:
d1855f8e22a929066a69470c7e3d082c70478575
Test-Parameters: trivial testlist=sanity-hsm
Signed-off-by: Thomas Stibor <t.stibor@gsi.de>
Change-Id: I2145a18ecf32479527bb045140e5e881e58dd115
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Stephan Thiell <sthiell@stanford.edu>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30500
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Steve Guminski [Fri, 14 Apr 2017 19:45:59 +0000 (15:45 -0400)]
LU-6210 utils: Use C99 struct initializers in lfs_hsm_state()
This patch makes no functional changes. Struct initializers that
use C89 or GCC-only syntax are updated to C99 syntax.
C89 positional initializers require values to be placed in the
correct order. This will cause errors if the fields of the struct
definition are reordered or fields are added or removed. C99 named
initializers avoid this problem, and also automatically clear any
values that are not explicitly set.
This patch updates lfs_hsm_state() to use the C99 syntax.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/27525
Lustre-commit:
73c2c103f4f43f9bb37119a2e90d6c0fc1870711
Signed-off-by: Steve Guminski <stephenx.guminski@intel.com>
Change-Id: I32f427396e99f1b86d329eb8457883a9aaaed181
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30499
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Andreas Dilger [Thu, 6 Jul 2017 06:55:08 +0000 (00:55 -0600)]
LU-9611 lov: allow lov.*.stripe{size,count}=-1 param
Since LU-7344 patch http://review.whamcloud.com/16930 was landed,
lov_stripeoffset_seq_write() and lov_stripecount_seq_write() have
incorrectly checked that lov.*.stripecount and lov.*.stripeoffset
are not negative. In fact they can both be "-1" to indicate that
the filesystem-wide default value should be used. These parameters
can also be set internally if using "lfs setstripe -c -1 $MOUNT"
or "lfs setstripe -i -1 $MOUNT" to set the system wide default,
generating console errors on the MDS from class_process_proc_param():
lov.: error writing proc entry 'stripecount': rc = -34
lov.: error writing proc entry 'stripeoffset': rc = -34
Fix these functions to allow "-1" as a valid value.
Lustre-change: https://review.whamcloud.com/27946
Lustre-commit:
f93276d9a5b5df475c9f6007265692632d8e7222
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Change-Id: I295d2591d535b039634689524a29725e963ebbe5
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30407
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Quentin Bouget [Tue, 17 Oct 2017 19:14:41 +0000 (19:14 +0000)]
LU-9474 tests: add the stack_trap() utility function
This patch implements the stack_trap() function and uses it in
test_24d of sanity-hsm (where the need for it first arose).
The stack_trap() function is meant to be used to register multiple
cleanup actions on a single sigspec (most likely EXIT). Over time,
any call to bash's trap builtin in tests should be replaced by a call
to stack_trap().
Note that cleanup functions do not need to start with "trap - EXIT".
Each test is run in a subshell of its own (in run_one_logged()) and
therefore traps do not leak from one test to another. This is true
with or without this patch.
This is a port to b2_10 of
Lustre change: https://review.whamcloud.com/#/c/29653/
Lustre commit:
1dfda720c080e39890e5a659a30c8988ca498a7c
Test-Parameters: trivial testlist=sanity-hsm,sanity-hsm
Change-Id: I47f92a963f094d3d7055592a748e81ce357bff75
Signed-off-by: Quentin Bouget <quentin.bouget@cea.fr>
Reviewed-on: https://review.whamcloud.com/29653
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Dominique Martinet <dominique.martinet@cea.fr>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
(cherry picked from commit
1dfda720c080e39890e5a659a30c8988ca498a7c)
Reviewed-on: https://review.whamcloud.com/30371
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Emoly Liu [Wed, 6 Dec 2017 07:06:00 +0000 (15:06 +0800)]
LU-10330 tests: fix version check in sanity.sh test_101g
The 16MB RPC patch is available in 2.7.x, so one more version
check needs to be added to 2.7.17 or later to avoid interop
failure.
Test-Parameters: trivial
Change-Id: I6eeefbf74017aaeeb8998accd6da04d8de75606c
Signed-off-by: Emoly Liu <emoly.liu@intel.com>
Reviewed-on: https://review.whamcloud.com/30365
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: Minh Diep <minh.diep@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Nunez [Mon, 20 Nov 2017 04:22:38 +0000 (21:22 -0700)]
LU-9872 tests: modify check space requirements for NFS test
In parallel-scale-nfs testing, the Lustre clients NFS mounts
the Lustre file system. In some cases, the file system looks
like it has enough space (du) to run NFS testing, but one or
more OSTs is full or is almost full. Since the default striping
for Lustre is a single stripe, some NFS tests will fail because
the file it is writing gets written to that almost full OST.
Increase the default stripe to all OSTs for all
parallel-scale-nfs tests.
Lustre-change: https://review.whamcloud.com/29786
Lustre-commit:
0b8e9558e88930814857c97dfe2394f8c8e24a9a
Test-Parameters: trivial testlist=parallel-scale,parallel-scale-nfsv3,parallel-scale-nfsv4
Signed-off-by: James Nunez <james.a.nunez@intel.com>
Change-Id: Iff187dc6c158d9063cd36ced0801b88cdc8814ae
Reviewed-by: James Casper <jamesx.casper@intel.com>
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30353
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Jadhav Vikram [Thu, 9 Feb 2017 06:25:57 +0000 (11:55 +0530)]
LU-9509 tests: fix compilebench timeout
With ext4 and lustre found compilebench always takes more time in
create dir operation whenever previous same test aborted without
deleting directory. As per test board result, found compilebench
test ran from suite parallel-scale-nfs.sh timedout before running
from suite parallel-scale.sh, so 1st timedout compilebench not
clear data, rerunning compilebench again causes timeout.
Fix is creating different directory on each run of compilebench.
Lustre-change: https://review.whamcloud.com/27131
Lustre-commit:
d15fe1fbb261107b021cd6ebe8b8c435d2148e0f
Seagate-bug-id: MRP-3753
Signed-off-by: Jadhav Vikram <jadhav.vikram@seagate.com>
Reviewed-by: Alexander Lezhoev <alexander.lezhoev@seagate.com>
Reviewed-by: Ashish Purkar <ashish.purkar@seagate.com>
Change-Id: I9b47e28fe5c638f4167c05fb68e46ec5e90de09e
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30352
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Jinshan Xiong [Fri, 15 Sep 2017 19:23:58 +0000 (19:23 +0000)]
LU-9997 ldlm: check lock cancellation in ldlm_cli_cancel()
In that case, the assert for 'list_empty(&lock->l_bl_ast)' will fail
because the lock is already in a cancel list.
This patch checks if the lock is already being canceled in prior.
Lustre-change: https://review.whamcloud.com/29080
Lustre-commit:
f4ea4017b4d6a420146b2959f9feb11866858b4a
Signed-off-by: Jinshan Xiong <jinshan.xiong@intel.com>
Change-Id: I04b9df789cf3b3b5e6dd61a647376307f9975f4a
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Bobi Jam <bobijam@hotmail.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30339
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Patrick Farrell [Mon, 21 Aug 2017 09:45:05 +0000 (04:45 -0500)]
LU-9894 lfsck: Print correct lfsck start info
When printing which scan type was started, lfsck iterates
through an array of types and compares the given type to
the types in the array. Type numbers are a bit mask.
However, LFSCK_TYPES_SUPPORTED and LFSCK_TYPES_DEF are the
full mask, and they are the first in the array. This means
we always match LFSCK_TYPES_SUPPORTED, which results in
always printing "all" as the type of scan.
Reorder the struct to increasing bit order to fix this.
Test-Parameters: trivial testlist=sanity-scrub,sanity-lfsck
Lustre-change: https://review.whamcloud.com/28604
Lustre-commit:
0c6805b2a0d575331dff0c22a657da91f61a1809
Signed-off-by: Patrick Farrell <paf@cray.com>
Change-Id: Ibc82369ff6531b56ceda4b1c0a833720dc61f3f4
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30265
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Steve Guminski [Fri, 19 May 2017 19:25:37 +0000 (15:25 -0400)]
LU-6210 utils: Use C99 initializer for lfsck_types_names
This patch makes no functional changes. The lfsck_types_names
struct initializer in lustre_lfsck.c is updated to C99 syntax.
C89 positional initializers require values to be placed in the
correct order. This will cause errors if the fields of the struct
definition are reordered or fields are added or removed. C99 named
initializers avoid this problem, and also automatically clear any
values that are not explicitly set.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/27791
Lustre-commit:
a1d62378ed98e2663c1f95f955433e2a5b13d68c
Signed-off-by: Steve Guminski <stephenx.guminski@intel.com>
Change-Id: I8a3b44b56263b00a926550e4122193300c0c399f
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30264
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Nunez [Fri, 11 Aug 2017 19:45:52 +0000 (13:45 -0600)]
LU-9860 tests: Add conf-sanity tests to ALWAYS_EXCEPT list
The following tests fail when run with a separate MDS and MGS:
conf-sanity tests 33a, 43b, 53b, 54b, 70e, 80, 84, 87, 100,
102, 103, 104, 105 and 107.
We need to add these tests to the ALWAYS_EXCEPT list
when running with a separate MDS and MGS.
Test-Parameters: trivial combinedmdsmgs=false testlist=conf-sanity envdefinitions=SLOW=yes
Signed-off-by: James Nunez <james.a.nunez@intel.com>
Change-Id: I1b17714216e14ad04eb9a492cb5f1aa4ed82bd1a
Reviewed-on: https://review.whamcloud.com/28497
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Wei Liu <wei3.liu@intel.com>
Reviewed-by: Dilip Krishnagiri <dilipx.krishnagiri@intel.com>
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
(cherry picked from commit
5297bfa671bd2cbb18fb3188c4d9e3b8edf3284a)
Reviewed-on: https://review.whamcloud.com/30216
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Nunez [Mon, 21 Aug 2017 22:26:30 +0000 (16:26 -0600)]
LU-9899 tests: mount client on MGS for ost-pools
When a Lustre configuration has the MGS and MDS on separate
nodes, the file system must be mounted on the MGS to allow
OST pools to work properly.
Add the ability to mount the file system on the MGS when
necessary for the Lustre test suite ost-pools.sh.
Test-Parameters: trivial testlist=ost-pools
Signed-off-by: James Nunez <james.a.nunez@intel.com>
Change-Id: Iff0663a38b92bb8e71c313897b12fca98fdae932
Reviewed-on: https://review.whamcloud.com/28638
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Arshad Hussain <arshad.hussain@seagate.com>
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
(cherry picked from commit
bb4c3bc38eeeeec111c14c024669465addb30c70)
Reviewed-on: https://review.whamcloud.com/30215
Reviewed-by: Arshad Hussain <arshad.super@gmail.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nikolay Borisov [Fri, 17 Nov 2017 14:23:04 +0000 (16:23 +0200)]
LU-10255 tests: Fix wrong comparison operator in sanity 129
Currently sanity 129 uses numerica (-eq) operator to check whether
the has_warning variable is true or false depending on whether
expected warnings have been detected. This is wrong since bash
doesn't really have bolean types and true/false are not evaluated to
1/0. This results in the following bash error when the test is run:
./sanity.sh: line 9244: [: true: integer expression expected
Fix it by using the correct string operator '=' to check for
correct value.
Test-Paramters: clientdistro=sles12sp2 testlist=sanity
Test-Paramters: clientdistro=sles12sp3 testlist=sanity
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Change-Id: I071dcb3001ea9b2e5806d346dcd48bfcaf3297e9
Reviewed-on: https://review.whamcloud.com/30151
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Tested-by: Jenkins
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nikolay Borisov [Thu, 9 Nov 2017 10:39:19 +0000 (12:39 +0200)]
LU-10217 test: Make sanity 248 work with newer dds
This patch fixes 2 problems when working with value from dd.
Firstly, extraction of the readings from dd rely on them always
being in field number 6. However, that's not true for newer dd
versions where the output has changed and the time reading is now in
field number 10. So to make the code more generic and work with both
old and new outputs switch to using an egrep regular expression to
extract the correct field.
Secondly, dd can output its time in scientific notation, with
decimal and floating point portion being separated by a comma rather
than a dot:
4096 bytes (4,1 kB, 4,0 KiB) copied, 9,1229e-05 s, 44,9 MB/s
Unforuntately this is not understood by bc so it needs to be
processed by substituting the comma for a dot and also expanding
the scientific notation to multiplication of 10 to the correct power.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Change-Id: I83ec659874ffe702c68f94f828827ff93325db72
Reviewed-on: https://review.whamcloud.com/30144
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Alex Zhuravlev [Tue, 29 Aug 2017 12:08:42 +0000 (15:08 +0300)]
LU-9660 ptlrpc: do not wakeup every second
Even if there are no RPC requests on the set, there is no need to
wake up every second. The thread is woken up when a request is added
to the set or when the STOP bit is set, so it is sufficient to only
wake up when there are requests on the set to worry about.
Lustre-change: https://review.whamcloud.com/28776
Lustre-commit:
e81847bd06519dd9847c31244abe6da978bcd016
Change-Id: Iac01d8c46e8645ecb6303ce72e0f6c59f16dcd5d
Signed-off-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Patrick Farrell <paf@cray.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29969
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Wang Shilong [Tue, 19 Sep 2017 13:10:48 +0000 (21:10 +0800)]
LU-10011 utils: suppress annoying messages for project quota
See following output:
[wsl@w003 ~]$ lfs quota /lustre1
Disk quotas for usr wsl (uid 14434):
Filesystem kbytes quota limit grace files quota limit
grace
/lustre1 0 0 0 - 0 0 0 -
Disk quotas for grp se (gid 1000):
Filesystem kbytes quota limit grace files quota limit
grace
/lustre1 44028 0 0 - 40 0 0 -
Unexpected quotactl error: Operation not supported
Disk quotas for prj <unknown> (pid 0):
Filesystem kbytes quota limit grace files quota limit
grace
/lustre1 [0] [0] [0] - [0] [0] [0] -
Some errors happened when getting quota info. Some devices may be not
working or deactivated. The data in "[]" is inaccurate.
Since project quota is disabled in default, unsupported project
quota messages will be annoying here.
Even Project quota is enabled, project id 0 will be outputed here,
it dose not make much sense either, instead, lfs quota <mnt> will only
output current user/group quota information in default
Lustre-change: https://review.whamcloud.com/29107
Lustre-commit:
0ba70b538768871f8504aca1ed6a24472f46a87d
Change-Id: Ie76ba14c4c4486a9246aafed0e8538eaae85ee98
Signed-off-by: Wang Shilong <wshilong@ddn.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Li Xi <lixi@ddn.com>
Reviewed-by: Emoly Liu <emoly.liu@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29600
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nathaniel Clark [Fri, 6 Oct 2017 16:49:23 +0000 (12:49 -0400)]
LU-10098 scripts: Fix mounted check in Lustre RA
The "Lustre" resource agent for pacemaker can mis-identify a resource
as being mounted if it's mountpoint is a substring match for anything
else in /proc/mounts. Change the lustre_is_mounted() function to
check to make sure it's a lustre fs mounted at mountpoint and the
"source" (i.e. device) is the target we expect.
Lustre-change: https://review.whamcloud.com/29351
Lustre-commit:
df96fab178534adb34067b20490a2d0629aabe2f
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: Ib877b0dc3d3ce0d93fd4663aa2418ac21d670428
Reviewed-by: Malcolm Cowe <malcolm.j.cowe@intel.com>
Reviewed-by: Olaf Faaland-LLNL <faaland1@llnl.gov>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29352
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
John L. Hammond [Tue, 12 Dec 2017 00:51:14 +0000 (18:51 -0600)]
New release 2.10.2.
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: I495068f728dfe75e82f2498a3fbdf9e15f06c58c
John L. Hammond [Wed, 6 Dec 2017 01:26:48 +0000 (19:26 -0600)]
New tag 2.10.2-RC2.
Second release candidate for 2.10.2 release.
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: I0ced71f744d66a8abc3ce7e51a61fbc45dc6c6e7
Sebastien Buisson [Thu, 9 Nov 2017 15:48:08 +0000 (00:48 +0900)]
LU-10220 mdd: fix buf alloc in mdd_changelog_data_store_by_fid
Fix allocation of mti_big_buf by call to lu_buf_check_and_alloc()
in mdd_changelog_data_store_by_fid().
reclen must take the header size of struct llog_changelog_rec into
account.
Maybe no memory corruptions were seen before because the buffer size
allocated in a previous call to mdd_declare_changelog_store() was
covering the need. But audit will add more information in changelog
records, provoking memory corruptions without this fix.
Lustre-change: https://review.whamcloud.com/30014
Lustre-commit:
f173f93032c62bd1f95330f331d3d93ce5a31598
Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
Change-Id: Id0a06c412b54c0ae12c15d53f3e166e3e5d9ed68
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Henri Doreau <henri.doreau@cea.fr>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Faccini Bruno <bruno.faccini@intel.com>
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30356
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
John L. Hammond [Tue, 14 Nov 2017 18:23:28 +0000 (12:23 -0600)]
LU-8497 osp: handle remote -ENOMEM from osp_send_update_req()
In osp_send_update_req() detect an unsent request by checking
rq_queued_time == 0 rather than rq_set == NULL, which is always true
after returning from ptlrpc_queue_wait().
Lustre-change: https://review.whamcloud.com/30083
Lustre-commit:
cef8983c8b5bf51b58df23a779769cc4b8ca8db5
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: Ief959b71600157a9c3521775cc06994326e50c51
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30354
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Bobi Jam [Sat, 2 Sep 2017 08:34:23 +0000 (16:34 +0800)]
LU-9941 lov: lsm_is_composite isn't right
LOVEA magic containing LOV_MAGIC_MAGIC will also be regarded as
a composite magic.
Signed-off-by: Bobi Jam <bobijam.xu@intel.com>
Change-Id: I3ef37ee80364b2a8f27831e3c53fb88b464f2039
Reviewed-on: https://review.whamcloud.com/28845
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Jinshan Xiong <jinshan.xiong@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
(cherry picked from commit
385518f67eb917335de0c1d727941094f4ab5874)
Reviewed-on: https://review.whamcloud.com/30342
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Bobi Jam <bobijam@hotmail.com>
John L. Hammond [Mon, 27 Nov 2017 15:15:49 +0000 (09:15 -0600)]
New tag 2.10.2-RC1.
First release candidate for 2.10.2 release.
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: I207f36c4e6815dfb06ba7b9622e939ade167eb89
Quentin Bouget [Wed, 15 Nov 2017 15:41:53 +0000 (15:41 +0000)]
LU-10234 tests: use wait correctly in sanity-hsm test_3[4-6]
Test 34, 35 and 36 did not properly check the return code of wait
and potentially missed regressions.
Test-Parameters: trivial testlist=sanity-hsm
Signed-off-by: Quentin Bouget <quentin.bouget@cea.fr>
Change-Id: I21e8b16b55b946a8e5837549c3a3698379132e48
Reviewed-on: https://review.whamcloud.com/30102
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Dominique Martinet <dominique.martinet@cea.fr>
Reviewed-by: Henri Doreau <henri.doreau@cea.fr>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: Ben Evans <bevans@cray.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
(cherry picked from commit
eec4b8985f5eaacd13f0e0db7328dcdd610655bc)
Reviewed-on: https://review.whamcloud.com/30208
Reviewed-by: John L. Hammond <john.hammond@intel.com>
John L. Hammond [Tue, 24 Oct 2017 15:28:57 +0000 (10:28 -0500)]
LU-10086 libcfs: use dynamic minors for /dev/{lnet,obd}
Request dynamic minor allocation when registering /dev/lnet and
/dev/obd. Remove the obsolete create-device-if-not-found code from
register_ioc_dev().
Lustre-change: https://review.whamcloud.com/29741
Lustre-commit:
e446c1667dc9136e3a1cb3603c3851975b68e0ac
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: I59c70912b4729f58a76dc6107b3e1d7379c6d7a3
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29945
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Bob Glossman [Tue, 14 Nov 2017 20:44:15 +0000 (12:44 -0800)]
LU-10241 kernel: kernel update RHEL6.9 [2.6.32-696.16.1.el6]
Update RHEL6.9 kernel to 2.6.32-696.16.1.el6
Test-Parameters: clientdistro=el6.9 mdsdistro=el6.9 \
ossdistro=el6.9 mdtfilesystemtype=ldiskfs \
ostfilesystemtype=ldiskfs testgroup=review-ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: Ib2215b56e647fb8e19bc8b7e344a94564c7a8c7f
Reviewed-on: https://review.whamcloud.com/30131
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Henri Doreau [Fri, 27 Oct 2017 07:31:58 +0000 (09:31 +0200)]
LU-10166 mdc: invalid free in changelog reader
Use kthread_stop() to instruct the producer thread to exit
when the device is closed, and only then: release the CRS
structure.
The previous implementation left small time windows open,
during which the producer threads could free a structure
before the consumer thread was completely done with it.
Change-Id: Id2038aa9b7fcfd2c3347f628e749f9d2c265ac6e
Signed-off-by: Henri Doreau <henri.doreau@cea.fr>
Reviewed-on: https://review.whamcloud.com/29818
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Quentin Bouget <quentin.bouget@cea.fr>
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
(cherry picked from commit
89e52326b5bd3d2716ce6ec5d9f9d787947d91a1)
Reviewed-on: https://review.whamcloud.com/30207
Emoly Liu [Thu, 9 Nov 2017 08:23:48 +0000 (16:23 +0800)]
LU-10040 nodemap: add nodemap idmap correctly
There are 3 situations when adding an idmap {id_client:id_fs} to
a nodemap tree:
- both id_client and id_fs are matched, that means this idmap
already exists, so return -EEXIT;
- neither id_client nor id_fs is matched, that means this is a
new idmap, so insert it;
- only "id_client" or "id_fs" is matched, since idmap uses
"id_client" as index key, we need to delete that old idmap and
its index by its id_client, and then insert it again. In the
original implementation, idmap_insert() calls rb_replace_node()
to replace the old idmap without re-sorting its both id_client
and id_fs, so that this new added idmap can't be found by
idmap_search() due to its wrong left and right nodes, and can't
be deleted either.
Also, this patch improves the following code:
- nm_idmap_lock: use type rw_semaphore instead of rwlock, because
nodemap_idx_idmap_del() may sleep on FS operations while this
lock is being held.
- Add "update_idmaps" to sanity-sec.sh test_15 to verify this fix,
and improve other part of this test case as well to make it run
correctly.
Test-Parameters: testlist=sanity-sec
Signed-off-by: Stephan Thiell <sthiell@stanford.edu>
Signed-off-by: Emoly Liu <emoly.liu@intel.com>
Change-Id: Icf777f14c2e1dd56fa5cd0eb56666240e206d199
Reviewed-on: https://review.whamcloud.com/29364
Tested-by: Jenkins
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Sebastien Buisson <sbuisson@ddn.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
(cherry picked from commit
253ccbd55ffe7fcdc405c9fcc4f72a47578920fe)
Reviewed-on: https://review.whamcloud.com/30206
Alex Zhuravlev [Thu, 28 Sep 2017 11:34:33 +0000 (14:34 +0300)]
LU-10041 tests: sanity/51 to cleanup properly
sanity/51 should cleanup properly in case of failure
Test-Parameters: trivial testlist=sanity ostfilesystemtype=zfs mdtfilesystemtype=zfs
Test-Parameters: trivial testlist=sanity mdscount=2 mdtcount=4
Lustre-change: https://review.whamcloud.com/29246
Lustre-commit:
0d5ceb891e904cc9bab3a6b5ce0944b8bab06975
Change-Id: Ib1c0e1a116a6802f2bf25d665be5c076ae07c8b8
Signed-off-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: Wei Liu <wei3.liu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/30023
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nikolay Borisov [Tue, 7 Nov 2017 16:44:11 +0000 (18:44 +0200)]
LU-10204 tests: Fix line continuation
There is a simple missing in one of the error paths in
ladvise_willread_performance which results in an unknown command
error. Fix it by adding the missing backslash.
Test-Parameters: trivial
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Change-Id: Ifff854c6cf5c1add71fd1571cb4de01d56204fde
Reviewed-on: https://review.whamcloud.com/29982
Tested-by: Jenkins
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Nathaniel Clark [Thu, 21 Sep 2017 17:09:18 +0000 (13:09 -0400)]
LU-10007 pacemaker: Use lctl and load lustre
When scripts are started, load lustre module.
Use lctl instead of directly accessing health_check file.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/29144
Lustre-commit:
6e299c2a3bd7566a322cf9bc9494f6850d2c1b7e
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: I4a81248939464e498006dc2c4072d44685add018
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29946
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Alexander Boyko [Thu, 21 Sep 2017 13:13:27 +0000 (16:13 +0300)]
LU-10015 o2iblnd: fix race at kiblnd_connect_peer
cmid will be destroyed at OFED if kiblnd_cm_callback return error.
if error happen before the end of kiblnd_connect_peer, it will touch
destroyed cmid and fail as
(o2iblnd_cb.c:1315:kiblnd_connect_peer())
ASSERTION( cmid->device != ((void *)0) ) failed:
Lustre-change: https://review.whamcloud.com/29134
Lustre-commit:
576551cb97c6a5efb27d8afc59ad60550dde51ce
Seagate-bug-id: MRP-4592
Signed-off-by: Alexander Boyko <alexander.boyko@seagate.com>
Change-Id: I83eb5bceeb567acef0316498b936d25d6c6ccd95
Reviewed-by: Alexey Lyashkov <c17817@cray.com>
Reviewed-by: Doug Oucharek <dougso@me.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29881
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Gu Zheng [Wed, 18 Oct 2017 19:10:53 +0000 (15:10 -0400)]
LU-9951 lustre_compat: add wrapper function for posix_acl_update_mode
posix_acl_update_mode is introduced in kernel 4.9, add the precheck
of it, if not exists, use inline wrapper function instead.
Lustre-change: https://review.whamcloud.com/28871
Lutre-commit:
ec6bdd55bb2128dcf9779017ef9623461afe05f8
Change-Id: I8a1476d611c387a88efef5d5b8707edf5feacca8
Signed-off-by: Gu Zheng <gzheng@ddn.com>
Reviewed-by: Wang Shilong <wshilong@ddn.com>
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29880
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Bob Glossman [Fri, 29 Sep 2017 22:27:12 +0000 (15:27 -0700)]
LU-10047 tests: stop skipping test_102 subtests
Remove obsolete version check on tar.
All tar versions in supported distros are now capable of --xattrs.
But not all tar version have --xattrs-include, so must test for and
adapt for that.
Lustre-commit:
036641a1e1f6d5d010873267b669528890f19fe4
Lustre-change: https://review.whamcloud.com/29288
Test-Parameters: trivial envdefinitions=ONLY=102 testlist=sanity
Test-Parameters: trivial clientdistro=el6.9 envdefinitions=ONLY=102 testlist=sanity
Test-Parameters: trivial clientdistro=sles12sp2 envdefinitions=ONLY=102 testlist=sanity
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I5e76bd1a762c4e01cf8a3a33789ca3a30c15abb0
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-on: https://review.whamcloud.com/29823
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Jian Yu [Fri, 7 Jul 2017 06:16:06 +0000 (23:16 -0700)]
LU-9663 tests: replace “ls -s” with “stat -c '%s'” to get file size
This patch improves acl/2561{,_zfs}.test to use “stat -c '%s'” to
get file size instead of using “ls -s”, which prints the allocated
size of the file in blocks.
Test-Parameters: trivial \
envdefinitions=ONLY=103 \
mdtfilesystemtype=zfs ostfilesystemtype=zfs \
testlist=sanity
Lustre-change: https://review.whamcloud.com/27961
Lustre-commit:
45b8c6cf6916cf012ad0512f9cf249c152b45236
Change-Id: I8bfea5197102baeece244e20731c90172c5cc2f1
Signed-off-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29816
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nathaniel Clark [Thu, 5 Oct 2017 11:43:26 +0000 (07:43 -0400)]
LU-9752 man: Reference zgenhostid instead of genhostid
In ZFS 0.7.0, they added zgenhostid(8) to be used in place of
Redhat's genhostid, so that there would be a platform agnostic
way to generate /etc/hostid.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/29327
Lustre-commit:
a1eb6de081473545fbd5c1fe33e209fe391bf708
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: I691266d04f91d5fa7c50b72948c801afa69d647d
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29805
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Alex Zhuravlev [Thu, 1 Jun 2017 07:20:12 +0000 (11:20 +0400)]
LU-9578 llite: use security context if it's enabled in the kernel
if it's disabled, then Lustre stop to work properly (can not create
files, etc)
Lustre-change: https://review.whamcloud.com/27364
Lustre-commmit:
61f26ea47f96632a90702f2b404e845a01498612
Change-Id: I1e431ec95a2b0613b43893567eb6d1a64ec832de
Signed-off-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Chris Horn <hornc@cray.com>
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Sebastien Buisson <sbuisson@ddn.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29737
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Henri Doreau [Thu, 19 Oct 2017 08:14:18 +0000 (10:14 +0200)]
LU-10141 llapi: integer overflow in llapi_changelog_start
Use the appropriate type to store and check the return value from lseek.
This prevents from misinterpreting high offsets as errors.
Lustre-change: https://review.whamcloud.com/29674
Lustre-commit:
aaa808e7a40198581956a1d648f413cc30e830ed
Change-Id: I15e92be3454af20ee6611c2a7ddfc1b597d639c2
Signed-off-by: Henri Doreau <henri.doreau@cea.fr>
Reviewed-by: Thomas LEIBOVICI <thomas.leibovici@cea.fr>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Stephan Thiell <sthiell@stanford.edu>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29735
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Nathaniel Clark [Mon, 23 Oct 2017 14:52:57 +0000 (10:52 -0400)]
LU-10150 build: Build with ZFS 0.7.3
Update ZFS and SPL version to 0.7.3
Also Fixup ChangeLog
Changelog: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.3
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: I88f0f2601262c0c535431d256a159d9e9d6ebd75
Reviewed-on: https://review.whamcloud.com/29713
Tested-by: Jenkins
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Di Wang [Wed, 13 Sep 2017 00:53:13 +0000 (00:53 +0000)]
LU-9840 lod: add ldo_dir_stripe_loaded
Add ldo_dir_stripe_loaded flag to avoid loading
stripes mulitple times especcially for non-stripe
directory.
Lustre-change: https://review.whamcloud.com/28962
Lustre-commit:
744fe412fa101609a38f7ccc77efc4f1c540e008
Change-Id: Ia9360aac9e24706e401184c75fae4ec7f8ec46d9
Signed-off-by: Di Wang <di.wang@intel.com>
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-on: https://review.whamcloud.com/29143
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Fri, 27 Oct 2017 16:37:41 +0000 (09:37 -0700)]
LU-10168 kernel: kernel update [SLES12 SP2 4.4.90-92.45]
Update target and kernel_config files for new version
Test-Parameters: clientdistro=sles12sp2 testgroup=review-ldiskfs \
mdsdistro=sles12sp2 ossdistro=sles12sp2 \
mdtfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: If24eddeeadc825b1b3073439304c0958c0ae1b74
Reviewed-on: https://review.whamcloud.com/29840
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Minh Diep <minh.diep@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
John L. Hammond [Tue, 17 Oct 2017 20:32:52 +0000 (15:32 -0500)]
LU-10132 llite: handle xattr cache refill race
In ll_xattr_cache_refill() if the xattr cache was invalid (and no
request was sent) then return -EAGAIN so that ll_getxattr_common()
caller will fetch the xattr from the MDT.
Lustre-change: https://review.whamcloud.com/#/c/29654/
Lustre-commit:
9cc8c3a20c547ec75325dde3dd17f4b1dcc66348
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: Ia9ec7424e8786d92bdecf4897fafcf71d5061fb1
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29795
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Bob Glossman [Wed, 25 Oct 2017 23:53:52 +0000 (16:53 -0700)]
LU-10164 kernel: kernel update [SLES12 SP3 4.4.92-6.18]
Update target and kernel_config files for new version
Test-Parameters: clientdistro=sles12sp3 testgroup=review-ldiskfs \
mdsdistro=sles12sp3 ossdistro=sles12sp3 \
mdtfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I4b046f0ac64b75545cd0e2a3a44e9117f4d79ef4
Reviewed-on: https://review.whamcloud.com/29825
Tested-by: Jenkins
Reviewed-by: Minh Diep <minh.diep@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Thu, 19 Oct 2017 15:25:25 +0000 (08:25 -0700)]
LU-10142 kernel: kernel update RHEL7.4 [3.10.0-693.5.2.el7]
update RHEL 7.4 kernel to 3.10.0-693.5.2.el7
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I6f22d9d96b86d7bd860a400cd803fad26a6b5d1a
Reviewed-on: https://review.whamcloud.com/29728
Tested-by: Jenkins
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Patrick Farrell [Wed, 18 Oct 2017 10:24:41 +0000 (05:24 -0500)]
LU-10131 llite: Update i_nlink on unlink
Currently, the client inode link count is not updated on
last unlink. This is fine because the dentries are all
gone and the inode is eligible for reclaim, but it's still
incorrect. This causes two problems:
1. Inode is not immediately reclaimed
2. i_nlink count is > 0 for a fully unlinked file, which
confuses wrapfs
On last unlink, the MDT sends back attributes. Use the
nlink count from these to update the client inode.
Remove null check inherited from ll_get_child_fid, because
the inode should never be null on an unlink.
Re-enabled test 76, which passes with this patch.
Removed slab allocator tuning from test_76, because slab is
no longer the default Linux allocator.
Lustre-change: https://review.whamcloud.com/29651
Lustre-commit:
947b22b08d3725852a811a9e330562dd986d7336
Signed-off-by: Patrick Farrell <paf@cray.com>
Change-Id: Ib253b5cf3d35188554cf8fc33a8a3d4b8bb237e8
Reviewed-by: Ben Evans <bevans@cray.com>
Reviewed-by: Alexey Lyashkov <c17817@cray.com>
Reviewed-by: Andrew Perepechko <c17827@cray.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29785
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Alex Zhuravlev [Thu, 28 Sep 2017 11:30:55 +0000 (14:30 +0300)]
LU-10041 osd: osd-zfs to choose dnode size
depending on dnodesize property it can be:
legacy (512 bytes), auto (512 bytes to 16K) or absolute
size (512, 1024, 2048, 4096, 8192, 16384).
Lustre-change: https://review.whamcloud.com/29242
Lustre-commit:
d993de7b40cd9625b48e5361ae29f77bfceb207a
Change-Id: Iea35d8ae850523440272467320410850821f484c
Signed-off-by: Alex Zhuravlev <bzzz@whamcloud.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29770
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Alexey Lyashkov [Thu, 20 Jul 2017 09:06:18 +0000 (14:36 +0530)]
LU-9782 osd-ldiskfs: avoid extra search
Extent tree grow greatly durin random IO test with small block size.
osd_is_mapped responsible to large cpu consumption in this case.
| |
| |--94.49%-- ldiskfs_es_find_delayed_extent_range
| | ldiskfs_fiemap
| | osd_is_mapped
| | osd_declare_write_commit
| |
| |--5.49%-- ldiskfs_fiemap
| | osd_is_mapped
| | osd_declare_write_commit
|
|--21.80%-- ldiskfs_es_find_delayed_extent_range
| |
| |--100.00%-- ldiskfs_fiemap
| | osd_is_mapped
let's cache a osd_is_mapped result to avoid extra search in extent
tree,
Lustre-change: https://review.whamcloud.com/28145
Lustre-commit:
1eb0573fdeb7ef8ed667974fd30d4d110b8166c9
Seagate-bug-id: MRP-4474
Signed-off-by: Alexey Lyashkov <alexey.lyashkov@seagate.com>
Change-Id: I63d480bfc7c6b7599b80ceeec9447b227a1610c8
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Andrew Perepechko <andrew.perepechko@seagate.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29739
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Andrew Perepechko <c17827@cray.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Andreas Dilger [Wed, 4 May 2016 05:29:42 +0000 (23:29 -0600)]
LU-7990 llite: increase whole-file readahead to RPC size
Increase the default whole-file readahead limit to match the current
RPC size. That ensures that files smaller than the RPC size will be
read in a single round-trip instead of sending multiple smaller RPCs.
Lustre-change: https://review.whamcloud.com/26955
Lustre-commit:
627d0133d9d7bef908544537a8a2b2093719fc72
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Change-Id: I3bdb1c7f92c546d58951a9e6b783af23c83ebbe5
Reviewed-by: Patrick Farrell <paf@cray.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29738
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Andreas Dilger [Wed, 13 Sep 2017 16:47:07 +0000 (10:47 -0600)]
LU-4705 mdc: improve mdc_enqueue() error message
Include the parent/child FIDs and name in the mdc_enqueue()
debug message.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/28978
Lustre-commit:
471c5303eb29d5ea1ba5a683173bda63095dae78
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Change-Id: I7b84921a52a4650be70fe87eea691ba2217bb3a6
Reviewed-by: Steve Guminski <stephenx.guminski@intel.com>
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29736
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Yang Sheng [Tue, 15 Aug 2017 10:42:09 +0000 (18:42 +0800)]
LU-9814 ldiskfs: restore simple_strtol in prealloc
Since kstrtol needs a null-terminor string so we
back to use simple_strtol in prealloc patches.
Lustre-change: https://review.whamcloud.com/28553
Lustre-commit:
685ef61f0fb9849e3f7a32c4ebf2980d3300afb0
Signed-off-by: Yang Sheng <yang.sheng@intel.com>
Change-Id: I331308d830fbeef9c00156bb8c14b43651d66420
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: Alexey Lyashkov <c17817@cray.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29733
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Wang Shilong [Mon, 25 Sep 2017 12:35:26 +0000 (20:35 +0800)]
LU-10029 osd-ldiskfs: make project inherit attr removeable
Inherit attribute should be clearable now
Lustre-change: https://review.whamcloud.com/29189
Lustre-commit:
9d068048603fefbab1eea8d8bb5a246ce4375dca
Signed-off-by: Wang Shilong <wshilong@ddn.com>
Change-Id: I878fde0dc134c9820436ee80979d87e6dacfb70d
Reviewed-by: Niu Yawei <yawei.niu@intel.com>
Reviewed-by: Li Xi <lixi@ddn.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29688
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Qian Yingjin [Thu, 29 Jun 2017 09:03:44 +0000 (17:03 +0800)]
LU-9140 nrs: measure the runtime of dd directly
This patch changes the way to measure the runtime of "dd". Instead
of parsing the output of "dd", we use date command to calculate
the runtime of dd directly, avoiding the parsing failure caused
by changed output format of "dd".
Lustre-change: https://review.whamcloud.com/27878
Lustre-commit:
66abf6ffe9f032aaa7c271ee2bd1f9b569058bd5
Change-Id: Ibd2e3963f791404ee927981238227012cf4dbf2c
Test-Parameters: trivial testlist=sanityn
Signed-off-by: Qian Yingjin <qian@ddn.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29686
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Wei Liu [Wed, 23 Aug 2017 16:49:29 +0000 (09:49 -0700)]
LU-9260 test: Use the correct mount device when test against lustre
The changes pass the MGSNID:/FSNAME into test, instead of
using the default loop device when testing against lustre.
The corresponding changes to the Posix test suites are also needed
to make the testing pass. Related changes apply to toolkit.
Test-Parameters: trivial testlist=posix
Lustre-change: https://review.whamcloud.com/28661
Lustre-commit:
7b59ed3ab3c9bfae95b9904982869d31a7e65770
Change-Id: I32fc5a401fdc53ed133a78dc4c84b4a7e2a5ad19
Signed-off-by: Wei Liu <wei3.liu@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29628
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nathaniel Clark [Thu, 31 Aug 2017 19:54:53 +0000 (15:54 -0400)]
LU-9888 tests: Update disk2_7-zfs.tar.bz2 for quota
Add a blimit file with the larger 40960 limit in it, as this seems to
be how the image was created, but the default (without this file) is
20K.
Also add an ilimit file with 4 (default for new images). Old default
value is 2.
This patch rolls in LU-9826 fix for larger ZFS
Lustre-change: https://review.whamcloud.com/28464
Lustre-commit:
6ab9866730c1bd2344869502586fc322f6ed7b71
This patch on master
Lustre-change: https://review.whamcloud.com/28820
Lustre-commit:
f37b25fbb4acf3f96ebc61bb4d9137a8f0401e35
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: I33921ac58a5252f3259145d5e00faedcd21559f9
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Wei Liu <wei3.liu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29068
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bruno Faccini [Tue, 18 Jul 2017 08:21:53 +0000 (10:21 +0200)]
LU-7988 hsm: update many cookie status at once
Instead of calling mdt_agent_record_update, which calls
cdt_llog_process, once for every HAL, build a list of the cookies to
update with their status and call mdt_agent_record_update just once
per seconds at most.
Update mdt_agent_record_update to take a status for every cookie.
Test-Parameters: trivial testlist=sanity-hsm
Lustre-change: https://review.whamcloud.com/19584
Lustre-commit:
f3a415289b560b5f422efe2bd08b3b7cff113cf0
Signed-off-by: frank zago <fzago@cray.com>
Change-Id: Ie4afd667727e07570ed6a2d51e8dfaea8302b97b
Signed-off-by: Ben Evans <bevans@cray.com>
Signed-off-by: Bruno Faccini <bruno.faccini@intel.com>
Reviewed-by: Quentin Bouget <quentin.bouget@cea.fr>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28973
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bobi Jam [Tue, 20 Jun 2017 09:44:01 +0000 (17:44 +0800)]
LU-3719 ldiskfs: adjust s_mb_prealloc_table_size correctly
When mb prealloc table item value is not valid, the
s_mb_prealloc_table_size should be adjust accordingly.
Port patch to rhel7 & sles12.
Lustre-change: https://review.whamcloud.com/27748
Lustre-commit:
b9ecf2671cba08530cc49d47713a360f2c6c25ca
Signed-off-by: Bobi Jam <bobijam.xu@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Alexander Boyko <alexander_boyko@xyratex.com>
Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Change-Id: I5aa3a32a6a3aedc70160409c6443746fd2ccbbc9
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: Ben Evans <bevans@cray.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28228
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Andreas Dilger [Thu, 11 May 2017 10:43:14 +0000 (04:43 -0600)]
LU-9462 doc: update lfs setstripe man page and usage
Update the lfs-setstripe.1 man page formatting and content.
Update the "lfs setstripe" usage message to be in "common use" order.
Test-Parameters: trivial
Reviewed-on: https://review.whamcloud.com/27066
Lustre-change-by: Andreas Dilger <andreas.dilger@intel.com>
Lustre-commit:
aa83ef5a9ec470d2f6af07d47b3dd763f4a0e7ce
Signed-off-by: Steve Guminski <stephenx.guminski@intel.com>
Change-Id: Ia761c7562fa398a8c1bb4354d09757cd5f3ebbe5
Reviewed-by: Jian Yu <jian.yu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29627
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Wei Liu [Tue, 12 Sep 2017 19:30:14 +0000 (12:30 -0700)]
LU-9158 test: Use project ID for project quota for quota_scan
Use project ID instead of quota user for project quota in
function quota_scan. This is not a fix for the rebalancing error,
only correct the test script issue.
Lustre-change: https://review.whamcloud.com/28957
Lustre-commit:
3a2f24fefbc8c4b6e98dfd6ba9957326ea0e7a97
Change-Id: I9165ada17de0f32ac38f720a5e9e9be46363b41f
Signed-off-by: Wei Liu <wei3.liu@intel.com>
Reviewed-by: Wang Shilong <wshilong@ddn.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29626
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Nunez [Mon, 21 Aug 2017 23:43:19 +0000 (17:43 -0600)]
LU-9741 test: Correct check of stripe count for directories
With the progressive file layout feature, the 'lfs getstripe -d'
output will report stripe count for each component. Since
sanity test 27w checks that there is only one "stripe_count"
line in the 'lfs getstripe -d' output, this needs to be changed
to check that there is at least one "stripe_count" reported.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/27980
Lustre-commit:
1cc354d559d1df90a2eaa886eb0e3956bf385a9e
Signed-off-by: James Nunez <james.a.nunez@intel.com>
Change-Id: I51f141b2542e65d1bc296cb2cb14c12f22afdcec
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Saurabh Tandan <saurabh.tandan@intel.com>
Reviewed-by: Wei Liu <wei3.liu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29625
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Sebastien Buisson [Mon, 2 Oct 2017 20:00:52 +0000 (16:00 -0400)]
LU-9672 gss: fix expiration time of sunrpc cache
Expiration time of sunrpc cache is misinterpreted. Downcal
and response from user space must provide an epoch time,
not a duration.
And on kernel side, expiry must always be expressed in seconds
from boot, as set when retrieved from get_expiry().
Lustre-change: https://review.whamcloud.com/27667
Lustre-commit:
f35425801545e0b47279597983cfbd02e837c45f
Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
Change-Id: I35c58a040a62410374dee0be3ae5bed7956cd985
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29624
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Alex Zhuravlev [Mon, 18 Sep 2017 20:17:29 +0000 (23:17 +0300)]
LU-9967 tests: run-llog to cleanup properly
move ignore_errors so that setup's error is ignored, the script
continues with detach command needed to release the module.
Lustre-change: https://review.whamcloud.com/29057
Lustre-commit:
e3921c4727c1d2e9866e0013fd37a7a4d4616621
Change-Id: I899de7a321fa927ca9884a6e4f9e8785bbc46f7c
Signed-off-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29366
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Fan Yong [Tue, 19 Sep 2017 15:55:59 +0000 (11:55 -0400)]
LU-9887 lfsck: calculate LFSCK speed properly
Originally, we used do_div(a,b) to calculate the LFSCK average
speed, and got the result from the parameter @a. But later, we
replaced do_div(a,b) with div_u64(a,b). The latter one doesn't
stores the quotient in the parameter @a, instead, the quotient
is returned via the function return value. The patch fixes the
LFSCK logic to obtain the LFSCK average speed from div_u64(a,b)
return value.
Lustre-change: https://review.whamcloud.com/28617
Lustre-commit:
cf800c062c8c6424c442509139297095f8a708db
Signed-off-by: Fan Yong <fan.yong@intel.com>
Change-Id: I442fb8f7e6c51a4853ea37694e3c221f97e26b19
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29294
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
dilip krishnagiri [Fri, 8 Sep 2017 18:30:57 +0000 (12:30 -0600)]
LU-9963 test: add parallel-scale tests to ALWAYS_EXCEPT
add the following parallel-scale tests
parallel_grouplock :
test_parallel_grouplock: test failed to respond and timed out
Associated Jira ticket LU-9429 is in open state.
to ALWAYS_EXCEPT list.
Test-Parameters: trivial testlist=parallel-scale
Lustre-change: https://review.whamcloud.com/28914
Lustre-commit:
38c78e21ca7abe4bd6e6500d88a692e7a56a7712
Change-Id: I25709af1ab49a30498a89e5369521582c5ab6cf8
Signed-off-by: dilip krishnagiri <dilipx.krishnagiri@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Reviewed-by: James Casper <jamesx.casper@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29146
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Jinshan Xiong [Thu, 27 Jul 2017 16:49:42 +0000 (09:49 -0700)]
LU-9802 pfl: swapping lcm_entry_count correctly
It's a u16 integer so it should use le16_to_cpu() instead of
le32_to_cpu().
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/28256
Lustre-commit:
21ea1f7629535090d64ee3355c491a9e35256f23
Signed-off-by: Jinshan Xiong <jinshan.xiong@intel.com>
Change-Id: I43c31a76d78aa294a3e3296a1bb69f4d6fb1423d
Reviewed-by: Bobi Jam <bobijam@hotmail.com>
Reviewed-by: Niu Yawei <yawei.niu@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29141
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Fri, 22 Sep 2017 15:29:55 +0000 (08:29 -0700)]
LU-10023 kernel: kernel update [SLES12 SP3 4.4.82-6.9]
Update target and kernel_config files for new version
Test-Parameters: clientdistro=sles12sp3 testgroup=review-ldiskfs mdsdistro=sles12sp3 ossdistro=sles12sp3 mdtfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs
Change-Id: Ie65afb3d7356c4679f4f37f4af324e955261b5af
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Bob Glossman [Thu, 7 Sep 2017 19:37:27 +0000 (12:37 -0700)]
LU-9956 kernel: kernel upgrade [SLES12 SP3 4.4.82-6.3]
Minor linux version upgrade, but SP2 and SP3 use linux 4.4 versions.
Some new kernel patches, a few revised ldiskfs patches.
All new target and config files.
Some autoconf changes to adapt to new or altered kernel APIs.
Test-Parameters: clientdistro=sles12sp3 testgroup=review-ldiskfs mdsdistro=sles12sp3 ossdistro=sles12sp3 mdtfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Signed-off-by: Yang Sheng <yang.sheng@intel.com>
Change-Id: I99e2b6848197ea19402fa415fdb562d03e87d947
Chris Horn [Fri, 13 Oct 2017 18:58:42 +0000 (13:58 -0500)]
LU-10119 scripts: Correct shebang/hashpling format
Shebang/hashpling should not have a space between the number sign and
exclamation mark.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/29605
Lustre-commit:
dd23aa4a64c776784cee05f69560c00b36440dc7
Signed-off-by: Chris Horn <hornc@cray.com>
Change-Id: I4a31d7dd7579bfaf231284c678e4100acea77d9b
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29689
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Henri Doreau [Wed, 23 Aug 2017 15:16:25 +0000 (17:16 +0200)]
LU-9416 hsm: add kkuc before sending registration RPCs
This avoids a situation where the registration completes and the CDT
sends HSM actions just before the kkuc registration happens. In this
case the client drops the actions because there are no CT pipes in the
kkuc list.
Lustre-change: https://review.whamcloud.com/28751
Lustre-commit:
bdb04079570dd2de3b9310221e0206d64efb9ecc
Change-Id: Icbd6575f04c0ca7e8f731ee8481ec72a9ff4f2e1
Signed-off-by: Henri Doreau <henri.doreau@cea.fr>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Faccini Bruno <bruno.faccini@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29687
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Jinshan Xiong [Thu, 1 Jun 2017 19:53:35 +0000 (12:53 -0700)]
LU-9574 llite: pipeline readahead better with large I/O
Fixed a bug where next readahead is not set correctly when
appplication issues large I/O;
Extend the readahead window length to at least cover the size of
current I/O.
Lustre-change: https://review.whamcloud.com/#/c/27388/
Lustre-commit:
e94dcdcf70526177633b71cfa1c6cb68c8f28ef0
Signed-off-by: Jinshan Xiong <jinshan.xiong@intel.com>
Change-Id: I43c5e4f25ea30d4a36263db2588bde0401122990
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29016
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Patrick Farrell <paf@cray.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Mon, 18 Sep 2017 15:39:58 +0000 (08:39 -0700)]
LU-10000 kernel: kernel update [SLES12 SP2 4.4.74-92.38]
Update target and kernel_config files for new version
Test-Parameters: clientdistro=sles12sp2 testgroup=review-ldiskfs \
mdsdistro=sles12sp2 ossdistro=sles12sp2 \
mdtfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I825369d9cafd4f75dc193f614d5adfe87769fcd1
Reviewed-on: https://review.whamcloud.com/29069
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Simmons [Thu, 14 Sep 2017 13:40:56 +0000 (09:40 -0400)]
LU-9558 tests: add completion.h header to kinode.c
When building lustre on a ARM fedora box running a 4.11 kernel
kinode.c failed to build due to the completion.h header missing.
A simple including of this header fixes everything.
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/28998
Lustre-commit:
982d660edbcacd528579f25ed2a3ae076a0134f3
Change-Id: I2a193346b214616a6f5dee5049466fb55567e396
Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Frank Zago <fzago@cray.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Reviewed-on: https://review.whamcloud.com/29567
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Patrick Farrell [Mon, 18 Sep 2017 11:05:48 +0000 (06:05 -0500)]
LU-7802 ldlm: No -EINVAL for canceled != unused
If any locks are removed from or added to the lru, the
check of "number unused vs number cancelled" may be wrong.
This is fine - do not return an error or print debug in
this case.
Lustre-change: https://review.whamcloud.com/28560
Lustre-commit:
a5081b7362e44b8d38aee1112f9a7d3aae1642c0
Signed-off-by: Patrick Farrell <paf@cray.com>
Change-Id: I2ee9b8d86fbd6c9bd2c29e3472e3d410ee303374
Reviewed-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28975
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Patrick Farrell [Mon, 14 Aug 2017 10:09:35 +0000 (05:09 -0500)]
LU-8276 ldlm: Make lru clear always discard read lock pages
A significant amount of time is sometimes spent during
lru clearing (IE, echo 'clear' > lru_size) checking
pages to see if they are covered by another read lock.
Since all unused read locks will be destroyed by this
operation, the pages will be freed momentarily anyway,
and this is a waste of time.
This patch sets the LDLM_FL_DISCARD_DATA flag on all the PR
locks which are slated for cancellation by
ldlm_prepare_lru_list when it is called from
ldlm_ns_drop_cache.
The case where another lock covers those pages (and is in
use and so does not get cancelled by lru clear) is safe for
a few reasons:
1. When discarding pages, we wait (discard_cb->cl_page_own)
until they are in the cached state before invalidating.
So if they are actively in use, we'll wait until that use
is done.
2. Removal of pages under a read lock is something that can
happen due to memory pressure, since these are VFS cache
pages. If a client reads something which is then removed
from the cache and goes to read it again, this will simply
generate a new read request.
This has a performance cost for that reader, but if anyone
is clearing the ldlm lru while actively doing I/O in that
namespace, then they cannot expect good performance.
In the case of many read locks on a single resource, this
improves cleanup time dramatically. In internal testing at
Cray with ~80,000 read locks on a single file, this improves
cleanup time from ~60 seconds to ~0.5 seconds. This also
slightly improves cleanup speed in the case of 1 or a few
read locks on a file.
Lustre-change: https://review.whamcloud.com/20785
Lustre-commit:
6a369b59f3729513dd8e81c4964dc6183287b601
Signed-off-by: Patrick Farrell <paf@cray.com>
Change-Id: I0c076b31ea474bb5f012373ed2033de3e447b62d
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Jinshan Xiong <jinshan.xiong@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29264
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Andriy Skulysh [Fri, 2 Sep 2016 09:28:24 +0000 (12:28 +0300)]
LU-8578 ldlm: ELC shouldn't wait on lock flush
commit
ad87adbff5148a74ac616dbc9bfa02a4e3814034
LU-5727 ldlm: revert the changes for lock canceling policy
but it removes the fix for LU-4300 when lru_resize is disabled.
Introduce ldlm_cancel_aged_no_wait_policy to be used by ELC.
Lustre-change: https://review.whamcloud.com/22286
Lustre-commit:
7ca60f338936465c534c2ac9a0ea467d276a7485
Change-Id: Ic74a6bce4a261dc96c8c0f6d8f7e20315def8c0e
Seagate-bug-id: MRP-3662
Signed-off-by: Andriy Skulysh <andriy.skulysh@seagate.com>
Reviewed-by: Vitaly Fertman <vitaly.fertman@seagate.com>
Reviewed-by: Patrick Farrell <paf@cray.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29263
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Wed, 23 Aug 2017 18:51:24 +0000 (11:51 -0700)]
LU-9469 ldiskfs: add additional attach_jinode call
In some execution paths jinode data structures are not
getting initialized. Add an extra init call to fix that.
Test-Parameters: clientdistro=sles12sp2 testlist=conf-sanity \
mdsdistro=sles12sp2 ossdistro=sles12sp2 testgroup=review-ldiskfs \
mdtfilesystemtype=ldiskfs ostfilesystemtype=ldiskfs
Lustre-change: https://review.whamcloud.com/28665
Lustre-commit:
84f690eee28f3b9123b89249c568dd6255a4a348
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I087eb06b9c5122be1cfd0aabbc04ea1db7ec765a
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Reviewed-by: Hongchao Zhang <hongchao.zhang@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28968
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Yang Sheng [Mon, 28 Aug 2017 19:30:13 +0000 (03:30 +0800)]
LU-9908 tests: force umount client in test 70e, 41b, and 105
In test_70e, import state may not update while
mds stopping. Since statfs will be invoked in sles12
before umounting, so umount with force flag to avoid
waitting a long time.
Add -f to stopall call in test-framework for the same reason,
to do umount with force flag.
Lustre-change: https://review.whamcloud.com/28767
Lustre-commit:
20787a89ad7dc99290c4d9cff8247b0a532e92b9
Signed-off-by: Yang Sheng <yang.sheng@intel.com>
Change-Id: I3d1e73b3501e98008ef18c05f7b5498d12cb46fb
Reviewed-by: Emoly Liu <emoly.liu@intel.com>
Reviewed-by: Jian Yu <jian.yu@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29108
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Emoly Liu [Fri, 22 Sep 2017 03:31:28 +0000 (11:31 +0800)]
LU-9929 nodemap: add default ACL unmapping handling
This patch adds default ACL unmapping code to mdt_getxattr
functions so that clients can get a correctly unmapped id.
Also, test_23b is added to sanity-sec.sh to verify this fix.
Lustre-change: https://review.whamcloud.com/29010
Lustre-commit:
62fee20556a4c90361bd28edb903dc77c9540133
Change-Id: I6562372c58ca9772f16f7d6b0b98b45ada87971a
Test-Parameters: testlist=sanity-sec
Signed-off-by: Emoly Liu <emoly.liu@intel.com>
Reviewed-by: Sebastien Buisson <sbuisson@ddn.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Stephan Thiell <sthiell@stanford.edu>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29369
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Thu, 5 Oct 2017 21:31:27 +0000 (14:31 -0700)]
LU-10088 kernel: kernel update RHEL6.9 [2.6.32-696.13.2.el6]
Update RHEL6.9 kernel to 2.6.32-696.13.2.el6
Test-Parameters: clientdistro=el6.9 mdsdistro=el6.9 \
ossdistro=el6.9 mdtfilesystemtype=ldiskfs \
ostfilesystemtype=ldiskfs testgroup=review-ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: Iedd8e4fc71fabfd7f779804ce546b5e3173d23d6
Reviewed-on: https://review.whamcloud.com/29362
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Reviewed-by: Minh Diep <minh.diep@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Nunez [Thu, 17 Aug 2017 20:04:14 +0000 (14:04 -0600)]
LU-9887 tests: ignore error sanity-lfsck test 9a,b
sanity-lfsck tests 9a and 9b are failing consistently on
checking that speed limiting LFSCK takes less time than the
user defined maximum speed. We should ignore these errors
for now and print the layout or namespace to help understand
this issue.
Test-Parameters: trivial testgroup=review-zfs-part-1
Test-Parameters: testgroup=review-dne-part-2
Lustre-change: https://review.whamcloud.com/28588
Lustre-commit:
6754b09335508ca4d977d10d1d05b5befd1a8aad
Signed-off-by: James Nunez <james.a.nunez@intel.com>
Change-Id: I64cac59edd456e6fd519961a4055130c8dbc8a4a
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29293
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Simmons [Thu, 31 Aug 2017 20:17:42 +0000 (16:17 -0400)]
LU-8541 ldlm: don't use jiffies as sysfs parameter
The ldlm sysfs file handles lru_max_age in jiffies which is wrong
since jiffies are not consistent across machine since HZ is
configurable at compile time. Talking to most users they thought
lru_max_age was in seconds which is incorrect. The best way to
fix this is to move lru_max_age to millisecs since most systems
lustre deals with sets HZ to 1000. To make it clear it is in
milliseconds print out lru_max_age with "ms". Since users tend
to think in seconds allow passing in seconds besides milliseconds
and internally converting them to nanaseconds. Since we have to
support milliseconds move to ktime_t since we can't use time64_t.
Unfortunately, this makes a relatively large patch, but I could
not find a way to split it up some more without breaking atomicity
of the change.
Lustre-change: https://review.whamcloud.com/28370
Lustre-commit:
800ffd4711863e1067a693f1283bccf4edddf2a2
Change-Id: I0b1814fd9d903767f62fe141d2c95845b75fb95a
Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29265
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Di Wang [Wed, 27 Sep 2017 09:10:26 +0000 (05:10 -0400)]
LU-9983 llog: skip non-exist log cancellation
Let's skip the record cancellation if the llog does
not exist at all, which usually happens when remote
log creation failed.
Signed-off-by: Di Wang <di.wang@intel.com>
Change-Id: I8b27978b725acf8dbffd1a743873a3854ee15efb
Reviewed-on: https://review.whamcloud.com/29238
Tested-by: Jenkins
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Elena Gryaznova [Wed, 13 Sep 2017 05:58:07 +0000 (22:58 -0700)]
LU-9980 tests: save specific facet in save_lustre_params()
In save_lustre_params(), while there are multiple server facets
having the same host, and the parameter has wildcard, duplicate
parameters with wrong facets will be saved.
This patch fixes the above issue by greping service name to save
the parameter with specific facet.
Test-Parameters: clientcount=4 osscount=2 mdscount=2 mdtcount=1 \
austeroptions=-R failover=true iscsi=1 testlist=replay-vbr
Lustre-change: https://review.whamcloud.com/28963
Lustre-commit:
7921d0d8db942057eb10042291d6d90448e5c197
Change-Id: Icba3fc532f4c67f02272c39e8e64d49325dad0e7
Signed-off-by: Elena Gryaznova <elena.gryaznova@seagate.com>
Signed-off-by: Jian Yu <jian.yu@intel.com>
Reviewed-by: James Nunez <james.a.nunez@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29147
Tested-by: Jenkins
Reviewed-by: Elena Gryaznova <c17455@cray.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bruno Faccini [Wed, 30 Aug 2017 09:37:03 +0000 (11:37 +0200)]
LU-9930 llite: only clear lli_sai if the setter
Previous to this patch, start_statahead_thread() was
unconditionnally clearing lli->lli_sai upon error, leading
to crash upon racy scenario where it has just been set in/by
another thread context.
Now, only clear lli_sai if current thread has set it.
Lustre-change: https://review.whamcloud.com/28794
Lustre-commit:
f4a0ebe28e88cbdd79061fad275cb9494fdba225
Signed-off-by: Bruno Faccini <bruno.faccini@intel.com>
Change-Id: I555febfad3494c9dd90eeb72d6dd9157428179ea
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29145
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Emoly Liu [Fri, 15 Sep 2017 07:56:11 +0000 (15:56 +0800)]
LU-9682 nodemap: delete nids range from nodemap correctly
In function nodemap_del_range(), we should check if the current
nodemap has the specified range before delete it from global
range tree.
Also, test_10b is added to sanity-sec.sh to verify this patch.
Lustre-change: https://review.whamcloud.com/28922
Lustre-commit:
62ca9b823524ca44d3344b2555754890abc55a3b
Change-Id: Ibab79056509d14d52f99b1ebe3319c301dbe45d9
Test-Parameters: testlist=sanity-sec
Signed-off-by: Emoly Liu <emoly.liu@intel.com>
Reviewed-by: Sebastien Buisson <sbuisson@ddn.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29138
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Minh Diep [Mon, 11 Sep 2017 17:02:19 +0000 (10:02 -0700)]
LU-9996 build: include MOFED lib
Test-Parameters: trivial
Lustre-change: https://review.whamcloud.com/#/c/29020/
Lustre-commit:
81ebf59c99b1e58d05d6d9af1ce645b09ecf3792
Change-Id: Ia1b5a97f59d5055311786934c9165a81f2af7cae
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/29118
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Simmons [Wed, 21 Jun 2017 21:37:04 +0000 (17:37 -0400)]
LU-9558 llite: user enhanced getattr functionality in newer kernels
Starting with the linux kernel 4.11 a new system call was added
to enhance the file info available. This new functionality has
changed the getattr functions in the linux kernel. This patch
only provides the most basic support for now.
Linux-commit:
a528d35e8bfcc521d7cb70aaf03e1bd296c8493f
Lustre-commit:
57730260e846cd5011469fe2edc667ef73ad3bad
Lustre-change: https://review.whamcloud.com/27715
Change-Id: Iee1b02bb94dab05a3197866af9eedd6f35cac7c5
Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-on: https://review.whamcloud.com/29006
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
James Simmons [Fri, 11 Aug 2017 18:50:52 +0000 (14:50 -0400)]
LU-9870 build: handle SNMP missing on build box
Currently the lustre spec file doesn't handle the case when SNMP
is missing. So even if the user does configure --disable-snmp our
rpm build process will ignore this and fail to build rpms. Pass
to the rpm build process the missing SNMP case.
Lustre-commit:
574451a4402df65d26d7af96d94a7bf0875c86af
Lustre-change: https://review.whamcloud.com/28494
Test-Parameters: trivial
Change-Id: Ia6dcfd31b50f4f67afe7a4545fe417c32df6e559
Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-by: Minh Diep <minh.diep@intel.com>
Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>
Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Reviewed-on: https://review.whamcloud.com/28987
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Wang Shilong [Mon, 3 Jul 2017 11:55:30 +0000 (19:55 +0800)]
LU-9733 obd: fix fsname parsing
Lustre support Lustre fsname started with numbers.
So here we should try fsname firstly, if it failed,
fall back to number parsing.
Lustre-change: https://review.whamcloud.com/27916
Lustre-commit:
cae71501680330a38c9bb16c25bf9c85dc0ec4e0
Change-Id: Idd98b9fdc8375729faa61f51251caa101035dd93
Signed-off-by: Wang Shilong <wshilong@ddn.com>
Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
Reviewed-by: Gu Zheng <gzheng@ddn.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28814
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Bob Glossman <bob.glossman@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Andrew Perepechko [Fri, 28 Apr 2017 17:20:06 +0000 (20:20 +0300)]
LU-9417 mdc: excessive memory consumption by the xattr cache
The refill operation of the xattr cache does not know the
reply size in advance, so it makes a guess based on
the maxeasize value returned by the MDS.
In practice, it allocates 16 KiB for the common case and
4 MiB for the large xattr case. However, a typical reply
is just a few hundred bytes. Even worse, RHEL6 has a very
bad vmalloc()/vfree() design with global locks.
If we follow the conservative approach, we can prepare a
single memory page for the reply. It is large enough for
any reasonable xattr set and, at the same time, it does
not require multiple page memory reclaim, which can be
costly.
If, for a specific file, the reply is larger than a single
page, the client is prepared to handle that and will fall back
to non-cached xattr code. Indeed, if this happens often and
xattrs are often used to store large values, it makes sense to
disable the xattr cache at all since it wasn't designed for
such [mis]use.
Lustre-change: https://review.whamcloud.com/26887
Lustre-commit:
94f080b395d6517e8da06a945bb10b0bfe69ad78
Change-Id: I98d97ffea5c83bccbc9f254717af8d2c0ac4d77f
Signed-off-by: Andrew Perepechko <andrew.perepechko@seagate.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Ben Evans <bevans@cray.com>
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28223
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
John L. Hammond [Tue, 3 Oct 2017 03:39:40 +0000 (22:39 -0500)]
New release 2.10.1.
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: Id69eb38fd2bb3987005fb0f4ec0a6da460dd1a19
John L. Hammond [Fri, 29 Sep 2017 20:57:00 +0000 (15:57 -0500)]
New tag 2.10.1-RC2.
Second release candidate for 2.10.1 release.
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: I849387cd0dac7a3897fd83ae250062bbcea5fe32
Bob Glossman [Wed, 27 Sep 2017 12:43:22 +0000 (05:43 -0700)]
LU-10037 kernel: kernel update RHEL6.9 [2.6.32-696.10.3.el6]
Update RHEL6.9 kernel to 2.6.32-696.10.3.el6
Test-Parameters: clientdistro=el6.9 mdsdistro=el6.9 \
ossdistro=el6.9 mdtfilesystemtype=ldiskfs \
ostfilesystemtype=ldiskfs testgroup=review-ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: Ic693e29056e099638ee49403b114f6872f7bc73f
Reviewed-on: https://review.whamcloud.com/29248
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Di Wang [Tue, 26 Sep 2017 00:25:07 +0000 (20:25 -0400)]
LU-9983 osp: align the OSP request size by 4k
Let's align the OSP request size by 4k, otherwise OUT
might get incorrect out requests.
Signed-off-by: Di Wang <di.wang@intel.com>
Change-Id: Id5c16b031dcb16d764c4e4f325f51b9ecf454533
Reviewed-on: https://review.whamcloud.com/29208
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
John L. Hammond [Fri, 15 Sep 2017 17:57:09 +0000 (12:57 -0500)]
New tag 2.10.1-RC1.
First release candidate for 2.10.1 release.
Signed-off-by: John L. Hammond <john.hammond@intel.com>
Change-Id: Ie2149519d4e272ca1a170f33871b28243ca897da
Bob Glossman [Fri, 15 Sep 2017 15:20:13 +0000 (11:20 -0400)]
LU-9978 kernel: kernel update RHEL7.4 [3.10.0-693.2.2.el7]
update RHEL 7.4 kernel to 3.10.0-693.2.2.el7
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: I2fe4e038f185f8d4acec74d9cc398da987bcad6b
Reviewed-on: https://review.whamcloud.com/29002
Tested-by: Jenkins
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Bob Glossman [Fri, 15 Sep 2017 15:11:42 +0000 (11:11 -0400)]
LU-9816 kernel: kernel upgrade RHEL7.4 [3.10.0-693.el7]
With this mod we switch our supported el7 version to RHEL 7.4
Lustre-change: https://review.whamcloud.com/#/c/28301/
Lustre-commit:
b2a39555d1bd4a75017ee6ca2a9a6920a30bafa8
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: Ib0bcb3547fcf220e1b4665229930c6ff28c6906c
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28532
Tested-by: Jenkins
Tested-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
James Simmons [Thu, 14 Sep 2017 01:21:22 +0000 (21:21 -0400)]
LU-9767 utils: validate filesystem name for mkfs.lustre
In an earlier LU-6401 patch various user land functions
used to validate poolnames and file system names were
removed. The checks instead were enforced on the kernel
side to ensure any possible user land software directly
interfacing to the kernel wouldn't be able to break
things badly. For the case of formating the backend
file system no kernel interaction doesn't happen until
it tries to mount the MDT/OST/MGT which is very late
in the process. So for this case lets add back the
file system name verification to mkfs.lustre to warn
users long before they try to mount anything.
Secondly we remove the verify_poolname() in lfs.c since
it really doesn't do much.
Test-Parameters: trivial
Lustre-commit:
28216a73f4c0b19ef45e3ec2d6949801f6b9f828
Lustre-change: https://review.whamcloud.com/28070
Change-Id: If094644e56a70b6dd8e6b0378adc8736911aeef1
Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-on: https://review.whamcloud.com/28070
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Fan Yong <fan.yong@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
Reviewed-on: https://review.whamcloud.com/28996
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Bob Glossman [Tue, 12 Sep 2017 16:36:41 +0000 (09:36 -0700)]
LU-9979 kernel: kernel update RHEL6.9 [2.6.32-696.10.2.el6]
Update RHEL6.9 kernel to 2.6.32-696.10.2.el6
Test-Parameters: clientdistro=el6.9 mdsdistro=el6.9 \
ossdistro=el6.9 mdtfilesystemtype=ldiskfs \
ostfilesystemtype=ldiskfs testgroup=review-ldiskfs
Signed-off-by: Bob Glossman <bob.glossman@intel.com>
Change-Id: Ie86a84fda1ec391c4e0b9ab18a82d4a5b0bd25d1
Reviewed-on: https://review.whamcloud.com/28969
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Tested-by: Jenkins
Reviewed-by: Minh Diep <minh.diep@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Nathaniel Clark [Mon, 11 Sep 2017 14:14:18 +0000 (10:14 -0400)]
LU-9960 osd-zfs: don't auto-upgrade quota
To preserve the ability to down-grade from 0.7.x to 0.6.x,
don't auto-upgrade quotas.
Print warning if quotas haven't been upgraded when mouting with 0.7.0.
Do check based on zpool feature in sanity-quota instead of just
version.
Lustre-change: https://review.whamcloud.com/#/c/28924/
Lustre-commit:
0bbef0afc16081e1af3529642436864954a73e3c
Signed-off-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
Change-Id: I2b0dcba3a230c9b2dec3d07d1b4ca6f1a1717d47
Signed-off-by: Minh Diep <minh.diep@intel.com>
Reviewed-on: https://review.whamcloud.com/28954
Tested-by: Jenkins
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: John L. Hammond <john.hammond@intel.com>