#48 fix logdump -b<block> to show correct allocation status

open
nobody
None
5
2012-11-28
2010-01-07
No

This fix the bug,
https://sourceforge.net/tracker/?func=detail&aid=2927365&group_id=2406&atid=102406

"logdump -b<block>" command in debugfs show incorrect allocation status in
block bitmap

== What happens ==
$ debugfs /dev/sda1
debugfs: logdump -b1827766

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)

Discussion