On Wed, Jan 3, 2018 at 2:44 PM, Chengguang Xu <cgxu519@xxxxxxxxxx> wrote:
>
[...]
> In order to add overlay support in some requirement checks like _require_metadata_journaling,
> I think it’s better save underlying filesystem type to $OVL_BASE_FSTYP and doing proper check based
> on it.
>
> Currently $OVL_BASE_FSTYP and $FSTYP all set to “overlay”, Is there any specific reason for it?
>
In _overlay_config_override():
# Config file may specify base fs type, but we obay -overlay flag
export OVL_BASE_FSTYP="$FSTYP"
export FSTYP=overlay
So either your setup is wrong or there is a bug.
$OVL_BASE_FSTYP *should* contain the base fs type,
but only if you defined FSTYPE in your config file when running ./check -overlay
Cheers,
Amir.
--
To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
