On 07/10/2018 00.50, Dave Howorth wrote:
On Sat, 6 Oct 2018 21:41:34 +0200 "Carlos E. R." <> wrote:
On 06/10/2018 21.25, L A Walsh wrote:
On 10/6/2018 5:07 AM, Dave Howorth wrote:
Usually I don't see probs like this on an xfs volume.
What are your mount parameters, BTW?
Default? Nothing about barriers, right?
From his post at the XFS mail list, apparently mount baulked at "noacls", as seen in dmesg output:
[ 467.743699] SGI XFS with ACLs, security attributes, no debug enabled [ 467.744733] XFS (dm-3): unknown mount option [noacl].
fstab was:
# grep live-tv /etc/fstab #LABEL=LiveTV /srv/live-tv xfs noatime,noacl 0 2 /dev/mint_vg/live-tv_lv /srv/live-tv xfs noatime,noacl 0 2
We forgot to ask for dmesg output here.
Thanks, Carlos. I thought I'd reported back but I suppose you wanted more detail than I gave. Yes, dmesg was key. The same information is in /var/log/messages and in the journal but both are so big that the only way to use them is search them and unfortunately I used the name of the filesystem to search. In dmesg the messages were conveniently near the end.
They would be similarly at the end on both syslog or journal, too. One trick is to open a terminal and do: journalctl --follow or tailf /var/log/messages or tail -f /var/log/messages and then, try the mount command on another terminal.
As to why XFS doesn't log the filesystem name and mount -v doesn't report the error to the command line... :( Well, just don't get me started! Usability seems to be ignored a lot of the time these days.
Yes, only some mount errors are reported to the terminal, others go to syslog only. Not only with XFS. And we did not remember this and told you to ask on the XFS mail list. It is even worse if you use the GUI to mount. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)