- 03 Nov, 2020 7 commits
-
-
Oleg Drokin authored
When we are trying to grant a lock and met an AST error, rerunning the policy is pointless since it cannot grant a potentially now eligible lock and our lock is already in all the queues, just be like all the other handlers for ERESTART return and run a full resource reprocess instead. Lustre-change: https://review.whamcloud.com/#/c/39598/ Lustre-commit: 24e3b539 Change-Id: I3edb37bf084b2e26ba03cf2079d3358779c84b6e Signed-off-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40412 Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Patrick Farrell authored
The search_itree and search_queue functions should both return either a pointer to a found lock or NULL. Currently, search_itree just returns the contents of data->lmd_lock, whether or not a lock was found. search_queue will do the same under certain cirumstances. Zero lmd_lock in both search_* functions, and also stop searching in search_itree once a lock is found. cray-bug-id: LUS-6783 Signed-off-by:
Patrick Farrell <paf@cray.com> Change-Id: Ie231166756e60c228370f8f1a019ccfe14dfda6a Reviewed-on: https://review.whamcloud.com/33754 Tested-by: Jenkins Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
James Simmons <uja.ornl@yahoo.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40399 Tested-by:
jenkins <devops@whamcloud.com>
-
Mikhail Pershin authored
The check in ll_dom_finish_open() for data end shouldn't use i_size for comparision because it may be not updated yet with just returned data from server. Use size value in mdt_body from reply for that check. Lustre-change: https://review.whamcloud.com/33895 Lustre-commit: 7b9fd576 Signed-off-by:
Mikhail Pershin <mpershin@whamcloud.com> Change-Id: I1104fbbb0eb4633869b9bf2d1803ac3e84e3853d Reviewed-on: https://review.whamcloud.com/40301 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Vladimir Saveliev authored
ll_dom_lock_cancel() should zero kms attribute similar to mdc_ldlm_blocking_ast0(). In order to avoid code duplication between mdc_ldlm_blocking_ast0() and ll_dom_lock_cancel() - add new cl_object_operations method - coo_object_flush() to reach mdc's blocking ast from llite level. Tests illustrating the issue are added. Lustre-change: https://review.whamcloud.com/34858 Lustre-commit: 707bab62 LU-12704 lov: check all entries in lov_flush_composite Check all layout entries for DOM layout and exit with -ENODATA if no one exists. Caller consider that as valid case due to layout change. Define llo_flush methods for all layouts as required by lov_dispatch(). Patch cleans up also cl_dom_size field in cl_layout which was used in previous ll_dom_lock_cancel() implementation Run lov_flush_composite under down_read lov->lo_type_guard to avoid race with layout change. Lustre-change: https://review.whamcloud.com/36368 Lustre-commit: 44460570 Signed-off-by:
Mikhail Pershin <mpershin@whamcloud.com> Change-Id: I2b100ead6d420dbf561bc61be973d64dad317214 Reviewed-on: https://review.whamcloud.com/40296 Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Oleg Drokin authored
in ldlm_handle_cp_callback the while loop is clearly supposed to be limited by the "to" value of 1 second, but is not. Seems to have been broken by all the Solaris porting in HEAD all the way back in 2008. Restore the to assignment to make it not hang indefinitely. Lustre-change: https://review.whamcloud.com/#/c/40375/ Lusre-commit: 5da99051 Change-Id: I449bfd7f585ab7db475fb3fd4cbbd876126ff789 Fixes: adde80ff ("Land b_head_libcfs onto HEAD") Signed-off-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40411 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Hongchao Zhang authored
In lov_cleanup, the check of each OSC is protected by lov_tgt_getrefs, which will increment the "lov_refcount", so the "lov_refcount" shouldn't be checked inside because it is always larger than 0. Change-Id: I21423d4345190b3e02eb00734c127e35cbc9b1af Signed-off-by:
Hongchao Zhang <hongchao@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39702 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by:
Bobi Jam <bobijam@hotmail.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40452
-
Alex Zhuravlev authored
to avoid quota misaccounting. Lustre-change: https://review.whamcloud.com/38842 Lustre-commit: 7805b45f Test-Parameters: fstype=ldiskfs Signed-off-by:
Alex Zhuravlev <bzzz@whamcloud.com> Change-Id: I5a02e6e7de71821a10704ac3516ee087998c9c21 Reviewed-by:
Hongchao Zhang <hongchao@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40403 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
- 29 Oct, 2020 7 commits
-
-
Jian Yu authored
Update RHEL7.8 kernel to 3.10.0-1127.19.1.el7. Test-Parameters: trivial clientdistro=el7.8 serverdistro=el7.8 Change-Id: I7d0cbdb32b33f2f8121fec707924c35fa086f965 Signed-off-by:
Jian Yu <yujian@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39993 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Yang Sheng <ys@whamcloud.com> Reviewed-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Amir Shehata authored
There are scenarios where there could be a discrepancy between cached peer information and reality. In these cases what could end-up happening is incomplete interface information might be cached because one side determined that the peer didn't require a PUSH. This will lead to undesired MR behavior, where not all the interfaces are used for a period of time. Therefore, it is safer to always force a full discovery cycle: GET/PUSH to ensure both sides are up-to-date. In the NMR case, when discovery is turned off, make sure to flag discovery as complete to avoid stalling the state machine. Signed-off-by:
Amir Shehata <ashehata@whamcloud.com> Change-Id: Ie49ad11e8ff874206baa268a4ef2d58ebb536ed5 Lustre-change: https://review.whamcloud.com/38322 Reviewed-by:
Chris Horn <chris.horn@hpe.com> Reviewed-by:
Serguei Smirnov <ssmirnov@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39577 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Cyril Bordage <cbordage@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Mikhail Pershin authored
Commit cf78502e checks the new state for IMP_CLOSED value instead of import current state so instead of keeping import closed it prevents import state from being set to IMP_CLOSE Patch restores original check to keep import closed by checking its current state Fixes: cf78502e ("LU-10756 ptlrpc: change IMPORT_SET_* macros into real functions") Signed-off-by:
Mikhail Pershin <mpershin@whamcloud.com> Change-Id: I7df2798f09ce7023381c03957adf530da4149c2d Reviewed-on: https://review.whamcloud.com/37405 Reviewed-by:
James Simmons <jsimmons@infradead.org> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> (cherry picked from commit 43dddbd0) Reviewed-on: https://review.whamcloud.com/38621
-
Hongchao Zhang authored
During target recovery, the recovery timer should be kept to be armed to ensure the recovery doesn't take too long time, there should be some problem if the deadline of the recovery timer is passed and the recovery is not completed yet, the recovery should be aborted in this case. Lustre-commit: 87443d9c Lustre-change: https://review.whamcloud.com/38277 Change-Id: Id44f2a2d1a3183ad8dd13f4d34392713c55a2cb3 Signed-off-by:
Hongchao Zhang <hongchao@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40303 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Mike Pershin <mpershin@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
John L. Hammond authored
In lod_layout_convert() zero out lcm and lcme before constructing the converted layout. Lustre-commit: 6f2a1c91 Lustre-change: https://review.whamcloud.com/40153 Signed-off-by:
John L. Hammond <jhammond@whamcloud.com> Change-Id: I40f96d51cb63816a9bfc34217f02ff7c450de974 Reviewed-on: https://review.whamcloud.com/40306 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Lai Siyao authored
Object with zero FID is used in stripe allocation, and it's meaningless to initialize such object via lu_object_find_at(), return error early to avoid assertion in lu_object_put(). Lustre-commit: 22ea9767 Lustre-change: https://review.whamcloud.com/39792 Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Change-Id: Ia1bda3d01ff7552e94f31a9c928868652937d559 Reviewed-on: https://review.whamcloud.com/40304 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Stephane Thiell <sthiell@stanford.edu> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Alex Zhuravlev <bzzz@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Serguei Smirnov authored
Release ln_api_mutex during LNet shutdown while waiting for zombie LNI to allow other threads to read the LNet state updated by the shutdown and fall through, avoiding the deadlock Lustre-change: https://review.whamcloud.com/39933 Lustre-commit: e0c44564 Signed-off-by:
Serguei Smirnov <ssmirnov@whamcloud.com> Change-Id: If0886f1bc4412dd9cacb08a0f06fa69aeeed1c5b Reviewed-on: https://review.whamcloud.com/40171 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Chris Horn <chris.horn@hpe.com> Reviewed-by:
Olaf Faaland-LLNL <faaland1@llnl.gov> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
- 22 Oct, 2020 8 commits
-
-
Serguei Smirnov authored
This is a fix for the issue with LNet lock-up while waiting for routers to become active with check_routers_before_use option. Release ln_api_mutex while waiting to allow incoming connections to be handled. Signed-off-by:
Serguei Smirnov <ssmirnov@whamcloud.com> Change-Id: I63b1d1ce5ee2b27a3bd2cea78713fc6fc7502cf7 Reviewed-on: https://review.whamcloud.com/40172 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Olaf Faaland-LLNL <faaland1@llnl.gov> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Amir Shehata <ashehata@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Andriy Skulysh authored
mdt_remote_object_lock_try() drops object reference in case of an error but if the request was sent to a server it is decreased again via failed_lock_cleanup() Add ldlm_created_callback. It is called after lock creation, so we can safely add a reference to l_ast_data and drop it only in BL AST handler. Lustre-commit: b2368774 Lustre-change: https://review.whamcloud.com/34181 Cray-bug-id: LUS-7013 Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Signed-off-by:
Andriy Skulysh <c17819@cray.com> Reviewed-by:
Alexandr Boyko <c17825@cray.com> Reviewed-by:
Vitaly Fertman <c17818@cray.com> Reviewed-by:
Mike Pershin <mpershin@whamcloud.com> Reviewed-by:
Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Change-Id: I49c946278f379390634642370d15c7fe89441d86 Reviewed-on: https://review.whamcloud.com/39976 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Vitaly Fertman authored
The blocking cb may be triggered in parallel and the convert logic of the DOM lock must be ready that the cancel_bits could be already zeroed by the first executor. As there may be several blocking cb parallel executors and several conversion callers, each requesting for different inode bits, setup the following logic: - the lock keeps the aggregated set of bits requested for cancelling by different parties, where 0 means the whole lock is to be cancelled, and where the CBPENDING flag means there is a canceling job pending; - once completed, the cancel_bits are zeroed and the CBPENDING flag is dropped, meaning the next request will be a part of the next job; - once a local lock is converted, its state is changed appropriately and no cleanup is left for the interpret time as the lock is ready for the next usage; - as the lock is unlocked in a process of conversion and more bits may appear, check it and repeat appropriately; - let just 1 conversion executor to work at a time, others are waiting similar to ldlm_cli_cancel(); - there are others who may want to cancel unused locks (cancel_lru, cancel_resource_local), consider CANCELING as a request to cancel the full lock independently of the cancel_bits; Some cleanups are done: - move the cache drop logic to the CANCELING part of the blocking cb from the BLOCKING one; - remove the convert RPC interpret, as the lock cleanups are already done in advance; the convert RPC is re-sendable and an error means there is a serioes net problem; Test-Parameters: testlist=racer,racer,racer Signed-off-by:
Vitaly Fertman <c17818@cray.com> Change-Id: I901de34241704ed801152f071cb7f610fe6f4bfe Signed-off-by:
Mikhail Pershin <mpershin@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39854 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
James Simmons <jsimmons@infradead.org> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Vitaly Fertman <vitaly.fertman@hpe.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Jian Yu authored
This patch makes changes to support new RHEL 7.9 release for Lustre server (kernel 3.10.0-1160.2.1.el7). Test-Parameters: trivial clientdistro=el7.9 serverdistro=el7.9 Change-Id: I7653091f2bd6a579447edb12045984d2829a8235 Signed-off-by:
Jian Yu <yujian@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40224 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Yang Sheng <ys@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Lai Siyao authored
It's a waste of time to call osd_add_oi_cache() in osd_it_ea_rec(), because each dirent read will override it. Lustre-change: https://review.whamcloud.com/39782 Lustre-commit: bc593463 Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Change-Id: Iec701bf66153fdf2ba7a3f3b89565381215abf33 Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Stephane Thiell <sthiell@stanford.edu> Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40135 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Minh Diep authored
Adding Ubuntu libtool-bin requirement Lustre-change: https://review.whamcloud.com/36471 Lustre-commit: dbce727a ) Test-Parameters: trivial clientdistro=ubuntu1804 testlist=sanity-hsm Change-Id: I04cfffc880259e4cf1c2cba142eddd47a95a736e Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-by:
James Simmons <jsimmons@infradead.org> Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/38822 Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
James Nunez <jnunez@whamcloud.com>
-
Andrew Perepechko authored
Due to a bug in the code, libcfs will crash if the number of online cpus does not divide by the number of cpu partitions. Based on the checks in cfs_cpt_table_create(), it appears that the original intent was to push the remaining cpus into the initial partitions. So let's do that properly. Lustre-commit: e33e3da5 Lustre-change: https://review.whamcloud.com/34991 Change-Id: I3c5e2aa1fdfca4c07e7afce143c984973373f009 Cray-bug-id: LUS-6455 Signed-off-by:
Andrew Perepechko <c17827@cray.com> Reviewed-by:
Alexander Boyko <c17825@cray.com> Reviewed-by:
Alexander Zarochentsev <c17826@cray.com> Reviewed-by:
Gu Zheng <gzheng@ddn.com> Reviewed-by:
Alexandr Boyko <c17825@cray.com> Reviewed-on: https://review.whamcloud.com/37994 Reviewed-by:
Serguei Smirnov <ssmirnov@whamcloud.com> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
James Nunez authored
In the setmodopts() function in functions.sh, the '_var' variable is set and used. There is one use of the variable 'var' which should be '_var'. Change the use of 'var' to '_var'. Reviewed-on: https://review.whamcloud.com/39891 (cherry picked from commit ff29ed8f ) Test-Parameters: trivial Test-Parameters: testlist=conf-sanity env=ONLY=53 clientdistro=ubuntu1804 fstype=ldiskfs Test-Parameters: testlist=conf-sanity env=ONLY=53 clientdistro=el7.8 fstype=ldiskfs Signed-off-by:
James Nunez <jnunez@whamcloud.com> Change-Id: If524be1f0b4b2170a514a558256a5308c9a5e586 Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
John L. Hammond <jhammond@whamcloud.com> Reviewed-by:
Vikentsi Lapa <vlapa@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39985 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
- 19 Oct, 2020 1 commit
-
-
Jian Yu authored
This patch makes changes to support new RHEL 7.9 release for Lustre client. Test-Parameters: trivial clientdistro=el7.9 Change-Id: I7a2846de48a6710d6d720d6ccc3176dba4afc6bb Signed-off-by:
Jian Yu <yujian@whamcloud.com> Reviewed-on: https://review.whamcloud.com/40177 Reviewed-by:
Yang Sheng <ys@whamcloud.com> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com>
-
- 06 Oct, 2020 2 commits
-
-
Mr NeilBrown authored
This arg is always '0', so remove it. Consequently, OBD_BRW_NOCACHE is never set, and cl_dirty_transit and obd_dirty_transit_pages are never non-zero, so they can be removed as well. Lustre-change: https://review.whamcloud.com/36319 Lustre-commit: 524deb6f Patch also includes changes for atomic ops optimization to keep in sync with master branch: Lustre-change: https://review.whamcloud.com/33859 Lustre-commit: 8b364fbd Signed-off-by:
Mikhail Pershin <mpershin@whamcloud.com> Change-Id: Ia047affc33fb9277e6c28a8f6d7d088c385b51a8 Reviewed-on: https://review.whamcloud.com/39518 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Olaf Faaland-LLNL <faaland1@llnl.gov> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Hongchao Zhang authored
Abort the reading update LLOG fromt other MDTs when the recovery is aborted, then the recovery process can be aborted in time. This patch also adds watchdog for the process of the replay request to detect possible stale process. Lustre-change: https://review.whamcloud.com/38746 Lustre-commit: 0496cdf2 Change-Id: Ie2de041360c9eba95ef9bfd14b00ac2709e6eace Signed-off-by:
Hongchao Zhang <hongchao@whamcloud.com> Reviewed-on: https://review.whamcloud.com/38746 Reviewed-by:
Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39284 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
- 19 Sep, 2020 8 commits
-
-
Lai Siyao authored
Pack parent FID in getattr request if OBD_CONNECT2_GETATTR_PFID is enabled, otherwise fill it with target FID for backward compatibility. Lustre-change: https://review.whamcloud.com/39290 Lustre-commit: 5f2c44bf Fixes: f9a2da63 ("LU-13437 mdt: don't fetch LOOKUP lock for remot...") Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by:
Neil Brown <neilb@suse.de> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Change-Id: I91bace23e67b548feb92fd885fb5e64e92c96408 Reviewed-on: https://review.whamcloud.com/39771 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Lai Siyao authored
Add OBD_CONNECT2_GETATTR_PFID connect flag to pack parent FID in getattr request, which will be used to check whether target is remote object, if so, don't take LOOKUP lock, otherwise client may see stale directory entries. Lustre-change: https://review.whamcloud.com/39289 Lustre-commit: f384a873 Test-parameters: trivial Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Neil Brown <neilb@suse.de> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Change-Id: Ibdf880934456f255f83cd4bac9d61ab5e1ed7330 Reviewed-on: https://review.whamcloud.com/39770 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Lai Siyao authored
In rename, all objects but target may be remote, so to check whether source is remote object on source parent, we need to compare which MDTs they are located if both are remote. Add a helper function mdt_rename_source_lock() to handle all possible combinations. If target parent is remote, take remote LOOKUP for target on where target parent is. Add sanityn.sh 81c. Lustre-change: https://review.whamcloud.com/38181 Lustre-commit: 4918fe40 Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I2c134970d6abc8761528d01950b23495292cdf93 Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Mike Pershin <mpershin@whamcloud.com> Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39601 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Lai Siyao authored
Pack parent FID in getattr by FID, which will be used to check whether child is remote object on parent. The helper function is called mdt_is_remote_object(). NB, directory shard is not treated as remote object, because if so, client needs to revalidate shards when dir is accessed, which will hurt performance much. For getattr by FID, if object is remote file on parent, don't fetch LOOKUP lock, otherwise client may see stale dir entries. Lustre-change: https://review.whamcloud.com/38561 Lustre-commit: f9a2da63 Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Yingjin Qian <qian@ddn.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Change-Id: I37b36983735eca63da37f190456b5cc1b861b29e Reviewed-on: https://review.whamcloud.com/39769 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Lai Siyao authored
Striped directory layout may be broken, if some stripe FID is insane, return -ENODEV. Lustre-change: https://review.whamcloud.com/38560 Lustre-commit: 698a496a Signed-off-by:
Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I7ed8c7c561e34625e2cb29bfd14bc0ecf3fce46c Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Hongchao Zhang <hongchao@whamcloud.com> Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39600 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Amir Shehata authored
When discovering a remote peer (not on the same network) a GET is sent to the peer to retrieve the peer's interfaces. This is followed by a PUSH, if discovery is on, to push the node's interfaces However, if both node and peer have multiple interfaces it is likely that the GET and the PUSH will originate on different interfaces. When the peer receives the PUSH it will not be able to connect the two NIDs and will not be able to consolidate the node's NIDs. This issue is specific for remote peers because at the time the push handler is invoked the remote lpni has not been created yet. lnet_parse() creates the lpni of the gateway. Similar to the strategy already in place of using the same source NID for all the messages of an RPC, discovery should use the same source NID for both the GET and PUSH. This patch stores the source NID interfaces the GET was sent on and uses it for the PUSH. Signed-off-by:
Amir Shehata <ashehata@whamcloud.com> Change-Id: I5a13ab7799b2ddc47714202bcbed786b0d3940b7 Reviewed-on: https://review.whamcloud.com/38320 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Chris Horn <chris.horn@hpe.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Serguei Smirnov <ssmirnov@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39576
-
Andreas Dilger authored
If doing a client-only build, do not set the FS_REQUIRES_DEV flag for the 'lustre' filesystem type. This is only needed on the server, but the filesystem type declaration is shared between both. In master, this was fixed by declaring a new 'lustre_tgt' filesystem type and using that for server filesystem mounts. However, for 2.12 this is overkill, and it is possible to get a 95% fix by dropping the FS_REQUIRES_DEV flag for the common case of client-only builds. Test-Parameters: trivial Signed-off-by:
Andreas Dilger <adilger@dilger.ca> Change-Id: Iab2e78515aba018e2a6bceb324ad1b8a313ebbe5 Reviewed-on: https://review.whamcloud.com/39674 Reviewed-by:
Jian Yu <yujian@whamcloud.com> Reviewed-by:
James Simmons <jsimmons@infradead.org> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Li Dongyang authored
Add ext4-no-max-dir-size-limit-for-iam-objects.patch to introduce new inode state EXT4_STATE_IAM and use it to mark IAM objects. Lustre-change: https://review.whamcloud.com/39823 Lustre-commit: 03e6db50 Change-Id: I3bcc5435ea07edb9fa265dcd8e3261d849495f00 Signed-off-by:
Li Dongyang <dongyangli@ddn.com> Reviewed-by:
Neil Brown <neilb@suse.de> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
James Simmons <jsimmons@infradead.org> Reviewed-on: https://review.whamcloud.com/39882 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
- 15 Sep, 2020 3 commits
-
-
Mikhail Pershin authored
Add check in the osc_init_grant() to prevent possible underflow of cl_avail_grant and report error if it happens Lustre-change: https://review.whamcloud.com/#/c/39827 Lustre-commit: e05ccafd Signed-off-by:
Mikhail Pershin <mpershin@whamcloud.com> Change-Id: Idcd25ed427c23735e1cdc70359bace43b5b9d886 Reviewed-on: https://review.whamcloud.com/39380 Tested-by:
jenkins <devops@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Vladimir Saveliev authored
New IO engine implementation lost consuming grants by direct I/O writes. That led to early emergence of out of space condition during direct I/O. The below illustrates the problem: # OSTSIZE=100000 sh llmount.sh # dd if=/dev/zero of=/mnt/lustre/file bs=4k count=100 oflag=direct dd: error writing ‘/mnt/lustre/file’: No space left on device Consume grants for direct I/O. Try to consume grants in osc_queue_sync_pages() when it is called for pages which are being writted in direct i/o. Tests are added to verify grant consumption in buffered and direct i/o and to verify direct i/o overwrite when ost is full. The overwrite test is for ldiskfs only as zfs is unable to overwrite when it is full. Lustre-change: https://review.whamcloud.com/35896 Lustre-commit: 05f326a7 Fixes: 9fe4b52a ("LU-1030 osc: new IO engine implementation") Signed-off-by:
Vladimir Saveliev <c17830@cray.com> Change-Id: I9a199452c564e8e8ad02f79231e8481166f3666e Cray-bug-id: LUS-7036 Reviewed-on: https://review.whamcloud.com/39386 Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Sergey Gorenko authored
A new argument was added to rdma_reject() in MOFED 5.1 and Linux 5.8. Add a cofigure check and support both versions of rdma_reject(). Lustre-commit: 956deb0f Lustre-change: https://review.whamcloud.com/39323 Test-Parameters: trivial Signed-off-by:
Sergey Gorenko <sergeygo@mellanox.com> Change-Id: I2b28991f335658b651b21a09899b7b17ab2a9d57 Reviewed-on: https://review.whamcloud.com/39781 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
- 01 Sep, 2020 4 commits
-
-
Shaun Tancheff authored
Without the hint from selinux_is_enabled() to determine if selinux is running at boot the performance fix from LU-549 to skip handling of selinux xattrs cannot be correctly handled. The correct path is to act is if selinux is enabled. This fixes a bug introduced by LU-12355 that now exists in RHEL 8.2 kernels where clients have enabled selinux. Lustre-change: https://review.whamcloud.com/39569 Lustre-commit: 994287bd Fixes: 39e5bfa7 ("LU-12355 llite: include file linux/selinux.h removed") Test-Parameters: clientdistro=el8.2 serverdistro=el8.2 clientselinux testlist=sanity-selinux Test-Parameters: clientdistro=el8.1 serverdistro=el8.1 clientselinux testlist=sanity-selinux Signed-off-by:
Shaun Tancheff <shaun.tancheff@hpe.com> Change-Id: I6fb5ed9ecdb79545225b5586b90509eb157a355b Reviewed-by:
Sebastien Buisson <sbuisson@ddn.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39671 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com>
-
Sebastien Buisson authored
Use 'stat' command instead of 'ls -lZ' to retrieve SELinux security context, to make it more portable. Lustre-change: https://review.whamcloud.com/38648 Lustre-commit: ca09fda1 Test-Parameters: trivial clientselinux testlist=sanity-selinux mdtcount=2 clientcount=2 Signed-off-by:
Sebastien Buisson <sbuisson@ddn.com> Change-Id: I61bc0efb1e8ae0427d05827e2933eb0b848fb442 Reviewed-on: https://review.whamcloud.com/39713 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Andreas Dilger <adilger@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-
Chris Horn authored
Reconcile the logic for updating the multi-rail flag of a peer when processing a discovery PUSH with the logic used when processing a discovery REPLY. Cray-bug-id: LUS-8516 Signed-off-by:
Chris Horn <hornc@cray.com> Change-Id: Idfb4c3729822d03b71f9440ac66176ae6b886022 Reviewed-on: https://review.whamcloud.com/37674 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Shaun Tancheff <shaun.tancheff@hpe.com> Reviewed-by:
Serguei Smirnov <ssmirnov@whamcloud.com> Reviewed-by:
Stephen Champion <stephen.champion@hpe.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39575 Reviewed-by:
Chris Horn <chris.horn@hpe.com>
-
Minh Diep authored
Installing libsnmp-dev will pull in the correct libsnmpXX. By depending on the libsnmp-dev we can install on ubuntu 20.04 which is libsnmp35 Lustre-change: https://review.whamcloud.com/39506 Lustre-commit: af2f7763 Change-Id: Ib921ac35e06149ba88fa8e39b9a0980deb94acf2 Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-by:
James Simmons <jsimmons@infradead.org> Reviewed-by:
Shaun Tancheff <shaun.tancheff@hpe.com> Reviewed-by:
Sebastien Buisson <sbuisson@ddn.com> Signed-off-by:
Minh Diep <mdiep@whamcloud.com> Reviewed-on: https://review.whamcloud.com/39679 Tested-by:
jenkins <devops@whamcloud.com> Tested-by:
Maloo <maloo@whamcloud.com> Reviewed-by:
Oleg Drokin <green@whamcloud.com>
-