New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fsck errors in system journal #1257

Closed
fasaxc opened this Issue Apr 29, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@fasaxc

fasaxc commented Apr 29, 2016

I'm not sure if these are benign but, at boot, I noticed fsck is complaining that it doesn't support the filesystem on my coreos host:

Apr 29 08:07:18 localhost systemd-fsck[656]: /dev/sda3 has unsupported feature(s): FEATURE_R24 FEATURE_R25 FEATURE_R26 FEATURE_R27 FEATURE_R28 FEATURE_R29 FEATURE_R30 FEATURE_R31
Apr 29 08:07:18 localhost systemd-fsck[656]: e2fsck: Get a newer version of e2fsck!
Apr 29 08:07:18 localhost systemd-fsck[656]: fsck failed with error code 8.
Apr 29 08:07:18 localhost systemd-fsck[656]: Ignoring error.

I'm running coreos-alpha-1010-1-0-v20160407 on GCE.

@crawford

This comment has been minimized.

Show comment
Hide comment
@crawford

crawford Apr 29, 2016

Member

This is due to us clobbering the filesystem flags. We do this to try to prevent people from remounting /usr read-write. This is safe to ignore.

Member

crawford commented Apr 29, 2016

This is due to us clobbering the filesystem flags. We do this to try to prevent people from remounting /usr read-write. This is safe to ignore.

@dnorthup-ums

This comment has been minimized.

Show comment
Hide comment
@dnorthup-ums

dnorthup-ums Jan 27, 2017

@crawford The correct way to fix this is not to ignore errors one finds inconvenient. Please work with the CoreOS core contributors to fix the appropriate systemd unit to not fsck /usr or start using the fstype flags appropriately. Even better, consider including an fsck that can actually deal with the filesystem as it is defined.

dnorthup-ums commented Jan 27, 2017

@crawford The correct way to fix this is not to ignore errors one finds inconvenient. Please work with the CoreOS core contributors to fix the appropriate systemd unit to not fsck /usr or start using the fstype flags appropriately. Even better, consider including an fsck that can actually deal with the filesystem as it is defined.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Jul 26, 2017

Member

/usr is immutable, so it doesn't make sense to fsck it. On systems with a sufficiently recent bootloader, dm-verity will notice any filesystem corruption that does occur.

coreos/bootengine#126 disables fsck for the /usr partition. That change should be included in 1492.0.0.

Member

bgilbert commented Jul 26, 2017

/usr is immutable, so it doesn't make sense to fsck it. On systems with a sufficiently recent bootloader, dm-verity will notice any filesystem corruption that does occur.

coreos/bootengine#126 disables fsck for the /usr partition. That change should be included in 1492.0.0.

@bgilbert bgilbert closed this Jul 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment