extundelete - How to solve 'Block bitmap checksum does not match bitmap when trying to examine filesystem'?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
The OS is Ubuntu 17.10 and I've been trying to recover(undelete) with extundelete.
(The File System is ext4.)
This didn't work. So, I tried with
extundelete /dev/mapper/ubuntu--vg-root --restore-file /home/chan/origol/routes/user.js
And It worked.
However, I got another problem.
Loading filesystem metadata ... extundelete: Block bitmap checksum does not match bitmap when trying to examine filesystem
I couldn't find any information about it. How can I solve this problem?
linux data-recovery ext4 forensics extundelete
add a comment |Â
up vote
0
down vote
favorite
The OS is Ubuntu 17.10 and I've been trying to recover(undelete) with extundelete.
(The File System is ext4.)
This didn't work. So, I tried with
extundelete /dev/mapper/ubuntu--vg-root --restore-file /home/chan/origol/routes/user.js
And It worked.
However, I got another problem.
Loading filesystem metadata ... extundelete: Block bitmap checksum does not match bitmap when trying to examine filesystem
I couldn't find any information about it. How can I solve this problem?
linux data-recovery ext4 forensics extundelete
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The OS is Ubuntu 17.10 and I've been trying to recover(undelete) with extundelete.
(The File System is ext4.)
This didn't work. So, I tried with
extundelete /dev/mapper/ubuntu--vg-root --restore-file /home/chan/origol/routes/user.js
And It worked.
However, I got another problem.
Loading filesystem metadata ... extundelete: Block bitmap checksum does not match bitmap when trying to examine filesystem
I couldn't find any information about it. How can I solve this problem?
linux data-recovery ext4 forensics extundelete
The OS is Ubuntu 17.10 and I've been trying to recover(undelete) with extundelete.
(The File System is ext4.)
This didn't work. So, I tried with
extundelete /dev/mapper/ubuntu--vg-root --restore-file /home/chan/origol/routes/user.js
And It worked.
However, I got another problem.
Loading filesystem metadata ... extundelete: Block bitmap checksum does not match bitmap when trying to examine filesystem
I couldn't find any information about it. How can I solve this problem?
linux data-recovery ext4 forensics extundelete
asked Jul 10 at 17:25
Chanjung Kim
12
12
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
You probably have the metadata_csum
feature enabled in your filesystem, but extundelete
does not understand this feature and is not updating the block bitmap checksum when it is modifying it to indicate the blocks from the undeleted file are again in use. That said, extundelete
shouldn't be modifying a filesystem that has features it does not understand, since this can lead to more significant filesystem corruption.
You should be able to fix this by running e2fsck -fy
on the filesystem. It would probably also be worthwhile to submit a bug report (ideally with an accompanying patch) to the extundelete
author/maintainer to both fix it to compute the metadata checksums, as well as ensure that it does not try to open filesystems for which it does not understand INCOMPAT
features, and only allow read-only opens for filesystems with RO_COMPAT
features.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You probably have the metadata_csum
feature enabled in your filesystem, but extundelete
does not understand this feature and is not updating the block bitmap checksum when it is modifying it to indicate the blocks from the undeleted file are again in use. That said, extundelete
shouldn't be modifying a filesystem that has features it does not understand, since this can lead to more significant filesystem corruption.
You should be able to fix this by running e2fsck -fy
on the filesystem. It would probably also be worthwhile to submit a bug report (ideally with an accompanying patch) to the extundelete
author/maintainer to both fix it to compute the metadata checksums, as well as ensure that it does not try to open filesystems for which it does not understand INCOMPAT
features, and only allow read-only opens for filesystems with RO_COMPAT
features.
add a comment |Â
up vote
0
down vote
You probably have the metadata_csum
feature enabled in your filesystem, but extundelete
does not understand this feature and is not updating the block bitmap checksum when it is modifying it to indicate the blocks from the undeleted file are again in use. That said, extundelete
shouldn't be modifying a filesystem that has features it does not understand, since this can lead to more significant filesystem corruption.
You should be able to fix this by running e2fsck -fy
on the filesystem. It would probably also be worthwhile to submit a bug report (ideally with an accompanying patch) to the extundelete
author/maintainer to both fix it to compute the metadata checksums, as well as ensure that it does not try to open filesystems for which it does not understand INCOMPAT
features, and only allow read-only opens for filesystems with RO_COMPAT
features.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
You probably have the metadata_csum
feature enabled in your filesystem, but extundelete
does not understand this feature and is not updating the block bitmap checksum when it is modifying it to indicate the blocks from the undeleted file are again in use. That said, extundelete
shouldn't be modifying a filesystem that has features it does not understand, since this can lead to more significant filesystem corruption.
You should be able to fix this by running e2fsck -fy
on the filesystem. It would probably also be worthwhile to submit a bug report (ideally with an accompanying patch) to the extundelete
author/maintainer to both fix it to compute the metadata checksums, as well as ensure that it does not try to open filesystems for which it does not understand INCOMPAT
features, and only allow read-only opens for filesystems with RO_COMPAT
features.
You probably have the metadata_csum
feature enabled in your filesystem, but extundelete
does not understand this feature and is not updating the block bitmap checksum when it is modifying it to indicate the blocks from the undeleted file are again in use. That said, extundelete
shouldn't be modifying a filesystem that has features it does not understand, since this can lead to more significant filesystem corruption.
You should be able to fix this by running e2fsck -fy
on the filesystem. It would probably also be worthwhile to submit a bug report (ideally with an accompanying patch) to the extundelete
author/maintainer to both fix it to compute the metadata checksums, as well as ensure that it does not try to open filesystems for which it does not understand INCOMPAT
features, and only allow read-only opens for filesystems with RO_COMPAT
features.
answered Jul 11 at 5:23
LustreOne
2998
2998
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454536%2fextundelete-how-to-solve-block-bitmap-checksum-does-not-match-bitmap-when-try%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password