2525 2012-05-31 03:19:15 +0000 dosfstools limits dos filesystems to 2GB 2014-06-23 18:15:52 +0000 1 1 7 Build System, Metadata & Runtime OE-Core deployment unspecified x86 Multiple RESOLVED OBSOLETE Low minor 1.7 1 seebs richard.purdie dvhart eddy.lai.tw meta.mr.watcher meta.watcher --- --- Don't know oldest_to_newest 21765 0 seebs 2012-05-31 03:19:15 +0000 The CFLAGS passed in by Yocto override the -D_FILE_OFFSET_BITS=64 in the Makefile, which causes dosfstools to end up only supporting 2GB filesystems. Workaround is to pass that in via CFLAGS_append. Spotted by mebrown in #yocto, who's on a crunch schedule and hasn't got time to file a formal report. (The -D_FILE_OFFSET_BITS=64 is in OPTFLAGS, which is shoved into CFLAGS in the makefile. I am not sure it should have been considered an optmitization flag to begin with, but...) 29159 1 nitin.a.kamble 2013-01-24 21:44:29 +0000 *** Bug 3779 has been marked as a duplicate of this bug. *** 29235 2 eddy.lai.tw 2013-01-28 13:35:57 +0000 is the workaround to put CFLAGS_append="-D_FILE_OFFSET_BITS=64" in the conf/local.conf then build the image? I have tried to use IMAGE_ROOTFS_EXTRA_SPACE = "1048576" to create a ~1.5GB image, but same failed to boot from USB flash disk. 29239 3 dvhart 2013-01-28 17:28:51 +0000 I believe you would to add something along those lines to a bbappend for the dosfstools recipe, not to local.conf. You can verify by viewing the compile step logs for the package. 30214 4 dvhart 2013-02-28 05:12:48 +0000 Eddy, have you had a chance to try the workaround? 43732 5 richard.purdie 2014-06-03 11:24:24 +0000 The recipe now contains this line, no feedback from the reporter for a couple of years so closing as obsolete, suspected resolved. Reopen if the are still issues.