[Bugs] [Bug 1199545] New: mount.glusterfs uses /dev/stderr and fails if the device does not exist
bugzilla at redhat.com
bugzilla at redhat.com
Fri Mar 6 15:16:00 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1199545
Bug ID: 1199545
Summary: mount.glusterfs uses /dev/stderr and fails if the
device does not exist
Product: GlusterFS
Version: 3.6.2
Component: scripts
Assignee: bugs at gluster.org
Reporter: nico-redhat-bugzilla at schottelius.org
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
Instead of using standard >&2 implementation, mount.glusterfs writes to
/dev/stderr.
This causes the mount to fail on current CentOS 7 systems with the following
message:
Mar 06 16:13:44 entrance mount[1886]: /sbin/mount.glusterfs: line 13:
/dev/stderr: No such device or address
Version-Release number of selected component (if applicable):
3.6.2
How reproducible:
always
Steps to Reproduce:
1. Add entry to /etc/fstab on CentOS 7 with glusterfs 3.6.2, reboot.
2. systemctl status
Actual results:
var-lib-one-datastores-100.mount - /var/lib/one/datastores/100
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Fri 2015-03-06 16:13:44 CET; 42s
ago
Where: /var/lib/one/datastores/100
What: vmhost2-cluster1.place4.ungleich.ch:/cluster1
Process: 1886 ExecMount=/bin/mount
vmhost2-cluster1.place4.ungleich.ch:/cluster1 /var/lib/one/datastores/100 -t
glusterfs -o
defaults,_netdev,backupvolfile-server=vmhost1-cluster1.place4.ungleich.ch
(code=exited, status=1/FAILURE)
Mar 06 16:13:40 entrance systemd[1]: Mounted /var/lib/one/datastores/100.
Mar 06 16:13:44 entrance mount[1886]: /sbin/mount.glusterfs: line 13:
/dev/stderr: No such device or address
Mar 06 16:13:44 entrance systemd[1]: var-lib-one-datastores-100.mount mount
process exited, code=exited status=1
Mar 06 16:13:44 entrance systemd[1]: Unit var-lib-one-datastores-100.mount
entered failed state.
[16:14:27] entrance:~#
Expected results:
glusterfs volumes mound
Additional info:
Preparing a patch for inclusion at the moment
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list