Why You Can’t FSCK a Mounted Partition – Explanation

Ok, so i found out on CentOS you can do this:

touch /forcefsck
echo -n "-ys" > /fsckoptions

to get a log of what fsck did i had to go on a harder route:
Warning: do this at your own risk, i have no ideia of what implications this could have if goes wrong

Edited the /etc/rc.sysinit (don't forget to backup) to get the desired behaviour:

from line 500 (changing the -C to -V gets rid of progress bars)

if [ "$BOOTUP" = "color" ]; then
       fsckoptions="-C $fsckoptions"
else
       fsckoption="-V $fsckoptions"

from line 648 changed the block that ran fsck to look like this:

outputtt="$(fsck -T -t noopts=_netdev -A $fsckoptions)"
mount -n -o remount,rw /
echo $outputtt > /var/log/fsckoutput
mount -n -o remount,ro /

one small perk is that it won't conserve new lines, but its readable in times of dire need.
Thanks for all the help.

Definitely XFS. XFS initialisation is much faster, performance is excellent, and XFS has been use for multi-terabytes volumes for ages. I currently support 230 machines with 8 to 76 TB XFS volumes. Tens are built with two or more RAID volumes aggregated through LVM without problem, so this is safe enough.

xfs_check speed depends mostly on the number of files. For typical large volumes (30 TB), xfs_repair takes less than 15 minutes given that the system has enough memory (older xfs_repair tends to gobbles tons of RAM), like 8 GB or more.