Public bug reported:

A customer reported on all of their ext3 and none of their ext4 systems
that the file system was in read-only mode, I believe after rebooting
into 3.13.0-157.207 from 3.13.0-156.206. Here is the output of tune2fs
-l for one of the file systems:

tune2fs 1.42.12 (29-Aug-2014)
Last mounted on:          /
Filesystem UUID:          748f503a-443d-4769-8dd2-45ff46b48555
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype 
needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1966080
Block count:              7863296
Reserved block count:     393164
Free blocks:              4568472
Free inodes:              1440187
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1022
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stride:              128
RAID stripe width:        512
Filesystem created:       Thu Feb 25 21:54:24 2016
Last mount time:          Fri Aug 24 07:40:51 2018
Last write time:          Fri Aug 24 07:40:51 2018
Mount count:              1
Maximum mount count:      25
Last checked:             Fri Aug 24 07:38:54 2018
Check interval:           15552000 (6 months)
Next check after:         Wed Feb 20 07:38:54 2019
Lifetime writes:          7381 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:      d6564a54-cd2a-4804-ad94-1e4e0e47933a
Journal backup:           inode blocks
FS Error count:           210
First error time:         Fri Aug 24 07:40:51 2018
First error function:     ext4_validate_block_bitmap
First error line #:       376
First error inode #:      0
First error block #:      0
Last error time:          Sun Aug 26 19:35:16 2018
Last error function:      ext4_remount
Last error line #:        4833
Last error inode #:       0
Last error block #:       0

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789131

Title:
  Probable regression with EXT3 file systems and CVE-2018-1093 patches

Status in linux package in Ubuntu:
  New

Bug description:
  A customer reported on all of their ext3 and none of their ext4
  systems that the file system was in read-only mode, I believe after
  rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
  of tune2fs -l for one of the file systems:

  tune2fs 1.42.12 (29-Aug-2014)
  Last mounted on:          /
  Filesystem UUID:          748f503a-443d-4769-8dd2-45ff46b48555
  Filesystem magic number:  0xEF53
  Filesystem revision #:    1 (dynamic)
  Filesystem features:      has_journal ext_attr resize_inode dir_index 
filetype needs_recovery sparse_super large_file
  Filesystem flags:         signed_directory_hash
  Default mount options:    (none)
  Filesystem state:         clean with errors
  Errors behavior:          Continue
  Filesystem OS type:       Linux
  Inode count:              1966080
  Block count:              7863296
  Reserved block count:     393164
  Free blocks:              4568472
  Free inodes:              1440187
  First block:              0
  Block size:               4096
  Fragment size:            4096
  Reserved GDT blocks:      1022
  Blocks per group:         32768
  Fragments per group:      32768
  Inodes per group:         8192
  Inode blocks per group:   512
  RAID stride:              128
  RAID stripe width:        512
  Filesystem created:       Thu Feb 25 21:54:24 2016
  Last mount time:          Fri Aug 24 07:40:51 2018
  Last write time:          Fri Aug 24 07:40:51 2018
  Mount count:              1
  Maximum mount count:      25
  Last checked:             Fri Aug 24 07:38:54 2018
  Check interval:           15552000 (6 months)
  Next check after:         Wed Feb 20 07:38:54 2019
  Lifetime writes:          7381 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:      d6564a54-cd2a-4804-ad94-1e4e0e47933a
  Journal backup:           inode blocks
  FS Error count:           210
  First error time:         Fri Aug 24 07:40:51 2018
  First error function:     ext4_validate_block_bitmap
  First error line #:       376
  First error inode #:      0
  First error block #:      0
  Last error time:          Sun Aug 26 19:35:16 2018
  Last error function:      ext4_remount
  Last error line #:        4833
  Last error inode #:       0
  Last error block #:       0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789131/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to