[dataflow] (DATAFLOW-361) Samba fs command in datastage-config appears to fail

[Mark Johnson (Created) (JIRA)]

Samba fs command in datastage-config appears to fail
----------------------------------------------------

Key: DATAFLOW-361
URL: http://dataflow-jira.bodleian.ox.ac.uk/jira/browse/DATAFLOW-361
Project: DataFlow
Issue Type: Bug
Components: DataStage
Affects Versions: 0.3
Environment: Ubuntu 12.04 LTS
Reporter: Mark Johnson
Assignee: Bhavana Ananda
Priority: Minor


With a fresh install of datastage, I run the {{datastage-config}} command as root and press {{c}} to get the config screen.

Under the Samba heading, I have the following warning:
{code}
Warning: The filesystem frpm which DataStage will serve data is missing mount options
Action: Type 'fs' to ensure the filesystem is mounted with acl and user_xattr options
{code}

I run {{fs}}, and the screen refreshes with the warning intact, so the command appears to have failed to have the desired effect.

My disk has an ext2 /boot parition, and an ext4 / partition on top of LVM. I don't know if having all data on the same partition is causing this problem, but that was a possibility that occurred to me. My fstab is as follows:
{code}
dataflow@dataflow:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/mapper/dataflow-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=c7447558-318c-4e0c-a626-283013606683 /boot ext2 defaults 0 2
/dev/mapper/dataflow-swap_1 none swap sw 0 0
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: http://dataflow-jira.bodleian.ox.ac.uk/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira