[Bug 1321418] Re: fsck.ext4 fails to fix multiply-claimed blocks: can't find dup_blk

Tue May 20 21:53:25 UTC 2014

Yeah, sorry about that. If I had known you were likely to respond so
quickly, I might have left it alone until I heard from you.

dumpe2fs 1.42.8 (20-Jun-2013)
Filesystem volume name:   root
Last mounted on:          /
Filesystem UUID:          3dd3e793-f873-4db2-8c68-801b217ba06e
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Remount read-only
Filesystem OS type:       Linux
Inode count:              30285824
Block count:              121119454
Reserved block count:     2422389
Free blocks:              14803241
Free inodes:              29247104
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      995
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Fri Jun 24 17:47:00 2011
Last mount time:          Tue May 20 12:03:32 2014
Last write time:          Tue May 20 12:03:31 2014
Mount count:              2
Maximum mount count:      -1
Last checked:             Tue May 20 11:10:00 2014
Check interval:           2419200 (4 weeks)
Next check after:         Tue Jun 17 11:10:00 2014
Lifetime writes:          6072 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:       27269186
Default directory hash:   half_md4
Directory Hash Seed:      814029bb-cac6-432f-9a6b-a7924a5e8f4a
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00b205bb
Journal start:            237

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

Title:
  fsck.ext4 fails to fix multiply-claimed blocks: can't find dup_blk

Status in “e2fsprogs” package in Ubuntu:
  New

Bug description:
  The last few times my root ext4 filesystem had its regularly-scheduled
  boot-time check, errors were reported. The first time it happened, I
  simply told the system to fix the errors, but since they kept coming
  up again, I decided to look more closely. I booted from a live USB
  drive, assembled my raid partitions, and ran fsck.ext4 manually.

  Without any options, fsck.ext4 simply reported that the filesystem was
  clean, and exited. Things got more interesting when I ran with -f. It
  reported several multiply-claimed blocks, and when I told fsck to go
  ahead and clone them, it failed with an internal error. Repeated runs
  of fsck revealed that the filesystem was still not fixed, and repeated
  attempts to fix the problem also failed, reporting that multiply-
  claimed blocks already reassigned or cloned.

  I was lucky in that the files in question were unimportant, so
  deleting one of them and running fsck again seems to have fixed my
  problem this time. However, fsck's internal error and failure to fix
  the problem in the first place is worrisome.

  Here's the full output:

  $ sudo fsck.ext4 -f /dev/md/1
  e2fsck 1.42.8 (20-Jun-2013)
  Pass 1: Checking inodes, blocks, and sizes

  Running additional passes to resolve blocks claimed by more than one inode...
  Pass 1B: Rescanning for multiply-claimed blocks
  Multiply-claimed block(s) in inode 27528089: 73467268 9287 9288 9289 9290 9291
  9292 9293
  Multiply-claimed block(s) in inode 27528105: 73467268 9287 9288 9289 9290 9291
  9292 9293
  Pass 1C: Scanning directories for inodes with multiply-claimed blocks Pass 1D:
  Reconciling multiply-claimed blocks
  (There are 2 inodes containing multiply-claimed blocks.)

  File
  /home/user/dir/subdir/05.09.2013_13.15.48.300.jpg
  (inode #27528089, mod time Mon Jan 13 02:50:08 2014)
    has 7 multiply-claimed block(s), shared with 1 file(s):
          /home/user/.thumbnails/normal/51048a1138d61df87bf3fdc7deed50e3.png/WebpageIcons.db
  (inode #27528105, mod time Mon Jan 13 02:50:08 2014)
  Clone multiply-claimed blocks<y>? yes
  clone_file_block: internal error: can't find dup_blk for 73467268

  clone_file_block: internal error: can't find dup_blk for 73467268

  File
  /home/user/.thumbnails/normal/51048a1138d61df87bf3fdc7deed50e3.png/WebpageIcons.db
  (inode #27528105, mod time Mon Jan 13 02:50:08 2014)
    has 7 multiply-claimed block(s), shared with 1 file(s):
          /home/user/dir/subdir/05.09.2013_13.15.48.300.jpg
  (inode #27528089, mod time Mon Jan 13 02:50:08 2014)
  Multiply-claimed blocks already reassigned or cloned.

  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  root: ***** FILE SYSTEM WAS MODIFIED *****
  root: 1038356/30285824 files (0.3% non-contiguous), 106319516/121119454 blocks

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