Thanks Carlos! :) I will check with the Amazon Linux guys. There flavour of GNU/Linux seems to be based off RHEL but they have woefully inadequate documentation about everything. They seem to be using upstart as the startup daemon but the logs are nowhere to be found. Will talk to them about both adding XFS to /etc/filesysems and where do they logs from system boot time end up. Thanks again, Vaibhaw On Thu, Feb 16, 2017 at 2:27 PM, Carlos Maiolino <cmaiolino@xxxxxxxxxx> wrote: > Hi, > > On Thu, Feb 16, 2017 at 12:42:43PM +0530, Vaibhaw Pandey wrote: >> Sorry to chime in again but I was wondering if it makes sense to just >> add "xfs" to /etc/filesystems during installation of the package >> itself? It is visible in the /proc/filesystems once it is installed >> anyways. I have posed this question to the xfs@xxxxxxxxxxx mailing >> list as well. >> > Just FYI, xfs@xxxxxxxxxxx is no more, we have moved to vger, so, no one will > actually reply you there, always use linux-xfs@xxxxxxxxxxxxxxx > > Regarding your question, that is still a question not for XFS, /etc/filesystems > file doesn't belong to any xfs package, so we can't touch it, setting > /etc/filesystems is responsibility for another software, which, I *think* is > distro dependent. > > Maybe it don't take too long by now, once many distros started to use XFS as > their default FS, but that might be a good idea to open a bug against the distro > you are using. > >> On Thu, Feb 16, 2017 at 8:37 AM, Vaibhaw Pandey <vaibhaw@xxxxxxxxxxxx> wrote: >> > 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. >> > > > Particularly I have never thought about adding something there because I always > use 'xfs' in fstab. > >> > 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. > > These logs won't appear in dmesg, this is the kernel log, what you should look > for is for `mount` logs. You are using systemd I suspect, if I am correct, you > will see such logs using `journalctl` command. > >> > successful mount logs but an unsuccessful one doesn't. I think I will >> > ask a mount expert for help on this. >> > > > Hope it have helped, > > Cheers > -- > 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
