[OpenWrt-Devel] Problem with blockd starting after partitions mounting
zajec5 at gmail.com
Tue May 12 02:16:08 EDT 2020
On Sun, 29 Dec 2019 at 15:35, Rafał Miłecki <zajec5 at gmail.com> wrote:
> A year ago I introduced hotplug.d script meant to manage Samba shares
> in a clever way by:
> 1) Using "mount" hotplug.d event
> 2) Getting mount info from blockd
> Relevant commit ef1efa756e0d ("samba36: add package with hotplug.d
> script for auto sharing"):
> Today I realized it doesn't work for partitions mounted at boot time
> as blockd isn't running then and "ubus call block info" simply fails.
> "mount" hotplug.d events at boot time are generated by:
> 1) /etc/hotplug.d/block/10-mount calling /sbin/block hotplug
> 2) /sbin/block hotplug calling /sbin/hotplug-call mount
> So it's not a matter of init.d order and adjusting START in
> /etc/init.d/blockd (block devices appear EARLY).
> Any idea how to solve this problem? Should we maybe postpone "mount"
> events? E.g. until "blockd" start? Or should hotplug.d script somehow
> wait until "blockd" starts?
For a reference this was fixed by 9ab936d973df ("block(d): always call
hotplug.d "mount" scripts from blockd"):
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel