In ubuntu 14.05.5 I am running into the same issue. I have a iscsi
device added in fstab with _netdev switch but doesnt' seem to work.
system just hangs at boot, i have to go into recovery mode to comment
out the filesystem to get the system to boot.
Interested in what others have done as a work a
I have a similar problem when trying to mount a cephfs volume on ubuntu 14.04.
It just freezes and I can't do anything about it.
I'm unable to figure out why it fails. I am running OpenvSwitch, what I see in
boot log is something like this:
* Starting configure network device
* Starting configure
I seem to be running into this bug on a new build of 14.04.4 when using
an LVM on a multipathed ISCSI drive which I am trying to mount at
/var/lib/mysql.
I'm no upstart guru, so if there is anything I can post to help verify
if it is this bug that is causing an issue please let me know.
If I just
OK. Couldn't find another bug about this with systemd, so created
#1536294.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313513
Title:
mountall does not honour _netdev
To manage notifications abo
On Wed, Jan 20, 2016 at 12:52:34PM -, Jonathan Kamens wrote:
> P.S. for me, it's 15.10 that's not working.
You're on the wrong bug. Mountall is an upstart-specific package, which is
not used for mounting in systemd systems (15.04 and later).
--
You received this bug notification because you
Fixed for me by putting this in /etc/systemd/system/remote-fs-
pre.target.d/override.conf:
[Unit]
Requires=NetworkManager-wait-online.service
After=NetworkManager-wait-online.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Actually, I was wrong, it's not because of DNS problems, it's because
systemd is trying to mount the filesystems before the network is up. I
changed the host names in /etc/fstab to IP addresses, and it still
doesn't work:
Jan 20 08:17:31 jik5 mount[979]: mount error(101): Network is
unreachable
S
I'm really not sure what to make of all this. My fstab has several cifs
filesystems in it, and none of them mount at boot regardless of whether
_netdev is specified. I don't know whether that's because of this bug --
it's not even clear to me _exactly_ what this bug is about -- or some
other bug th
By the way, in my case it appears to be because mount can't resolve the
host name of the CIFS file server. I think this is because systemd is
trying to mount the filesystems before the nameserver is finished
launching, so perhaps if bind9.service is enabled on the host, systemd
needs to wait for it
IMO it is not enough to say "obsolete documentation, someone should
remove it". Some of us have been using *nix for years (or decades), and
some of these facilities have been developed and stabilized years ago.
We rely on things that used to work to keep working. At the very least,
one should revis
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313513
Title:
m
mountall blocks only those parts of the boot process that are marked as
depending on the relevant filesystem. And by default, mountall assumes
that the 'filesystem' event should not be emitted until all filesystems
under /usr and /var are mounted. If this is not the correct policy for
your use ca
As a point of interest, this is an `rbdmount` script I use with upstart
as a work-around to the mountall issue.
It assumes that the devices listed in /etc/ceph/rbdmap are intended to
be mounted locally, and so calls mount on each listed device that
appears.
Very much a hack: it'd be more elegant
On 29/04/14 10:32, Steve Langasek wrote:
> While the mount(8) manpage says that _netdev causes the mount to be
> deferred until the network is up, this manpage was written in a bygone
> era when "network up" was a discrete event, which it hasn't been for a
> long time.
Ahh, so out of date document
While the mount(8) manpage says that _netdev causes the mount to be
deferred until the network is up, this manpage was written in a bygone
era when "network up" was a discrete event, which it hasn't been for a
long time. The current behavior is that _netdev devices will be tried
immediately on boo
15 matches
Mail list logo
