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

[Launchpad Bug Tracker]

This bug was fixed in the package e2fsprogs - 1.42-1ubuntu2.3

---
e2fsprogs (1.42-1ubuntu2.3) precise; urgency=low

  * fix rule-violating lblk->pblk mappings on bigalloc filesystems (LP:
#1321418)

 -- Seyeong Kim   Tue, 01 Sep 2015 10:57:56
-0500

** Changed in: e2fsprogs (Ubuntu Precise)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Fix Released

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? 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

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package e2fsprogs - 1.42.9-3ubuntu1.3

---
e2fsprogs (1.42.9-3ubuntu1.3) trusty; urgency=medium

  * fix rule-violating lblk->pblk mappings on bigalloc filesystems (LP:
#1321418)

 -- Seyeong Kim   Tue, 01 Sep 2015 07:08:12
-0500

** Changed in: e2fsprogs (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Fix Released

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? 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

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

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

[Chris J Arges]

Hello Forest, or anyone else affected,

Accepted e2fsprogs into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/e2fsprogs/1.42.9-3ubuntu1.3 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

-- 
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:
  Fix Committed
Status in e2fsprogs source package in Trusty:
  Fix Committed

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? 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:

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

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/precise-proposed/e2fsprogs

** Branch linked: lp:ubuntu/trusty-proposed/e2fsprogs

-- 
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:
  Fix Committed
Status in e2fsprogs source package in Trusty:
  Fix Committed

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? 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

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

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

[Forest]

Chris, I have no way to test this, because I no longer have a filesystem
with multiply-claimed blocks.

-- 
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:
  Fix Committed
Status in e2fsprogs source package in Trusty:
  Fix Committed

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? 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

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

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

[Simon Déziel]

This verified fine on Precise and Trusty using the FS image from comment
#6. Thank you

** 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 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:
  Fix Committed
Status in e2fsprogs source package in Trusty:
  Fix Committed

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? 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

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

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

[Chris J Arges]

Sponsored for P/T.

-- 
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? 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

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

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

[Seyeong Kim]

** 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 blocksy? 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 

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

[Seyeong Kim]

** Patch added: trusty-fix-multiply-claimed.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4454739/+files/trusty-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 blocksy? 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

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

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

[Louis Bouchard]

** Also affects: e2fsprogs (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: e2fsprogs (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: e2fsprogs (Ubuntu Precise)
   Importance: Undecided
   Status: New

** No longer affects: e2fsprogs (Ubuntu Vivid)

-- 
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:
  In Progress
Status in e2fsprogs source package in Precise:
  New
Status in e2fsprogs source package in Trusty:
  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 blocksy? 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

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

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

[Rafael David Tinoco]

Hello, for all those interested..

I'll be providing the fix by backporting/cherry-picking commit
9a1d614df217 from upstream mentioned by Theo so we can create a SRU for
this...

inaddy@xxx:~/sources/upstream/e2fsprogs$ git tag --contains 9a1d614df217
v1.42.12

From rmadison all affected versions are:

- Precise (1.42-1ubuntu2.2)
- Trusty (1.42.9-3ubuntu1.2)
- Utopic (1.42.10-1.1ubuntu1)

Vivid is ok (1.42.12-1ubuntu2)

I already cherry-picked the commit and I'm solving conflicts. Then I'll
test the fsck with the image provided by Theo to see if it solves the
issue and ask for SRU.

Thank you!

Rafael Tinoco

** Changed in: e2fsprogs (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: e2fsprogs (Ubuntu)
 Assignee: Theodore Ts'o (tytso) = Rafael David Tinoco (inaddy)

** Tags added: cts

-- 
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:
  In Progress

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 blocksy? 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

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

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

[Rafael David Tinoco]

Okay, I have provided one PPA for precise for this particular case:

https://launchpad.net/~inaddy/+archive/ubuntu/lp1321418

Cherry-picking 2 needed patches from upstream.

I have tested also the fsck with the filesystem that Theo provided and
version from PPA fixes the problems.

Second fsck run shows:

inaddy@xxx:~/filesystem$ fsck.ext4 -f ./f_dup5.img
e2fsck 1.42 (29-Nov-2011)
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
./f_dup5.img: 13/16 files (15.4% non-contiguous), 65/100 blocks

No errors.

I'm waiting for feedback from some users to provide debdiffs to be
proposed as SRU for Precise, Trusty and Utopic.

Thank you very much for reporting this.

Rafael Tinoco

-- 
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:
  In Progress

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 blocksy? 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

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

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

[bigeel]

Hi Theodore,

thanks for your really fast answer. I do not know how to get fsck version 
number, but I had the following output:
  fsck from util-linux 2.20.1
  e2fsck 1.42 (29-Nov-2011)


However I have run `e2fsck f_dup5.img` on your attachment at #6, and no error 
was reported, so I do not know how if I can trust the 1.42 (29-Nov-2011) part:
  e2fsck 1.42 (29-Nov-2011)
  f_dup5.img: clean, 13/16 files, 43/100 blocks

  
Anyway, I do not think I am willing to run fsck again as it takes 4 days to 
complete, and the data is not that important.

What I am more worried about is what could have caused it, and how serious this 
is. Do you have a clue? 
Would deleting (or cp file bak; rm file; mv bak file) solve the problem? 
(at least I have done some cp/rm and the number of errors decreased, but I 
wonder whether it’s just shallow or the real problem is gone)

Best

-- 
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:
  Confirmed

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 blocksy? 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

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

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

[Theodore Ts'o]

The file system which I posted  in #6 no longer triggers a bug in
1.42.12.   It looks like it was fixed as a side effect of commit
9a1d614df217.  @bigeel, what version of e2fsck were you using?
Could you try using e2fsprogs 1.42.12 and see if that fixes the problem
for you?

Thanks!!

-- 
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:
  Confirmed

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 blocksy? 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

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

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

[bigeel]

Hi,
I had the same error message doing while fsck'ing one of my disks.

I did not understand well the cause of the problem. Is fsck what caused
the file-system corruption? (because of an extent-mapped inode getting
written (or copied) to a different/wrong place in the inode table?)

This ticket is labelled e2fsprogs. May you explain if the planned fix is:
- to avoid file-system corruption
- to enable fsck to fix it
(- something else?)
 please?

-- 
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:
  Confirmed

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 blocksy? 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

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