Carlos, Thanks a lot for replying. :) I should have read the mount man page more carefully: By adding "xfs" to /etc/filesystems, the /etc/fstab entry even with an auto started working fine. blkid always had an entry for the volume in question but that didn't make a difference in this case: $ sudo blkid /dev/xvda1: LABEL="/" UUID="ebbf1f1c-fb71-40aa-93a3-056b455e5127" TYPE="ext4" /dev/xvdb: UUID="bf4be26c-1c1c-40fc-b5cf-b9048dcc61b6" TYPE="xfs" > Anyway, if you have the logs from your system when it tries to mount the > partition maybe it give us some clue of what is happening. It was the complete lack of logs in dmesg or /var/log/messages about a failure to mount is what confused me on why this was failing. A successful mount logs but an unsuccessful one doesn't. I think I will ask a mount expert for help on this. Thanks again, Vaibhaw On Wed, Feb 15, 2017 at 5:57 PM, Carlos Maiolino <cmaiolino@xxxxxxxxxx> wrote: > Hi, > >> LABEL=/ / ext4 defaults,noatime 1 1 >> tmpfs /dev/shm tmpfs defaults 0 0 >> devpts /dev/pts devpts gid=5,mode=620 0 0 >> sysfs /sys sysfs defaults 0 0 >> proc /proc proc defaults 0 0 >> /dev/sdb /redis_data auto noatime,noexec,nodiratime 0 0 >> $ df -T /redis_data/ >> Filesystem Type 1K-blocks Used Available Use% Mounted on >> /dev/xvdb xfs 5232640 32940 5199700 1% /redis_data >> >> However if I change the /etc/fstab directive to: >> >> /dev/sdb /redis_data xfs noatime,noexec,nodiratime 0 0 >> >> the auto mount starts working fine. Now this isn't a major problem >> since the functionality ultimately works. But I would certainly like >> to have the flexibility to avoid hard coding the fs type in the code >> that generates these fstab entries. >> > > I believe this is not a question for us, but for whatever software you are using > to mount your partitions, systemd, unit, init, whatever. It also might be a > problem with `mount` command, but if you say you can mount it normally after the > system is live, it looks not to be the case. > > XFS doesn't control who and how it reads the entries in fstab. > > As stated in `mount` manpage: > > "If no -t option is given, or if the auto type is specified, mount will try to > guess the desired type. Mount uses the blkid library for guessing the > filesystem type; if that does not turn up anything that looks familiar, mount > will try to read the file /etc/filesystems, or, if that > does not exist, /proc/filesystems. All of the filesystem types listed there > will be tried, except for those that are labeled "nodev" (e.g. devpts, proc > and nfs). If /etc/filesystems ends in a line with a single *, mount > will read /proc/filesystems afterwards. While trying, all filesystem > types will be mounted with the mount option silent." > > > Anyway, if you have the logs from your system when it tries to mount the > partition maybe it give us some clue of what is happening. > > Cheers > >> Any pointers or help is much appreciated. :) >> >> Thanks, >> Vaibhaw >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > Carlos -- Member of Technical Staff | ScaleGrid.io | @_vaibhaw | LinkedIn | Google+ Read my latest blog post: I Get To Know the Redis Database: Iterating Over Keys -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
