# The rootfs size overrides IMAGE\_ROOTFS\_MAXSIZE

**URL:** <https://hub.mender.io/t/the-rootfs-size-overrides-image-rootfs-maxsize/1016>\
**Category:** General Discussions\
**Created:** [September 14, 2019, 2:49pm UTC](https://hub.mender.io/t/the-rootfs-size-overrides-image-rootfs-maxsize/1016 "2019-09-14T14:49:25Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [October 12, 2020, 2:27pm UTC](https://hub.mender.io/t/the-rootfs-size-overrides-image-rootfs-maxsize/1016/21 "2020-10-12T14:27:02Z")

</div>

No because at that point you do not know if the new update is sane.

What you need to do is to somehow delay the extra reboot until the update has been committed. I’m not real clear on your use case so I can’t think of anything else to suggest.

[Previous page](https://hub.mender.io/t/the-rootfs-size-overrides-image-rootfs-maxsize/1016.md?page=1)