"Wrong ufstype may corrupt your filesystem" - Should I be worried?

I was just now looking through /var/log/syslog and I found these line which worried me:

ufs: You didn't specify the type of your ufs filesystem
May  5 09:06:09 Bath-Towel kernel: [  425.626221] 
May  5 09:06:09 Bath-Towel kernel: [  425.626221] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
May  5 09:06:09 Bath-Towel kernel: [  425.626221] 
May  5 09:06:09 Bath-Towel kernel: [  425.626221] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

What is it, what does it mean, and what should I do about it (if anything)? If more information is needed to answer my question, please just comment and I will provide it.

OS Information:

Description:    Ubuntu 15.04
Release:    15.04

Solution 1:

This message could be generated when the user or a script runs the update-grub script, which would explain why you get it after kernel update. From what i understood, update-grub tries to dynamically find all the possible partitions and operating systems in them for generating the most complete grub.conf file. one of the options(one of the last ones actually) that update-grub tries for mounting an unknown partition, is ufs. This is a bug however as it could be misleading and confuse the user.

More info: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1374759

Solution 2:

I got this error and I fixed it updating to kernel 3.19.0-26. I think it was some bug in 3.19.0-25.

Solution 3:

This is a bit "me too" but I saw this during a different kernel upgrade to 4.2 (most recent at time of writing)

Seems some installation code (acer recovery partition) tries to mount all partitions including a partition that should not be mounted /dev/sda4 which is an extended partition block created to have more than 4 partitions on a disk. Its not just UFS, the script tries to mount it as ext4, fat, and some others, each have a different error message, only the UFS error message looks a bit scary.

So I think this is a cosmetic issue and the messages can be ignored.