touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #49346
[Bug 1413554] Re: OS's partitions never fsck'ed
Automatic fsck has been disabled in the upstream e2fsprogs a while ago
(see
http://git.whamcloud.com/tools/e2fsprogs.git/commitdiff/3daf592646). So
my suspicion is that you have kept your /home partition around for quite
a while and that one was still created with an mkfs.ext4 that enabled
automatic fsck, but your recent OS install already used a newer one. Can
you please check the output of
sudo dumpe2fs /dev/sdaX | grep 'ount count'
for both your root and your home partition? If the "Maximum mount count"
is -1, then automatic fsck is disabled. Or you might of course not use
ext[234] in the first place, but another file system which also has
automatic fsck.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1413554
Title:
OS's partitions never fsck'ed
Status in systemd package in Ubuntu:
Incomplete
Bug description:
In the past 3 months the /home data partition has been fsck'ed as expected (every 35 mounts) on that vivid i386 booted with systemd (systemd-sysv installed). But none of the 3 other OS partitions have been fsck'ed, which seems scary. So systemd seems not dealing with all the cases.
I have use 'shutdown -R now' to expect forcing fsck on the next boot, but only /home is checked.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 218-3ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
Uname: Linux 3.19.0-2-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu2
Architecture: i386
BootDmesg: (Nothing has been logged yet.)
CurrentDesktop: GNOME
Date: Thu Jan 22 11:54:22 2015
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413554/+subscriptions
References