You should always use 'nobootwait' on remote mounts so that the server
can boot even when there is some problem with the remote mount.
Drop in to #gluster on Freenode IRC and ping me, semiosis, for help
troubleshooting this.
Thanks.
--
You received this bug notification because you are a member
[Expired for mountall (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mountall (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103
I create a bug (#1205075) about mountall that doesn't generate good
mount commande line for glusterfs. My Bug was marked duplicate of this
one.
The final problem was the same, but the clues I found are pretty
different.
More, this bug has importance=low but for me it would be CRITICAL 'cause
my s
Hi guys, i have the exact same problem but with ocfs2. mountall tries to
mount my remote volume before o2cb is running, so it fails. There's a
really nasty workaround adding /etc/init.d/o2cb start in the mountall-
net.conf file, like this:
# mountall-net - Mount network filesystems
#
# Send mount
On Mon, Apr 15, 2013 at 11:07:10PM -, Zach Bethel wrote:
> As you can see, _netdev is specified and is being ignored.
Incorrect. _netdev is being *respected*: _netdev does not tell the system
anything about *which* network device a filesystem mount depends on, so
mountall retries the mount af
I'm getting this same behavior on Ubuntu 12.04 LTS with an ext4
filesystem (iSCSI volume).
I am repeatedly seeing events like this sprinkled throughout my boot.log
file.
mount: special device /dev/mapper/mpath2-part1 does not exist
mount: special device /dev/mapper/mpath3-part1 does not exist
mou
Bruno, could you please attach the boot.log in question? I need to see
the entirety of what mountall is doing to understand what's really going
wrong. It's normal that mountall will attempt to mount all filesystems
ASAP after boot, which means sometimes it tries to mount them before the
network i
Ok so the situation was as following.
In boot.log we have:
mounted event handled for /var/www
local 2/3 remote 1/1 virtual 9/10 swap 0/0
Mount failed. Please check the log file for more details.
mountall: mount /var/www [337] terminated with status 1
Filesystem could not be mounted: /var/www
The
Bruno, your first pastebin shows:
local 3/3 remote 0/1 virtual 11/11 swap 0/0
mounting event handled for /var/www
mounting event sent for /var/www
mounting event handled for /var/www
unknown option _netdev (ignored)
mounted event handled for /var/www
remote finished
This tells us several things:
>From fstab we have this kind of log:
http://pastebin.com/DBFPmRTQ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103047
Title:
mountall causes automatic mounting of gluster shares to fail
To mana
Hello,
here is a log: http://pastebin.com/tBJLDVwj
I did the mountall myself fro mthe command line (i.e not log from
fstab).
Might indeed be that glusterfs is passed the _netdev option and does not
support it.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bug
Clayton, can you provide the output of 'mountall --verbose' requested in
comment #5, when using the _netdev option? To get this output, add
--verbose to the commandline in /etc/init/mountall.conf (as in the
original bug report).
BTW, glusterfs doesn't require any client daemons to be running for
I had to comment out the gluster fstab entry to get these 12.04.2
machines to finish their boot. Mountall kept throwing an "mountall event
failed" before the system console was up. Adding and removing _netdev
from the /etc/fstab had no affect.
My workaround involved booting the KVMs on server ISO
Just had the same thing happen on a number of our 12.04.2 KVM guests.
The _netdev parameter is being ignored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103047
Title:
mountall causes automatic m
> I am also running in this problem, and _netdev didn't fix it
Did you also get the "unknown option _netdev (ignored)" message? If so,
when and where does it show up?
_netdev is a standard option which should do exactly what's expected
here. So if it's not working, I would need to see some logs
I am also running in this problem, and _netdev didn't fix it, and as the
other guy said, right after booting, doing a `mount -a` mounts the /home
just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
On Thu, Jan 24, 2013 at 10:19:03AM -, Bram De Wilde wrote:
> Mounting of gluster volumes with or without the _netdev option in the
> fstab entry gives a:
> unknown option _netdev (ignored)
At what point do you get this message?
> It's my understanding that _netdev only works for nfs volumes,
Mounting of gluster volumes with or without the _netdev option in the
fstab entry gives a:
unknown option _netdev (ignored)
It's my understanding that _netdev only works for nfs volumes, no?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
mountall doesn't know that glusterfs is a network filesystem type. This
means that at boot time, there's a race between bringing the network up
and trying to mount /home, and when mountall wins the race, the mount
fails and is never re-tried. The newer version of mountall is faster by
mounting in
19 matches
Mail list logo
