Fsck run on every boot since upgrade to natty

[Lukas Winter]

Binary package hint: upstart

SInce I upgraded to natty fsck is run on every boot which makes the boot process very slow. Also ureadahead does not create a pack file anymore. I have attached the boot log file.

My fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda3 during installation
UUID=1ba10fee-e03f-44de-ab61-e4c619e3e242 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda6 during installation
UUID=f8478e32-ab31-4b39-9bc6-29819de15685 /home btrfs defaults 0 2
# /windows was on /dev/sda2 during installation
UUID=7056EA5956EA2018 /windows ntfs defaults,umask=007,gid=46 0 0
# swap was on /dev/sda5 during installation
UUID=6e92af3c-aafe-410f-8e30-58e513c78443 none swap sw 0 0

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: upstart 0.9.7-1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Wed May 4 18:39:59 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: upstart
UpgradeStatus: Upgraded to natty on 2011-05-02 (1 days ago)

[dahias (wengahias)]

same problem with btfs filesystem on root-filesystem and ext4 on /boot

# / was on /dev/sda2 during installation
UUID=(blabla2) / btrfs defaults 0 1
# /boot was on /dev/sda1 during installation
UUID=(blabla1) /boot ext4 defaults 0 2

[dahias (wengahias)]

bad but helpful workaround for this would be to set <pass>-number from 1 to 0 in "/etc/fstab" - the filesystem will not be checked at all after this change.
-
UUID=(blabla2) / btrfs defaults 0 0
-

[Samuel Lidén Borell (samuellb)]

Maybe this is a duplicate of #771748 ?

[z (fgh4)]

No, this bug is not duplicate of #771748.

I doesn't have btrfs at all. I have a single ext2 root partition and got fsck check on every boot. There are errors on a file system. Fortunatelly all of them look like 'deleted inode have zero dtime'. It's looks like a system goes to power off / reboot before root fs is unmounted. Even 'sync' doesn't help.

I'm not familiar with upstart and can't find a real culprit.

[Lukas Winter (webmaster-geloescht)]

Yes, it is. I reported the btrfs-related issue in this bug report. Your problem sounds more like a real filesystem damage. Maybe you should open a question on Launchpad Answers or discuss your problem on a support forum.

[z (fgh4)]

Sorry, Lukas. I didn't see any btrfs mention nor in theme nor in description except one line at fstab and doesn't consider this bug is supposed to be related to btrfs somehow.

Thank you for your advise.