| 2014-05-20 19:01:37 |
Forest |
bug |
|
|
added bug |
| 2014-05-20 19:02:02 |
Forest |
summary |
fsck.ext4 fails to fix multiply-claimed blocks |
fsck.ext4 fails to fix multiply-claimed blocks: can't find dup_blk |
|
| 2014-05-21 03:11:31 |
Theodore Ts'o |
e2fsprogs (Ubuntu): status |
New |
Confirmed |
|
| 2014-05-21 03:11:31 |
Theodore Ts'o |
e2fsprogs (Ubuntu): assignee |
|
Theodore Ts'o (tytso) |
|
| 2014-05-21 03:12:30 |
Theodore Ts'o |
attachment added |
|
File system image with repro. https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4116503/+files/f_dup5.img.gz |
|
| 2014-09-28 22:20:21 |
Venelin |
bug |
|
|
added subscriber Venelin |
| 2014-11-10 12:42:53 |
Don Bowman |
bug |
|
|
added subscriber Don Bowman |
| 2015-04-07 10:37:17 |
Florian |
bug |
|
|
added subscriber Florian |
| 2015-04-14 17:48:54 |
Rafael David Tinoco |
e2fsprogs (Ubuntu): status |
Confirmed |
In Progress |
|
| 2015-04-14 17:48:59 |
Rafael David Tinoco |
e2fsprogs (Ubuntu): assignee |
Theodore Ts'o (tytso) |
Rafael David Tinoco (inaddy) |
|
| 2015-04-14 17:49:15 |
Rafael David Tinoco |
tags |
|
cts |
|
| 2015-08-28 10:21:32 |
Louis Bouchard |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-08-28 10:21:32 |
Louis Bouchard |
bug task added |
|
e2fsprogs (Ubuntu Trusty) |
|
| 2015-08-28 10:21:32 |
Louis Bouchard |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-08-28 10:21:32 |
Louis Bouchard |
bug task added |
|
e2fsprogs (Ubuntu Vivid) |
|
| 2015-08-28 10:21:32 |
Louis Bouchard |
nominated for series |
|
Ubuntu Precise |
|
| 2015-08-28 10:21:32 |
Louis Bouchard |
bug task added |
|
e2fsprogs (Ubuntu Precise) |
|
| 2015-08-28 10:21:51 |
Louis Bouchard |
bug task deleted |
e2fsprogs (Ubuntu Vivid) |
|
|
| 2015-08-31 01:21:08 |
Seyeong Kim |
e2fsprogs (Ubuntu): status |
In Progress |
Invalid |
|
| 2015-08-31 01:21:11 |
Seyeong Kim |
e2fsprogs (Ubuntu Precise): status |
New |
In Progress |
|
| 2015-08-31 01:21:13 |
Seyeong Kim |
e2fsprogs (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2015-08-31 01:21:14 |
Seyeong Kim |
e2fsprogs (Ubuntu Trusty): status |
Incomplete |
In Progress |
|
| 2015-08-31 01:21:19 |
Seyeong Kim |
e2fsprogs (Ubuntu Precise): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2015-08-31 01:21:21 |
Seyeong Kim |
e2fsprogs (Ubuntu Trusty): assignee |
|
Seyeong Kim (xtrusia) |
|
| 2015-08-31 01:21:25 |
Seyeong Kim |
e2fsprogs (Ubuntu): assignee |
Rafael David Tinoco (inaddy) |
|
|
| 2015-08-31 01:25:45 |
Seyeong Kim |
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 |
[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 |
|
| 2015-08-31 01:26:19 |
Seyeong Kim |
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 |
[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 |
|
| 2015-08-31 01:27:20 |
Seyeong Kim |
tags |
cts |
sts |
|
| 2015-08-31 01:27:32 |
Seyeong Kim |
attachment added |
|
precise-fix-multiply-claimed.debdiff https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4454738/+files/precise-fix-multiply-claimed.debdiff |
|
| 2015-08-31 01:27:48 |
Seyeong Kim |
attachment added |
|
trusty-fix-multiply-claimed.debdiff https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4454739/+files/trusty-fix-multiply-claimed.debdiff |
|
| 2015-08-31 01:28:16 |
Seyeong Kim |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-08-31 01:28:44 |
Seyeong Kim |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2015-09-01 16:04:29 |
Chris J Arges |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2015-09-09 15:58:33 |
Chris J Arges |
e2fsprogs (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2015-09-09 15:58:35 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2015-09-09 15:58:45 |
Chris J Arges |
tags |
sts |
sts verification-needed |
|
| 2015-09-09 15:59:33 |
Chris J Arges |
e2fsprogs (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2015-09-09 16:18:46 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/e2fsprogs |
|
| 2015-09-09 16:18:50 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/e2fsprogs |
|
| 2015-09-09 18:03:44 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2015-09-09 18:11:50 |
Simon Déziel |
tags |
sts verification-needed |
sts verification-done |
|
| 2015-09-16 17:44:44 |
Launchpad Janitor |
e2fsprogs (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2015-09-16 17:44:50 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-09-16 17:45:20 |
Launchpad Janitor |
e2fsprogs (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2015-09-24 09:39:38 |
Jouan Oceane |
e2fsprogs (Ubuntu): assignee |
|
Jouan Oceane (jouanoceane) |
|
| 2015-09-24 09:39:47 |
Jouan Oceane |
e2fsprogs (Ubuntu): assignee |
Jouan Oceane (jouanoceane) |
|
|
