Adjusting the Debian bug link, I discussed this on https://bugs.debian.org/809166 already. ifupdown should *not* stop "manual" interfaces with ifdown, unless you have an explicit "down" action in /etc/network/interfaces. I assume this is not the case. It was an explicit decision by the Debian maintainer (Guus) to not take these "network file system" checks into the new .service, as this hides real bugs and should really not be necessary.
So I take it the bug is now that "ifdown"ing a manual interface actually "ifconfig down"s it?
Adjusting the Debian bug link, I discussed this on https:/ /bugs.debian. org/809166 already. ifupdown should *not* stop "manual" interfaces with ifdown, unless you have an explicit "down" action in /etc/network/ interfaces. I assume this is not the case. It was an explicit decision by the Debian maintainer (Guus) to not take these "network file system" checks into the new .service, as this hides real bugs and should really not be necessary.
So I take it the bug is now that "ifdown"ing a manual interface actually "ifconfig down"s it?