f2fs filesystem in bmap-tool
Alfredo Pons
alfredo.pons at gmail.com
Wed Jul 22 08:30:27 PDT 2015
Hello,
The bmap-tool (version 3.2) reort this:
root at atlantis:/home/apons/plastia# bmaptool create -o bmap
intool-jessie-0.1.img
bmaptool: WARNING: all 7.2 GiB are mapped, no holes in
'intool-jessie-0.1.img'
bmaptool: WARNING: was the image handled incorrectly and holes were
expanded?
And the partions of image are:
Disk /dev/sdc: 3.7 GiB, 3904897024 bytes, 7626752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x50446648
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 249855 247808 121M c W95 FAT32 (LBA)
/dev/sdc2 249856 2347007 2097152 1G 83 Linux
/dev/sdc3 2347008 7626751 5279744 2.5G 83 Linux
First partition ais vfat (/booy).
Second partition is ext4 (/).
Third partition is fsfs.
Regards.
Alfredo Pons
Mòbil: 637367156
Blog: http://gnodebian.blogspot.com.es/
CV: http://es.linkedin.com/in/alfredopons
2015-07-22 8:53 GMT+02:00 Artem Bityutskiy <dedekind1 at gmail.com>:
> On Mon, 2015-07-20 at 13:35 +0200, Alfredo Pons wrote:
> > It is planned to work with the f2fs filesystem?
> > Currently it is not supported.
>
> Do you want to use f2fs on the build host (the image is created on a
> host which uses f2fs) or you want the image to contain f2fs, while the
> build host uses something else like ext4?
>
> Or please, elaborate some more what do you mean by not supported, what
> are the symptoms?
>
> From the build host side, bmap-tools relies on the FIEMAP or FIBMAP
> ioctls. Does f2fs support them, if yes, then there should be no
> problem. Otherwise, we'd need to see if f2fs offers any alternatives to
> these ioctls.
>
> Thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/bmap-tools/attachments/20150722/ce9713dc/attachment.html>
More information about the Bmap-tools
mailing list