systemd-fsck show message when boot evertime. What does meaning? And how to hidding them.
systemd-fsck: /dev/sda4: clean, 112977/9296096 files, 185427/21217024 blocks systemd-fsck: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
Sorry, I loss something. Full message is:
/dev/sda3: clean, 131838/991232 files, 1193255/3933482 blocks systemd-fsck: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks systemd-fsck: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 20G 0 disk ├─sda1 8:1 0 102M 0 part /boot ├─sda2 8:2 0 258.9M 0 part [SWAP] ├─sda3 8:3 0 15G 0 part / └─sda4 8:4 0 4.7G 0 part /home
Last edited by eshizhan (2012-10-22 04:52:13)
fsck stands for "file system check" . systemd will check all of your filesystems every time you boot .
systemd-fsck: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks systemd-fsck: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
These messages mean that there are no problems with your filesystems and they are "clean". If there ever was a problem with any of your filesystems, these messages are how fsck will let you know so I don't think you want to hide them.
My kernel argument has 'quiet', So I think it should be hided when boot normal.
if you really want to hide the output, it may be possible to override systemd-fsck@.service by copying it to /etc/systemd/system/ and changing StandardOutput to:
Note however that I did not test this and it is a bad idea in general because the fsck output may be important if there are actual problems with your filesystem or even the hard drive itself.
better to set it to "journal" so you can at least see the output in the journal later.
Last edited by 65kid (2012-10-21 15:27:56)
Yes,But I don't understand why it's output when my filesystem is normal.
I inadvertantly got some of the messages to go away when I changed the level of MaxLevelConsole= in journald.conf. I used to have all my filesystem's fsck shown, and now that I have it set to err instead of debug, my / partition is the only one shown. Maybe by changing it to 'emerg' or 0 might surpress it, but I have not tried. I just thought it was probably good that I know that my filesystem is okay.
WonderWoofy, I try your way. The systemd-fsck message have been hided when I set MaxLevelConsole=notice.
However the message still show:
/dev/sda3: clean, 131838/991232 files, 1193255/3933482 blocks
I think it's not systemd-fsck output.
Out of curiosity, did you manage to get rid of this "clean" message?
That is output from the initramfs. I don't know that there is actually a way to get rid of this. Though I guess you could edit the mkinitpcio scripts, but if you were to redirect to /dev/null for example, you wouldn't be able to see if things were totally f*cked up. So it is probably a better idea to simply let it do its thing for now. The issue has come up on the systemd mailing list. There was a general concensus that the fsck binaries should work like other programs where a successful non-error run (exits with a 0 code) should not print anything, or at least the output should be optional in some way. There was mention of trying to work with the upsteam filesystem devs to get this changed.