Whamcloud - gitweb
LU-12462 osc: Do not assert for first extent 76/36876/2
authorPatrick Farrell <pfarrell@whamcloud.com>
Tue, 16 Jul 2019 16:28:25 +0000 (12:28 -0400)
committerOleg Drokin <green@whamcloud.com>
Fri, 20 Dec 2019 06:44:51 +0000 (06:44 +0000)
In the discard case, the OSC fsync/writeback code asserts
that each OSC extent is fully covered by the fsync request.

This is not valid for the DOM case, because OSC extent
alignment requirements can create OSC extents which start
before the OST region of the layout (ie, they cross in to
the DOM region).  This is OK because the layout prevents
them from ever being used for i/o, but this same behavior
means that the OSC fsync start/end is aligned with the
layout, and so does not necessarily cover that first
extent.

The simplest solution is just to not assert on the first
extent.  (There is no way at the OSC layer to recognize the
DOM case.)

Lustre-change: https://review.whamcloud.com/35525
Lustre-commit: 092ecd66127eade284550b83192fa004ff55501b

Signed-off-by: Patrick Farrell <pfarrell@whamcloud.com>
Change-Id: If66f8d81fb9dd4546a5647a10f6ca551e2cf98e3
Reviewed-by: Mike Pershin <mpershin@whamcloud.com>
Reviewed-by: Andriy Skulysh <c17819@cray.com>
Signed-off-by: Minh Diep <mdiep@whamcloud.com>
Reviewed-on: https://review.whamcloud.com/36876
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
lustre/osc/osc_cache.c

index 418f912..7cf8934 100644 (file)
@@ -3057,9 +3057,16 @@ int osc_cache_writeback_range(const struct lu_env *env, struct osc_object *obj,
                                unplug = true;
                        } else {
                                /* the only discarder is lock cancelling, so
-                                * [start, end] must contain this extent */
-                               EASSERT(ext->oe_start >= start &&
-                                       ext->oe_end <= end, ext);
+                                * [start, end] must contain this extent.
+                                * However, with DOM, osc extent alignment may
+                                * cause the first extent to start before the
+                                * OST portion of the layout.  This is never
+                                * accessed for i/o, but the unused portion
+                                * will not be covered by the sync request,
+                                * so we cannot assert in that case. */
+                               EASSERT(ergo(!(ext == first_extent(obj)),
+                                       ext->oe_start >= start &&
+                                       ext->oe_end <= end), ext);
                                osc_extent_state_set(ext, OES_LOCKING);
                                ext->oe_owner = current;
                                list_move_tail(&ext->oe_link,