Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
LU-4345 osp: store valid bits in setattr record
Backport a series of 4 patches to resolve the random ID on OST objects problem. 1: store valid bits in setattr record (LU-4345) We'd store LA_UID/LA_GID bit along with the UID/GID in the setattr llog record, otherwise, osp could set a random uid/gid to the OST object. Lustre-commit: 80f90fc Lustre-change: http://review.whamcloud.com/10223 2: Correctly check for invalid setattr record (LU-5188) Patch for LU-4345 (commit 80f90fc ) has a correct comment about lsr_valid member being either 0 or having UID and GID fields set, but the check has a typo causing it to check for lsr_valid to be both 0 and have the bits set which is impossible. The osp_sync_new_setattr_job() should return 0 for invalid record, so that sync thread can continue processing on other records. Lustre-commit: 79dd530 Lustre-change: http://review.whamcloud.com/10706 3: don't skip attr_set for osp objects (LU-5296) The lsr_valid handling in osp_sync_add_rec() was got a problem in commit 80f90fc because it stored all of the passed attr flags in struct llog_setattr64_rec, even though there are only fields for storing the UID and GID. Since the time stamps do not need to be propagated to the OSTs (the MDT values are good enough), this is not a problem. Also, osp_sync_add_rec stored LA_UID/LA_GID flags on disk, but they are not part of lustre_idl.h or lustre_disk.h and are not guaranteed to be constant over time. Instead, use the flags OBD_MD_FLUID/OBD_MD_FLGID that are in lustre_idl.h. Lustre-commit: 2d5a5e8 Lustre-change: http://review.whamcloud.com/10989 4: return 1 if osp_sync_xxx_job issue RPC (LU-5188) Return 1 if osp_sync_new_xxx_job() issue RPC, so sp_sync_process_record() can decrease opd_syn_rpc_in_flight and opd_syn_rpc_in_progress correctly if RPC is not being sent, otherwise the opd_sync_thread will not be stopped, caused LBUG (see LU-5244) Lustre-commit: 73f47cd Lustre-change: http://review.whamcloud.com/10828 Test-Parameters: alwaysuploadlogs \ envdefinitions=SLOW=yes,ENABLE_QUOTA=yes,ONLY=34 \ ossjob=lustre-b2_4 mdsjob=lustre-b2_4 ossbuildno=73 mdsbuildno=73 \ testlist=sanity-quota Signed-off-by: Niu Yawei <yawei.niu@intel.com> Change-Id: Ie231465b274627561e7eb58f30b868472751bd71 Signed-off-by: Jian Yu <jian.yu@intel.com> Reviewed-on: http://review.whamcloud.com/11435 Tested-by: Jenkins Tested-by: Maloo <hpdd-maloo@intel.com> Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
- Loading branch information
Showing
7 changed files
with
61 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters