extfsclone.c: bitmap error at xx group
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
I want to clone a ext4 filesystem which ends in the following error:
Partclone v0.2.89 http://partclone.org
Starting to clone device (/dev/sda1) to image (-)
Reading Super Block
we need memory: 15270312 bytes
image head 4160, bitmap 15262052, crc 4100 bytes
Calculating bitmap... Please wait... extfsclone.c: bitmap error at 17 group.
Partitioning:
~# sfdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x6c6583c4
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 976773167 976771120 465.8G 83 Linux
Diskinfo:
Model Family: Western Digital Blue Mobile
Device Model: WDC WD5000LPVX-22V0TT0
Serial Number: WD-WXB1A45580UJ
LU WWN Device Id: 5 0014ee 605ce1d84
Firmware Version: 01.01A01
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Jul 21 10:27:40 2016 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
When I format the partition as ext3, cloning is possible without any errors. I think this is a bug.
Additional information:
The ext4 filesystem is fully initialized at the time of cloning.
"Calculating bitmap... Please wait... extfsclone.c: bitmap error at 17 group." ->
Did you try to choose the opton "-fsck-y" (or -fsck-src-part-y for older version of Clonezilla live) when saving an image?
Steven
Yes, I checked the filesystem with the clonezilla option and also before
cloning with e2fsck -f. The filesystem was clean.
Even if the partition was fresh formatted with no data on it, this error
remains.
Klaus
Steven Shiau schrieb am 24.07.2016 um 06:32:
Related
Bugs:
#256Could you please tell us in detail how you create that Ext4 file system? On which verson of GNU/Linux, and how you create that. We'd like to reproduce the issue here, and if it's reproducible, it could be fixed.
Thanks.
Steven
I do not own this disk and notebook any more but because of the very new
hardware it was necessary to install a Debian jessie backports kernel
linux-image-4.6.0-0.bpo.1-amd64 (4.6.3-1~bpo8+1)
I tried 2 methods to create the ext4 filesystem, both with the same result:
mkfs.ext4 /dev/sda1
and
mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/sda1
Klaus
Steven Shiau schrieb am 07.08.2016 um 05:48:
Related
Bugs:
#256This is weird. I just could not reproduce this issue here. Attached you can find the results about formating /dev/sda1 as ext4 and saving it as an image successfully.
Which version of mkfs.ext4 did you use?
Steven
Hello Steven,
thanks for testing.
As I'm not able to provide further details any more and because you
cannot reproduce this behavior my bug report may be closed.
Klaus
Steven Shiau schrieb am 09.08.2016 um 14:57:
Related
Bugs:
#256OK, thanks.
Steven