I didn't actually apply these patches directly. I updated mine (0.1.15) manually. Read the man page of dd. The size of the file that dd creates is equal to the product of the blocksize and the count. In the 0.1.11 the block size is 1 byte and the count is 'persist' (ie the number of bytes you wanted your persistence file to be). Having a block size of 1 byte was problematic and that prompted this bug report. Apparently later someone decided to fix it but swung things to the opposite extreme. So you see in 0.1.16 that now the blocksize is set to 'persist' (the size you want) and the count is set to 1. So instead of a huge number of blocks that are too small, now it is trying to make a single block that is too large (dd won't allow > 2GB). To fix this you set the block size to something appropriate like in the 1KB-1MB range for most common cases, and then you calculate the count so that it gives you the filesize you requested.
If you look at John Gruber's patch at the top of this bug report you see this change: popen(['dd', 'if=/dev/zero', 'bs=1024', 'of=%s/casper-rw' % target, 'count=%s' % (persist/1024)]) He set the block size to 1024 (ie 1 KB) and the count is set to persist/1024 (ie the size of your persitence file divided by the blocksize). That is why I referred to this thread in my bug report. This patch for the old problem in 0.1.11 is correct and what is currently in 0.1.16 is incorrect. -- Persistence Slider Wrong; Takes more than 3 hours to produce largest persistence file https://bugs.launchpad.net/bugs/321544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
