Public bug reported:
Binary package hint: e2fsprogs
"logdump -b<block>" command in debugfs show incorrect allocation status
in block bitmap
== Step to repeat ==
$ debugfs /dev/sda1
debugfs: logdump -b1827766
== What happens ==
It always report "block is SET" like this,
FS block 1802240 logged at journal block 14742 (flags 0x2)
(block bitmap for block 1827766: block is SET)
FS block 1802240 logged at journal block 14749 (flags 0x2)
(block bitmap for block 1827766: block is SET)
== What should happen ==
It should show SET or CLEAR correspond to the bitmap logged in the journal like
this,
FS block 1802240 logged at journal block 14742 (flags 0x2)
(block bitmap for block 1827766: block is CLEAR)
FS block 1802240 logged at journal block 14749 (flags 0x2)
(block bitmap for block 1827766: block is SET)
== How to fix ==
The attachment is the patch to fix this.
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
--
debugfs: logdump -b<block> show incorrect allocation status in block bitmap
https://bugs.launchpad.net/bugs/501686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
