Bug 1839

Summary:	mkdosfs fails for filesystems larger than 2GB
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Marc Ferland <marc.ferland>
Component:	devtools / tool chain	Assignee:	Nitin Kamble <nitin.a.kamble>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Low	CC:	jessica.zhang, meta.mr.watcher, meta.watcher, sgw
Version:	1.1
Target Milestone:	1.2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Marc Ferland 2011-12-15 11:57:26 UTC

I was building a development image which includes a lot of packages and the final hddimg failed with:

mkdosfs: seek failed
mkdosfs 2.10 (22 Sep 2003)
ERROR: Function 'build_boot_bin' failed

Manually creating a 2GB filesystem works fine:
tmp/sysroots/x86_64-linux/usr/sbin/mkdosfs -C foo.img 2000000
mkdosfs 2.10 (22 Sep 2003)

Manually creating a 2.1GB filesystem fails with:
tmp/sysroots/x86_64-linux/usr/sbin/mkdosfs -C foo.img 2100000
mkdosfs 2.10 (22 Sep 2003)
mkdosfs: seek failed

So I guess the problem really is mkdosfs.

Comment 1 Nitin Kamble 2011-12-15 12:01:41 UTC

The mkdosfs tool is a hacked up version to create efi partitions, 2gb or  more is too big dos fs for it to handle.

Comment 2 Saul Wold 2012-01-11 15:25:15 UTC

I recently created a 3.5G mkdosfs, can you try again with the recent master, there were some fixes that where added, I was not able to make an dosfs greater than 4G, as Nitin point out this is primarily used for EFI boot creation.  Can you please confirm that you can't build an fs greater than 2G, also check you local fs to make sure oyu have space.

Comment 3 Marc Ferland 2012-01-12 09:16:15 UTC

I tested mkdosfs from poky master branch and it works as expected. I was able to create a file larger than 2GB.

Running the exact same command from the edison branch fails as described earlier. 

Problem solved!
Thanks!

Comment 4 Nitin Kamble 2012-01-12 09:33:56 UTC

I guess upgrade to the newer version has brought new features solving the 2GB barrier. Closing the bug now.