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 (Ubun
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 Pre
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321418
Title:
fsck.ext4 fails to fix multiply-cl
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321418
Title:
fsck.ext4 fails to fix mult
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
ht
Sponsored for P/T.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321418
Title:
fsck.ext4 fails to fix multiply-claimed blocks: can't find dup_blk
To manage notifications about this bug go to:
http
** 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 P
** 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
Bugs, which is subscribed to Ubuntu.
h
** 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 (Ub
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 ru
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
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
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 r
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 i
That's great news. Thanks for the quick response!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321418
Title:
fsck.ext4 fails to fix multiply-claimed blocks: can't find dup_blk
To manage notificat
** Attachment added: "File system image with repro."
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321418/+attachment/4116503/+files/f_dup5.img.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Thanks, I was able to reproduce the problem using a test file system.
The problem appears to have been caused by an extent-mapped inode
getting written (or copied) to a different/wrong place in the inode
table. I should be able to get this fixed now that I have a simple
repro.
** Changed in: e2fs
Yeah, sorry about that. If I had known you were likely to respond so
quickly, I might have left it alone until I heard from you.
dumpe2fs 1.42.8 (20-Jun-2013)
Filesystem volume name: root
Last mounted on: /
Filesystem UUID: 3dd3e793-f873-4db2-8c68-801b217ba06e
Filesystem magic
Right, I didn't notice the first time I read the bug report you had
already deleted the inode to fix the problem. It would have been nice
to have gotten a look at the inode in question so I could really see
what was going on.
The "internal error: can't find dup_blk" error is one of those "this
sh
(Keep in mind that I'm running debugfs after having deleted the file at
inode 27528089 using rm.)
debugfs: stat <27528105>
Inode: 27528105 Type: regularMode: 0600 Flags: 0x8
Generation: 2927505238Version: 0x:0001
User: 1000 Group: 1000 Size: 28672
File ACL: 0
Can you send me the output of the following:
debugfs /dev/md/1
debugfs: stat <27528105>
debugfs: stat <27528089>
debugfs: quit
Thanks!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321418
Title:
22 matches
Mail list logo