Il 14/05/2015 19:46, James Hogarth ha scritto:
On 14 May 2015 16:12, "Alessandro Baggi" alessandro.baggi@gmail.com wrote:
Il 14/05/2015 13:40, Tris Hoar ha scritto:
On 14/05/2015 10:16, Alessandro Baggi wrote:
Hi List, I've installed C7.1 and today configuring fstab for another disk I get this:
UUID=d5ff30df-9e1d-4fc8-99b6-845ffa6509db / xfs defaults 0 0 UUID=052f75bc-0513-45e0-a01f-06c9a698469f /mnt/data xfs defaults 0 0 UUID=732dafbd-2f14-4dd6-8513-1504b13302f1 swap swap defaults 0 0
Fields fs_freq and fs_passno are all set to 0. This fstab was generated by the installer and not yet modified.
To reproduce this, I've installed a minimal centos on a VM and the same problem persists.
I don't know if this is a bug or if there is a new system that does not require the last two field on C7 REL 1503.
Someone has the same problem?
THanks in advance.
This is the default when using the xfs filesystem
Tris
Hi Tris, sorry but, I've another c7(1406) and the upgraded to 1503 rel with all
xfs fs but in fstab i get different values.
Why this is the default for xfs? No fsck on boot? (Sorry I can't find
info on web)
What's happening if I set 1 1, 1 2...?
Thanks in advance.
There is no boot time XFS fsck
The fsck.xfs file is a noop
In the event that a repair is needed you should use xfs_repair ... The design is to avoid this though and if you reach this stage bad things must have happened to your system (more than a simple power loss probably). _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Thanks for your reply. Than there is not automatic check for xfs fs from boot without user script.