12235 2017-10-18 12:43:16 +0000 image.bbclass: Consider adding --apparent-size to du -ks for get_rootfs_size 2018-01-11 15:54:40 +0000 1 1 7 Build System, Metadata & Runtime OE-Core deployment 5.99 All Multiple RESOLVED DUPLICATE 8430 Medium+ normal 2.5 M1 1 net147 maxin.john randy.macleod ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 77656 0 net147 2017-10-18 12:43:16 +0000 Consider changing du -ks to du --apparent-size -ks for more reproducible builds. I get slightly different results running du -ks on a btrfs filesystem with compress-force=lzo compared to an ext4 filesystem. btrfs: $ wget http://www.tpg.com.au/test3.iso $ du --apparent-size -ks test3.iso 51102 test3.iso $ du -ks test3.iso 51104 test3.iso ext4: $ wget http://www.tpg.com.au/test3.iso $ du --apparent-size -ks test3.iso 51102 test3.iso $ du -ks test3.iso 51108 test3.iso 77704 1 ross.burton 2017-10-19 14:44:55 +0000 As we're getting the size of a single file, we could just use stat() right? 77718 2 net147 2017-10-19 22:14:53 +0000 (In reply to comment #1) > As we're getting the size of a single file, we could just use stat() right? It is calculating size for a directory not a single file. 77723 3 ross.burton 2017-10-20 07:50:45 +0000 Yes, sorry, I was thinking of the wrong variable. Note that you'll still get differences with --apparent-size thanks to the directory inodes being of variable size. 78287 4 maxin.john 2017-11-20 12:51:26 +0000 http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144538.html 79030 5 ross.burton 2018-01-11 15:54:40 +0000 Duplicate so marking as such. *** This bug has been marked as a duplicate of bug 8430 ***