Menu
▾
▴
Re: [Astlinux-devel] Home Gateway Appliance - Issue with Free Space during Startup
|
From: Ramesh GK <ram...@ho...> - 2020-12-08 00:59:49
|
Thanks, Lonnie. Updating the MAX_IMAGEFS_SIZE resolved the problem and I have not seen any further issues. Thanks much for the quick response. Thanks Ramesh GK Phone: 408-462-0408 Strive not to be a success but rather to be of value - Albert Einstein ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Monday, December 7, 2020 12:15 PM To: AstLinux Developers Mailing List <ast...@li...> Subject: Re: [Astlinux-devel] Home Gateway Appliance - Issue with Free Space during Startup Hi David, We could ... but 192m gives us a little margin for the 256 MB FAT16 partition, and we have eaten into that margin recently. 1) Updating to Syslinux 6 (and memtest) used more space at the base. 2) As the size of RUNNIX increases, it uses more space, now about 9 MB each, we support a revert version, 18 MB total. 3) We now supply a unique initrd (astlinux-*.initrd.img) for every run image instead of just one shared, that added about 4 MB to the FAT16 partition. Currently our largest standard image is the Asterisk 16 build, which has a RAM based read-only filesystem of 137.2 MB, so the current limit of 192 MB offers significant headroom at the moment. Back to the 256 MB FAT16 partition needs: Syslinux 6 (and memtest): 0.5 MB RUNNIX (current): 9 MB RUNNIX (previous): 9 MB initrd (current): 4 MB initrd (previous): 4 MB So that leaves 229.5 MB to be shared by two compressed os/*.run images, a 256m value with 100 MB each max (compressed), yields less than 30 MB headroom, it would be getting tight, about only 10% free. The current 192m yields 74 MB each max (compressed), which gives us 81 MB of headroom out of the 256 MB FAT16 partition. I don't see us eating onto the 256 MB FAT16 partition other than the os/*.run images, but you never know. Good to do these calculations for time to time. Lonnie > On Dec 7, 2020, at 9:35 AM, David Kerr <da...@ke...> wrote: > > Maybe we should just make the default build 256 MB. There can't be many systems now-a-days that could not accommodate that? > > David. > > On Mon, Dec 7, 2020 at 10:03 AM Lonnie Abelbeck <li...@lo...> wrote: > > > > On Dec 7, 2020, at 8:18 AM, Lonnie Abelbeck <li...@lo...> wrote: > > > >> > >> On Dec 6, 2020, at 10:54 PM, Ramesh GK <ram...@ho...> wrote: > >> > >> Hi, > >> > >> I started working on building some additions on top of astlinux 1.3.10 distribution without modifications to base packages and bumped into a strange issue after successful installation to the target system. > >> > >> During startup after loading the kernel, I am receiving the below message. > >> > >> Copying AstLinux files to RAM... > >> ... > >> ... > >> ... > >> cp: write error: no space left of device. > >> cp: write error: no space left of device. > >> cp: write error: no space left of device. > >> cp: write error: no space left of device. > >> cp: write error: no space left of device. > >> > >> After the above messages for some time it shows a bunch of errors and comes to a truncated login screen without any info that is normally shown at login prompt. > >> > >> I tried to increase the size during astlinux-makeimage creation from 256 to 512 which did not help. > >> > >> please let know if you have any ideas on how to resolve this issue. > >> > >> Thanks > >> Ramesh GK > > > > By default, the upper limit to the RAM based read-only filesystem is 192 MB (uncompressed). > > > > This can be increased by bumping the MAX_IMAGEFS_SIZE variable in two places: > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fastlinux-project%2Fastlinux%2Fblob%2Fmaster%2Fscripts%2Fbuild%23L6&data=04%7C01%7C%7Cebb697e18fcd44d677fe08d89ad3cd35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637429581755928094%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4W4ajH4gMW5CG0sqFXVw1gD2bmx%2BOLxkRdVKrR08ixU%3D&reserved=0 > > -- > > MAX_IMAGEFS_SIZE=196608 # 192m > > -- > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fastlinux-project%2Fastlinux%2Fblob%2Fmaster%2Fproject%2Finitrd%2Ftarget_skeleton%2Flinuxrc%23L6&data=04%7C01%7C%7Cebb697e18fcd44d677fe08d89ad3cd35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637429581755928094%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l6OoQH%2Bslcql1bvOeSThwjrtIOHucv85p%2FYKJ9KzhNE%3D&reserved=0 > > -- > > MAX_IMAGEFS_SIZE=196608 # 192m > > -- > > > > Then, to rebuild the initrd, simply "rm initrd.img", and the next "./scripts/build/" will rebuild the initrd.img file. > > > > I would suggest 256m, which is 256*1024 = 262144 > > -- > > MAX_IMAGEFS_SIZE=262144 # 256m > > -- > > > > Lonnie > > Replying to myself while I'm thinking about it ... > > The MAX_IMAGEFS_SIZE is also coupled with the size of the FAT16 partition size, 256 MB by default. > > We want to accommodate two (compressed) os/*.run images so we can revert-to-previous firmware. > > The uncompressed RAM size is around 2.6x the compressed size, so a 256m limit would result in approximately 100 MB compressed images, which should still work for two on a 256 MB FAT16 partition. > > Any higher value MAX_IMAGEFS_SIZE beyond 256m would require a larger FAT16 partition size if supporting two (compressed) os/*.run images is maintained. > > BTW, if no DAHDI hardware cards are used, setting BR2_PACKAGE_DAHDI_NO_CARD_FIRMWARE=y in .config will reduce the RAM based read-only filesystem by 8.8 MB. > > Lonnie > > > > > > > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=04%7C01%7C%7Cebb697e18fcd44d677fe08d89ad3cd35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637429581755928094%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=z7LPJgzXTB5%2FarC67WsQdAzMhVAAj%2BpTSRXHZ%2FN7v7c%3D&reserved=0 > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=04%7C01%7C%7Cebb697e18fcd44d677fe08d89ad3cd35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637429581755928094%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=z7LPJgzXTB5%2FarC67WsQdAzMhVAAj%2BpTSRXHZ%2FN7v7c%3D&reserved=0 _______________________________________________ Astlinux-devel mailing list Ast...@li... https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fastlinux-devel&data=04%7C01%7C%7Cebb697e18fcd44d677fe08d89ad3cd35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637429581755938089%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=V21vO%2Be90tODE0Sd%2BIOIj8j2J08imOYOqY5h8dm1n%2B0%3D&reserved=0 |
