touch-packages team mailing list archive

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

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Seyeong Kim <seyeong.kim@xxxxxxxxxxxxx>
Date: Mon, 31 Aug 2015 01:27:32 -0000
Reply-to: Bug 1321418 <1321418@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
** Changed in: e2fsprogs (Ubuntu)
       Status: In Progress => Invalid

** Changed in: e2fsprogs (Ubuntu Precise)
       Status: New => In Progress

** Changed in: e2fsprogs (Ubuntu Trusty)
       Status: New => Incomplete

** Changed in: e2fsprogs (Ubuntu Trusty)
       Status: Incomplete => In Progress

** Changed in: e2fsprogs (Ubuntu Precise)
     Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: e2fsprogs (Ubuntu Trusty)
     Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: e2fsprogs (Ubuntu)
     Assignee: Rafael David Tinoco (inaddy) => (unassigned)

** Description changed:

+ [SRU justification]
+ 
+ [Impact]
+ 
  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.
+ 
+ [Test Case]
  
  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
+   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
+   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
+ 
+ [Regression Potential]
+ 
+ [Other Info]
+ 
+ backported from upstream

** Description changed:

  [SRU justification]
  
  [Impact]
  
  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.
  
  [Test Case]
  
  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
  
  [Regression Potential]
  
  [Other Info]
  
  backported from upstream
+ https://kernel.googlesource.com/pub/scm/fs/ext2/e2fsprogs/+/9a1d614df217c02ea6b2cb0072fccfe706aea111
+ https://kernel.googlesource.com/pub/scm/fs/ext2/e2fsprogs/+/84397754250d13e8596dd68c157c4c9863800079%5E%21/#F0

** Tags removed: cts
** Tags added: sts

** Patch added: "precise-fix-multiply-claimed.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4454738/+files/precise-fix-multiply-claimed.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Invalid
Status in e2fsprogs source package in Precise:
  In Progress
Status in e2fsprogs source package in Trusty:
  In Progress

Bug description:
  [SRU justification]

  [Impact]

  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.

  [Test Case]

  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

  [Regression Potential]

  [Other Info]

  backported from upstream
  https://kernel.googlesource.com/pub/scm/fs/ext2/e2fsprogs/+/9a1d614df217c02ea6b2cb0072fccfe706aea111
  https://kernel.googlesource.com/pub/scm/fs/ext2/e2fsprogs/+/84397754250d13e8596dd68c157c4c9863800079%5E%21/#F0

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