[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
The machine has been stable for a couple of days, and I tested today that fsck finished OK. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1547844 Title: systemd-fsckd does not allow fsck to finish Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G xhci_hcd.quirks=262144 SourcePackage: systemd UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI EXTREME 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.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to:
[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
I installed the 229-4ubuntu11 version. If the system is stable till the weekend, and does not hang/crash/livelock/deadlock/whatever happened when I tested the ubuntu9 version, I'll twiddle max mount count to force fsck during the weekend. -- 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/1547844 Title: systemd-fsckd does not allow fsck to finish Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G xhci_hcd.quirks=262144 SourcePackage: systemd UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI EXTREME 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.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage
[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
I have had 229-4ubuntu10 version now for the packages, and the machine has not crashed yet (last crash was Friday morning, so 2 days without crash... -- 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/1547844 Title: systemd-fsckd does not allow fsck to finish Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd package in Debian: Fix Released Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G xhci_hcd.quirks=262144 SourcePackage: systemd UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI EXTREME 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.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to:
[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
this might be unrelated, but since I tried the xenial-proposed packages, the computer has crashed about once a day. Usually I don't get any info on syslog, but I found this on syslog today: Sep 30 13:32:28 xpc kernel: [19560.717703] INFO: task jbd2/dm-1-8:879 blocked for more than 120 seconds. Sep 30 13:32:28 xpc kernel: [19560.717706] Tainted: G OE 4.4.0-38-generic #57-Ubuntu Sep 30 13:32:28 xpc kernel: [19560.717706] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 30 13:32:28 xpc kernel: [19560.717707] jbd2/dm-1-8 D 8800af107c98 0 879 2 0x Sep 30 13:32:28 xpc kernel: [19560.717710] 8800af107c98 0246 8801b8279b80 8801b5d36040 Sep 30 13:32:28 xpc kernel: [19560.717712] 8800af108000 8800ae9718b8 8800af107d88 8800af107d70 Sep 30 13:32:28 xpc kernel: [19560.717713] 8801b5d36040 8800af107cb0 8182c5f5 8800ad776900 Sep 30 13:32:28 xpc kernel: [19560.717714] Call Trace: Sep 30 13:32:28 xpc kernel: [19560.717720] [] schedule+0x35/0x80 Sep 30 13:32:28 xpc kernel: [19560.717723] [] jbd2_journal_commit_transaction+0x240/0x1870 Sep 30 13:32:28 xpc kernel: [19560.717727] [] ? wake_atomic_t_function+0x60/0x60 Sep 30 13:32:28 xpc kernel: [19560.717730] [] ? try_to_del_timer_sync+0x5e/0x90 Sep 30 13:32:28 xpc kernel: [19560.717732] [] kjournald2+0xca/0x250 Sep 30 13:32:28 xpc kernel: [19560.717733] [] ? wake_atomic_t_function+0x60/0x60 Sep 30 13:32:28 xpc kernel: [19560.717735] [] ? commit_timeout+0x10/0x10 Sep 30 13:32:28 xpc kernel: [19560.717736] [] kthread+0xd8/0xf0 Sep 30 13:32:28 xpc kernel: [19560.717738] [] ? kthread_create_on_node+0x1e0/0x1e0 Sep 30 13:32:28 xpc kernel: [19560.717740] [] ret_from_fork+0x3f/0x70 Sep 30 13:32:28 xpc kernel: [19560.717740] [] ? kthread_create_on_node+0x1e0/0x1e0 Sep 30 13:32:28 xpc kernel: [19560.717747] INFO: task vdr:1307 blocked for more than 120 seconds. Sep 30 13:32:28 xpc kernel: [19560.717748] Tainted: G OE 4.4.0-38-generic #57-Ubuntu Sep 30 13:32:28 xpc kernel: [19560.717748] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 30 13:32:28 xpc kernel: [19560.717749] vdr D 880198ac3b08 0 1307 1 0x0004 Sep 30 13:32:28 xpc kernel: [19560.717750] 880198ac3b08 88017b477bc8 8801b827a940 8800aeeb0dc0 Sep 30 13:32:28 xpc kernel: [19560.717751] 880198ac4000 8800ae971870 011d3628 8800ae971870 Sep 30 13:32:28 xpc kernel: [19560.717753] 8800ad776900 880198ac3b20 8182c5f5 8800ae971800 Sep 30 13:32:28 xpc kernel: [19560.717754] Call Trace: Sep 30 13:32:28 xpc kernel: [19560.717755] [] schedule+0x35/0x80 Sep 30 13:32:28 xpc kernel: [19560.717757] [] wait_transaction_locked+0x8a/0xd0 Sep 30 13:32:28 xpc kernel: [19560.717758] [] ? wake_atomic_t_function+0x60/0x60 Sep 30 13:32:28 xpc kernel: [19560.717759] [] add_transaction_credits+0x223/0x2a0 Sep 30 13:32:28 xpc kernel: [19560.717761] [] ? wake_up_bit+0x25/0x30 Sep 30 13:32:28 xpc kernel: [19560.717762] [] start_this_handle+0x10c/0x400 Sep 30 13:32:28 xpc kernel: [19560.717765] [] ? kmem_cache_alloc+0x1ca/0x1f0 Sep 30 13:32:28 xpc kernel: [19560.717766] [] jbd2__journal_start+0xdb/0x1e0 Sep 30 13:32:28 xpc kernel: [19560.717769] [] ? ext4_rename+0x41d/0x900 Sep 30 13:32:28 xpc kernel: [19560.717771] [] __ext4_journal_start_sb+0x6d/0x120 Sep 30 13:32:28 xpc kernel: [19560.717772] [] ext4_rename+0x41d/0x900 Sep 30 13:32:28 xpc kernel: [19560.717774] [] ? terminate_walk+0x64/0xd0 Sep 30 13:32:28 xpc kernel: [19560.717776] [] ext4_rename2+0x1d/0x30 Sep 30 13:32:28 xpc kernel: [19560.71] [] vfs_rename+0x58c/0x8e0 Sep 30 13:32:28 xpc kernel: [19560.717779] [] ? security_kernel_fw_from_file+0x20/0x70 Sep 30 13:32:28 xpc kernel: [19560.717780] [] SyS_rename+0x39f/0x3c0 Sep 30 13:32:28 xpc kernel: [19560.717782] [] entry_SYSCALL_64_fastpath+0x16/0x71 Sep 30 13:32:28 xpc kernel: [19560.717794] INFO: task kworker/u16:2:7411 blocked for more than 120 seconds. Sep 30 13:32:28 xpc kernel: [19560.717795] Tainted: G OE 4.4.0-38-generic #57-Ubuntu Sep 30 13:32:28 xpc kernel: [19560.717795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 30 13:32:28 xpc kernel: [19560.717796] kworker/u16:2 D 8801885777f8 0 7411 2 0x Sep 30 13:32:28 xpc kernel: [19560.717800] Workqueue: writeback wb_workfn (flush-252:1) Sep 30 13:32:28 xpc kernel: [19560.717801] 8801885777f8 8801b8279b80 8800940ee040 Sep 30 13:32:28 xpc kernel: [19560.717803] 880188578000 8800ae971870 011d3628 8800ae971870 Sep 30 13:32:28 xpc kernel: [19560.717804] 8800ad776900 880188577810 8182c5f5 8800ae971800 Sep 30 13:32:28 xpc kernel: [19560.717805] Call Trace: Sep 30 13:32:28 xpc kernel: [19560.717806] []
[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
now it worked. the packages I needed: kex@xpc:~$ sudo dpkg -l | grep 229 ii libpam-systemd:amd64 229-4ubuntu9 amd64system and service manager - PAM module ii libsystemd0:amd64229-4ubuntu9 amd64systemd utility library ii libsystemd0:i386 229-4ubuntu9 i386 systemd utility library ii libudev1:amd64 229-4ubuntu9 amd64libudev shared library ii libudev1:i386229-4ubuntu9 i386 libudev shared library ii systemd 229-4ubuntu9 amd64system and service manager ii systemd-sysv 229-4ubuntu9 amd64system and service manager - SysV links ii udev 229-4ubuntu9 amd64/dev/ and hotplug management daemon ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1547844 Title: systemd-fsckd does not allow fsck to finish Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia
[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish
hi, the packet fails to install: kex@xpc:~$ LANG=en sudo apt-get install systemd/xenial-proposed Reading package lists... Done Building dependency tree Reading state information... Done Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 'systemd' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd : Depends: libsystemd0 (= 229-4ubuntu9) but 229-4ubuntu8 is to be installed Recommends: libpam-systemd but it is not going to be installed E: Unable to correct problems, you have held broken packages. If I try to install both, a scary list of packages will be removed (I have no courage now to do that): kex@xpc:~$ LANG=en sudo apt-get install libsystemd0/xenial-proposed systemd/xenial-proposed Reading package lists... Done Building dependency tree Reading state information... Done Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 'libsystemd0' Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 'systemd' The following packages were automatically installed and are no longer required: account-plugin-tools accountsservice-ubuntu-schemas argyll argyll-ref dbus-property-service gir1.2-gdesktopenums-3.0 gir1.2-gnomedesktop-3.0 gir1.2-udisks-2.0 gnome-shell-common gstreamer1.0-plugins-base:i386 libaudio2:i386 libcdparanoia0:i386 libconnectivity-qt1 libdbus-cpp5 libglib2.0-0:i386 libgstreamer-plugins-base1.0-0:i386 libgstreamer1.0-0:i386 libhybris libhybris-utils libjpeg62:i386 libmedia1 libmng2:i386 libmysqlclient20:i386 libonline-accounts-client1 libonline-accounts-daemon1 libonline-accounts-qt1 liboobs-1-5 libopts25 libopus0:i386 liborc-0.4-0:i386 libpkcs11-helper1 libprocess-cpp3 libqgsttools-p1 libqmenumodel0 libqofono-qt5-0 libqt4-sql:i386 libqt4-sql-mysql:i386 libqt4-xml:i386 libqt5multimedia5-plugins libqt5multimediaquick-p5 libqt5multimediawidgets5 libqt5systeminfo5 libqt5xmlpatterns5 libqtcore4:i386 libsystemsettings1 libtheora0:i386 libtrust-store2 libubuntuoneauth-2.0-0 libvisual-0.4-0:i386 libvisual-0.4-plugins:i386 libxss1:i386 libxtst6:i386 libxv1:i386 mate-polkit-common mutter-common network-manager-openvpn ntp openvpn plainbox-secure-policy python-gpgme python3-gnupg python3-guacamole python3-jinja2 python3-markupsafe python3-padme python3-pyparsing python3-xlsxwriter qmenumodel-qml qml-module-qtmultimedia qml-module-qtsysteminfo qml-module-ubuntu-connectivity qml-module-ubuntu-onlineaccounts2 qtdeclarative5-gsettings1.0 qtdeclarative5-ofono0.2 qtdeclarative5-ubuntu-settings-components sqlite3 system-image-common system-image-dbus system-tools-backends ubuntu-keyboard-data ubuntuone-credentials-common urfkill Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: apparmor-easyprof apparmor-easyprof-ubuntu click click-apparmor gir1.2-click-0.4 gir1.2-gee-0.8 libboost-log1.58.0 libboost-regex1.58.0 libboost-thread1.58.0 libc-ares2 libclick-0.4-0 libcontent-hub0 libgflags2v5 libgoogle-glog0v5 libhardware2 libhybris-common1 liblibertine1 liblttng-ust-ctl2 liblttng-ust0 libubuntu-app-launch2 libubuntu-application-api3 libubuntu-download-manager-client1 libubuntu-download-manager-common1 libubuntu-platform-hardware-api3 libudm-common1 liburcu4 ofono powerd python3-apparmor python3-apparmor-click python3-click-package python3-libapparmor qtdeclarative5-ubuntu-content1 ubuntu-application-api3-test Suggested packages: click-reviewers-tools ubuntu-app-launch-tools | upstart-app-launch-tools content-hub systemd-ui systemd-container Recommended packages: libpam-systemd The following packages will be REMOVED: aptdaemon brasero checkbox checkbox-converged checkbox-gui checkbox-qt colord deja-dup-backend-gvfs gnome-bluetooth gnome-color-manager gnome-control-center gnome-disk-utility gnome-session gnome-settings-daemon gnome-system-log gnome-system-tools gnome-tweak-tool gnome-user-share gvfs gvfs-backends gvfs-daemons gvfs-fuse hplip indicator-bluetooth indicator-sound landscape-client-ui-install language-selector-gnome libasound2-plugins:i386 libavahi-client3:i386 libcanberra-pulse libcups2:i386 libdbus-1-3:i386 libdbusmenu-qt2:i386 libpam-systemd libpulse0:i386 libqt4-dbus:i386 libqt4-declarative:i386 libqt4-network:i386 libqt4-opengl:i386 libqt4-script:i386 libqt4-xmlpatterns:i386 libqtdbus4:i386 libqtgui4:i386 libqtwebkit4:i386 libsane:i386 libsystemd0:i386 nautilus nautilus-dropbox nautilus-sendto nautilus-share network-manager network-manager-gnome plainbox-provider-checkbox plainbox-provider-resource-generic policykit-1 policykit-1-gnome printer-driver-postscript-hp pulseaudio pulseaudio-module
[Touch-packages] [Bug 1547844] Re: systemd does not allow fsck to finish on ubuntu 15.10
Then: running fsck in recovery mode works nice: root@xpc:~# fsck /dev/mapper/xpcvg-home fsck – util-linux 2.26.2 e2fsck 1.42.12 (29-Aug-2014) /dev/mapper/xpcvg-home has been mounted 166 times without being checked, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/mapper/xpcvg-home: 368728/65536000 files (1.5% non-contiguous), 78669441/262144000 blocks root@xpc:~# tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474559 Free inodes: 65167272 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 14:39:09 2016 Mount count: 0 Maximum mount count: 157 Last checked: Sat Feb 20 14:39:09 2016 Check interval: 15552000 (6 months) Next check after: Thu Aug 18 15:39:09 2016 Lifetime writes: 1114 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks -- 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/1547844 Title: systemd does not allow fsck to finish on ubuntu 15.10 Status in systemd package in Ubuntu: New Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has
[Touch-packages] [Bug 1547844] [NEW] systemd does not allow fsck to finish on ubuntu 15.10
Public bug reported: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width:384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G xhci_hcd.quirks=262144 SourcePackage: systemd UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI EXTREME 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.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1547844 Title: systemd does not allow fsck to finish on ubuntu 15.10 Status in systemd package in Ubuntu: New Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem
