Whamcloud - gitweb
LU-8535 lod: RR policy should not allocate on same ost 90/22090/3
authorRahul Deshmkuh <rahul.deshmukh@seagate.com>
Wed, 24 Aug 2016 05:28:21 +0000 (10:58 +0530)
committerOleg Drokin <oleg.drokin@intel.com>
Mon, 26 Sep 2016 15:20:18 +0000 (15:20 +0000)
commitbc3f670eb8ba2f96ae7e83e1a2c3a061c4be21a8
tree5f7496ca666048311987bcf72e9973a6aa2c0e13
parentc782be8d0ecc3d8ac3c418252ecae18b9de345a5
LU-8535 lod: RR policy should not allocate on same ost

Problem: With Round Robin (RR) policy we should not allowed
to create objects on same ost but currently it is possible.

Solution: lod_check_and_reserve_ost() skips a check for
already used OST when speed=0 i.e. at the first round of
object allocation. Enabling the check unconditionally to
fix above mention problem.

This patch contains both re-producer and the fix.

Signed-off-by: Rahul Deshmukh <rahul.deshmukh@seagate.com>
Signed-off-by: Alexander Zarochentsev <alexander.zarochentsev@seagate.com>
Seagate-bug-id: MRP-3480
Change-Id: I80895f8d7cc0a146a098869842bbc256152e6c2e
Reviewed-on: http://review.whamcloud.com/22090
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
lustre/include/obd_support.h
lustre/lod/lod_qos.c
lustre/tests/sanityn.sh [changed mode: 0755->0644]