[Bug 692355] Re: fsck doesn't update system info on login

[Steve Langasek]

On Mon, May 13, 2013 at 09:27:06AM -0000, maletin wrote:
> Steve Langasek (vorlon) wrote on 2013-05-11:    #24

> > Which means this is working exactly as designed.

> correct. but why does my vmware not start a fsck after reboot (even with
> /forcefsck)?

I don't know, but that seems to be describing a different issue than this
bug.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/692355

Title:
  fsck doesn't update system info on login

Status in “update-notifier” package in Ubuntu:
  Triaged

Bug description:
  Every time I login to my Ubuntu 11.04 Alpha 1 (server), I see this
  message:

  *** /dev/sda5 will be checked for errors at next reboot ***

  I have done both the 'touch /forcefsck' (file is gone after reboot)
  and I have done 'shutdown -rF now' and yet the message is still
  displayed.  I checked my boot.log and fsck did run:

  fsck from util-linux-ng 2.17.2 
  fsck from util-linux-ng 2.17.2 
  /dev/mapper/sh*tbox1-root: clean, 103845/4669440 files, 1179707/18669568 blocks
  /dev/sda5: clean, 245/124496 files, 83515/248976 blocks

  Since fsck did run successfully, the '*** /dev/sda5 will be checked
  for errors at next reboot ***' message should not appear again unless
  the system has determined the filesystem is dirty. I seriously doubt
  that this not very old drive is having this many problems, especially
  since the OS runs 24/7 with no problems besides this.

  lsb_release -rd:
  Description:    Ubuntu natty (development branch)
  Release:        11.04

  uname -a output:
  Linux node1 2.6.37-10-server #24-Ubuntu SMP Thu Dec 16 18:10:40 UTC 2010 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/692355/+subscriptions