Hi Brian,
many thanks for your reply!
I already tried the cleanup-cache parameter without success.
To figure out whats going on I created a completely fresh USB stick with
the 4G image from:
https://us-east.manta.joyent.com/Joyent_Dev/public/SmartDataCenter/usb-latest.tgz
This is the result:
/dev/sdc1 3.7G 2.7G *1.1G* 73%
/run/media/noroot/HEADNODE
du -sh ./*
17K ./LICENSE
1.0K ./application.json
1.0K ./banner
2.5M ./boot
1.3M ./boot_archive.manifest
625K ./cn_tools.tar.gz
4.0K ./config.inc
3.0K ./default
1.7M ./dos
*2.2G ./images*
12K ./manifests
275M ./os
2.0K ./private
177K ./scripts
34M ./sdcadm-install.sh
75K ./services
685K ./tools.tar.gz
218M ./ur-scripts
9.0K ./usb_key.manifest
1.0K ./version
77K ./zones
On a completely fresh and unused stick there is only *1.1 GB *of disk
space left.
Quoting the documentation again:
"Joyent recommends that you keep only the platform images you are
actively using, as each platform image will take up roughly*300MB* of
space on your USB key."
My math is saying that this leaves enough space for 3 images on the
fresh USB stick.
Other directories on the stick that I am actively using also increased a
bit in size, what only left me with enough space for 2 images.
Can't explain whats going on here.
Maybe things are using much more space on my USB sticks than they should?
Anyways, I finally found a way to "expand" the FAT filesystem to use the
whole 16 GB USB stick.
Essentially I used *dd* to copy the image onto the stick as described in
the docs.
Then I used *gparted* to expand the partition, although it fails
expanding the FAT filesystem.
Then I created a new FAT filesystem on the expanded partition with
*mkfs.fat* and default settings.
And finally I copied the files from the image back into that new
partition using *rsync*.
Not the cleanest solution, but it worked and now there is plenty of
space for platform images. :)
Best Regards,
Benjamin
On 07/09/2018 04:45 PM, Brian Bennett wrote:
We haven't modified the image size on ours, and have many more than
two images. You should have plenty of room for at least 10 platform
images.
I suspect that when you remove them, you're only removing them from
the zpool and not from the USB. Run this command:
sdcadm platform remove --all --cleanup-cache
That will remove all images that are /neither/ current or boot
platform for any CN, and will remove them from the USB as well.
--
Brian Bennett
Systems Engineer, Cloud Operations
Joyent, Inc.|www.joyent.com <http://www.joyent.com>
On Jul 8, 2018, at 9:58 AM, Benjamin Beier
<[email protected] <mailto:[email protected]>> wrote:
Hello,
until now I always had 2 platform images on the headnode USB stick.
The one that is currently running and the newer one I am updating to.
As soon as all nodes are running on the new images I can delete the
old one and later pull the next one.
Now for the first time since I provisioned my Triton cloud I ran into
a problem with one platform image not working properly on my compute
nodes.
The headnode is working properly with it, but the compute nodes not.
So essentially both images on the USB stick are in use now.
My idea was to simply pull a third platform image to see if this
might work on the compute nodes.
But I ran into an error message telling me that there is no space
left on the USB device.
This is confusing me quite a bit, as the USB stick was provisioned
exactly as described in the Triton documentation.
The image in the usb-latest.tgz is prepared with 4 GB of size.
I copied it onto a 32 GB USB stick, but of course this does not fix
(expand) the 4 GB partition and filesystem size.
The documentation is saying nothing about expanding the 4 GB image to
fit the whole USB stick.
Nevertheless in the documentation they are always playing with 3 or
more platform images at the same time.
To quote a statement at the bottom of the following page:
https://docs.joyent.com/private-cloud/platform-images
/"Ideally, you will only keep only three platform images"/
Can someone please tell me what I am missing?
How I am supposed to fit more than 2 platform images onto the USB stick?
Best Regards
Benjamin
Begin forwarded message:
From: "Benjamin Beier" <[email protected]
<mailto:[email protected]>>
Subject: [smartos-discuss] Triton installation media size (4GB) and
number of platform images
Date: July 8, 2018 at 9:58:28 AM PDT
To: [email protected]
<mailto:[email protected]>
Reply-To: [email protected]
<mailto:[email protected]>
Hello,
until now I always had 2 platform images on the headnode USB stick.
The one that is currently running and the newer one I am updating to.
As soon as all nodes are running on the new images I can delete the
old one and later pull the next one.
Now for the first time since I provisioned my Triton cloud I ran into
a problem with one platform image not working properly on my compute
nodes.
The headnode is working properly with it, but the compute nodes not.
So essentially both images on the USB stick are in use now.
My idea was to simply pull a third platform image to see if this
might work on the compute nodes.
But I ran into an error message telling me that there is no space
left on the USB device.
This is confusing me quite a bit, as the USB stick was provisioned
exactly as described in the Triton documentation.
The image in the usb-latest.tgz is prepared with 4 GB of size.
I copied it onto a 32 GB USB stick, but of course this does not fix
(expand) the 4 GB partition and filesystem size.
The documentation is saying nothing about expanding the 4 GB image to
fit the whole USB stick.
Nevertheless in the documentation they are always playing with 3 or
more platform images at the same time.
To quote a statement at the bottom of the following page:
https://docs.joyent.com/private-cloud/platform-images
/"Ideally, you will only keep only three platform images"/
Can someone please tell me what I am missing?
How I am supposed to fit more than 2 platform images onto the USB stick?
Best Regards
Benjamin
Begin forwarded message:
From: "Benjamin Beier" <[email protected]
<mailto:[email protected]>>
Subject: [smartos-discuss] Triton installation media size (4GB) and
number of platform images
Date: July 8, 2018 at 9:58:28 AM PDT
To: [email protected]
<mailto:[email protected]>
Reply-To: [email protected]
<mailto:[email protected]>
Hello,
until now I always had 2 platform images on the headnode USB stick.
The one that is currently running and the newer one I am updating to.
As soon as all nodes are running on the new images I can delete the
old one and later pull the next one.
Now for the first time since I provisioned my Triton cloud I ran into
a problem with one platform image not working properly on my compute
nodes.
The headnode is working properly with it, but the compute nodes not.
So essentially both images on the USB stick are in use now.
My idea was to simply pull a third platform image to see if this
might work on the compute nodes.
But I ran into an error message telling me that there is no space
left on the USB device.
This is confusing me quite a bit, as the USB stick was provisioned
exactly as described in the Triton documentation.
The image in the usb-latest.tgz is prepared with 4 GB of size.
I copied it onto a 32 GB USB stick, but of course this does not fix
(expand) the 4 GB partition and filesystem size.
The documentation is saying nothing about expanding the 4 GB image to
fit the whole USB stick.
Nevertheless in the documentation they are always playing with 3 or
more platform images at the same time.
To quote a statement at the bottom of the following page:
https://docs.joyent.com/private-cloud/platform-images
/"Ideally, you will only keep only three platform images"/
Can someone please tell me what I am missing?
How I am supposed to fit more than 2 platform images onto the USB stick?
Best Regards
Benjamin
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: https://www.listbox.com
