Out of disk space on dockerized shared hosts #2494
Comments
|
It looks like the disks are full. e.g. from https://ci.nodejs.org/job/node-test-commit-linux-containered/24011/nodes=ubuntu1804_sharedlibs_withoutssl_x64/console the relevant lines are: I'll try removing the 14G/16G workspaces. |
|
I've cleaned up the workspaces for |
|
feel free to clean out all of the workspaces, it's not a huge slowdown to recreate them here (like it is on the Pi hosts) |
|
Out of space again this morning: So the 15G workpaces are back and look to be Debug builds. I don't know what the typical expected workspace size is -- whether the sizes have been creeping up slowly over time or if there's been a recent change to cause a jump. FWIW |
|
I was waiting for the inflight https://ci.nodejs.org/job/node-test-commit-linux-containered/ jobs to complete before manually removing things but it looks like the two most recent builds passed. The current disk space usage with nothing running looks like this: i.e. we only have one 16G (i.e. Debug build) workspace. We're probably seeing flaky behaviour if more than one https://ci.nodejs.org/job/node-test-commit-linux-containered/ is running and we end up with two inflight Debug builds which fills up the disk. |
|
Disk full again, with 15G workspaces on two hosts (suggesting we had concurrent debug builds again):
I've gone and wiped all the workspaces. |
|
Cleaned up |
|
Any chance something similar is going on with #2588? |
|
Possibly? Maybe bring |
|
Hmmm, looks like it's already back online. |
|
probably related to an |
|
@richardlau is the cleanup that originated this issues something that we might enable |
Yes, it would be a good candidate. |
|
We should add it to a list somewhere, @AshCripps do you have anything like that created ? |
|
FWIW I've kept this issue open as the underlying issue is that we run multiple containers (5 at the current time) on each docker host and typically we run into problems when two of the containers on the same host are running debug builds. I think we've only seen it happen on the softlayer host although whether that is due to how Jenkins schedules across all the containers or possibly the softlayer host has less available disk space than the two digitalocean hosts (I'll check the disk sizes tomorrow). |
|
FWIW re. available disk space: So it looks like the SoftLayer host has half the storage compared to the two Digital Ocean hosts. |
|
(Joyent hosts are expected to be offline.) i.e. four debug builds Maybe Jenkins hasn't picked up on the space freed in #2611? And for completeness |
|
Cleared the workspaces from |
|
The debug builds are so much bigger than the release builds that we might want to rethink our container strategy... perhaps we could get away with reducing the number of sharedlibs containers on each docker host from five to four and having a dedicated container for debug builds? That would prevent having multiple debug builds running at the same time on any single docker host. It would cut the number of available executors for the debug builds from fifteen down to three but we do not have the disk capacity to run five debug builds (absolute worst case scenario in the current setup) on any of our docker hosts. |
|
yeah, that's not a bad idea. We could also do post-build cleanup, I don't think we have that enabled for these builds. |
|
Post build cleanup is an option but wouldn't prevent disk space issues for multiple debug builds in progress on the same docker host at the same time (but would at least recover the space for the next builds). I'll add separating out the debug builds into its own container to my list of things to do. |
|
All the softlayer containers were automatically marked offline in Jenkins due to low disk space. FTR: Cleared I've also gone and removed the |
|
Softlayer docker host is out of space again, reported in #2664 and #2665. 33G for |
|
I've removed the |
|
|
|
There softlayer containers were offline at the beginning of this month (#2803) and that was due to the I had to wipe out the workspaces on the softlayer containers on Tuesday as we were out of space again. This didn't seem related to #2803 (i.e. the cross-compile workspaces seemed to be a reasonable size). Today the containers on test-digitalocean-ubuntu1804_docker-x64-2 are offline for space reasons: I'll investigate later this afternoon (I have a medical appointment to attend first). |
|
Current root@test-digitalocean-ubuntu1804-docker-x64-2:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 324M 2.9G 11% /run
/dev/vda1 194G 194G 0 100% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/vda15 105M 6.7M 98M 7% /boot/efi
overlay 194G 194G 0 100% /var/lib/docker/overlay2/9bd8b27d2bb7e293a55a1b91cccf15093602dc839ce49a67cb4f7ca221028b66/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/b906535907d92563295f4345c2ffffc3c762fc67848849d1e869aa2e40ed2889/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/c008e6cf0135cd79f85f14fd4aa46c0f4e1f67b4439ee007b9161c4b9f4d4265/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/9cc63648a6ba2d48ca6753210dc0959b6e45aea6277cb010251b158f61a2b584/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/5cac407aba5a15f229addd9904605df7fbad3a241144e23b57e45965cd51c390/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/cb19d48ebf158b985f06438c60e1e39a89c8c6aa51ab8ed7407173c8b9cef984/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/508bb2ca92eaa09f49f102d4215f3f37f3cbfa2d018d4fc9257d2a2e9c79088e/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/2de854f1186395900422662e192607148094b383462ba8d7b56149fe84dd3b28/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/2052de449009e2d9f9f17c7cfc8b43bfd981a2eeb956f816f09ccb859a216032/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/37e866d149ac586cbf5f57000fc8f8263833336b66f791b6a77378907aa8a1df/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/36320a9f453d1da6b0e498d13b03853e794b1e21ed39da41c2ee6054df3fabdd/merged
overlay 194G 194G 0 100% /var/lib/docker/overlay2/026ab3aa9261e923ae35edb2ae5ac315cc444da187ef24eb23c77e49cbd82224/merged
tmpfs 3.2G 0 3.2G 0% /run/user/0
root@test-digitalocean-ubuntu1804-docker-x64-2:~# du -hs /home/iojs/.ccache /home/iojs/*
39G /home/iojs/.ccache
17M /home/iojs/jenkins_diagnostics.txt
197M /home/iojs/remoting
852K /home/iojs/slave.jar
2.9G /home/iojs/test-digitalocean-alpine311_container-x64-2
2.7G /home/iojs/test-digitalocean-alpine312_container-x64-2
2.5G /home/iojs/test-digitalocean-ubi81_container-x64-2
2.8G /home/iojs/test-digitalocean-ubuntu1604_arm_cross_container-x64-2
340M /home/iojs/test-digitalocean-ubuntu1604_container-x64-2
3.1G /home/iojs/test-digitalocean-ubuntu1804_arm_cross_container-x64-2
340M /home/iojs/test-digitalocean-ubuntu1804_container-x64-2
23G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-10
23G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-2
23G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-4
23G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-6
23G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-8
11M /home/iojs/tools
4.0K /home/iojs/workspace
root@test-digitalocean-ubuntu1804-docker-x64-2:~# |
|
The obvious outlier is that it looks like all 5 sharedlibs_containers were trying to build debug builds at the same time. I think this has been exacerbated by the increase in build times (being addressed by nodejs/node#40934) which is leading to builds being queued up and keeping all of the containers busy. I've run a root@test-digitalocean-ubuntu1804-docker-x64-2:~# find /home/iojs/*/build/workspace/* -type d -prune -not -name *@tmp -exec sh -c "cd {} && git clean -fdX" \;
...
root@test-digitalocean-ubuntu1804-docker-x64-2:~# du -hs /home/iojs/.ccache /home/iojs/*
39G /home/iojs/.ccache
17M /home/iojs/jenkins_diagnostics.txt
197M /home/iojs/remoting
852K /home/iojs/slave.jar
1.8G /home/iojs/test-digitalocean-alpine311_container-x64-2
1.7G /home/iojs/test-digitalocean-alpine312_container-x64-2
1.8G /home/iojs/test-digitalocean-ubi81_container-x64-2
2.3G /home/iojs/test-digitalocean-ubuntu1604_arm_cross_container-x64-2
340M /home/iojs/test-digitalocean-ubuntu1604_container-x64-2
2.3G /home/iojs/test-digitalocean-ubuntu1804_arm_cross_container-x64-2
340M /home/iojs/test-digitalocean-ubuntu1804_container-x64-2
1.9G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-10
1.8G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-2
1.9G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-4
2.0G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-6
1.9G /home/iojs/test-digitalocean-ubuntu1804_sharedlibs_container-x64-8
11M /home/iojs/tools
4.0K /home/iojs/workspace
root@test-digitalocean-ubuntu1804-docker-x64-2:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 1.6M 3.2G 1% /run
/dev/vda1 194G 88G 106G 46% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/vda15 105M 6.7M 98M 7% /boot/efi
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/9bd8b27d2bb7e293a55a1b91cccf15093602dc839ce49a67cb4f7ca221028b66/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/b906535907d92563295f4345c2ffffc3c762fc67848849d1e869aa2e40ed2889/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/c008e6cf0135cd79f85f14fd4aa46c0f4e1f67b4439ee007b9161c4b9f4d4265/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/9cc63648a6ba2d48ca6753210dc0959b6e45aea6277cb010251b158f61a2b584/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/5cac407aba5a15f229addd9904605df7fbad3a241144e23b57e45965cd51c390/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/cb19d48ebf158b985f06438c60e1e39a89c8c6aa51ab8ed7407173c8b9cef984/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/508bb2ca92eaa09f49f102d4215f3f37f3cbfa2d018d4fc9257d2a2e9c79088e/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/2de854f1186395900422662e192607148094b383462ba8d7b56149fe84dd3b28/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/2052de449009e2d9f9f17c7cfc8b43bfd981a2eeb956f816f09ccb859a216032/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/37e866d149ac586cbf5f57000fc8f8263833336b66f791b6a77378907aa8a1df/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/36320a9f453d1da6b0e498d13b03853e794b1e21ed39da41c2ee6054df3fabdd/merged
overlay 194G 88G 106G 46% /var/lib/docker/overlay2/026ab3aa9261e923ae35edb2ae5ac315cc444da187ef24eb23c77e49cbd82224/merged
tmpfs 3.2G 0 3.2G 0% /run/user/0
root@test-digitalocean-ubuntu1804-docker-x64-2:~#I'll try and find some time to implement the separation of the debug builds (ref: libuv/libuv#3349 (comment)). |
|
@mhdawson turned off the x64 debug builds for master (Node.js 18 onwards) (#2837 (comment)) which has alleviated the disk space pressure somewhat. There remains a discrepancy between the available disk space to the SoftLayer (IBM) host vs the two Digital Ocean ones (#2494 (comment)). $ ssh test-digitalocean-ubuntu1804_docker-x64-1 df -h /home/iojs
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 194G 106G 89G 55% /
$ ssh test-digitalocean-ubuntu1804_docker-x64-2 df -h /home/iojs
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 194G 98G 97G 51% /
$ ssh test-softlayer-ubuntu1804_docker-x64-1 df -h /home/iojs
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 99G 79G 16G 84% /
$I think it makes sense to bump the storage on the SoftLayer machine to 200GB (I think @mhdawson and I may have had this conversation some time ago). I believe on IBM Cloud this is done by adding "Portable storage". We currently have (n.b. I have a vague recollection that the unattached "jenkins-release-new" is from when we had to rebuild the release CI and had issues attaching the storage and had to get IBM support involved. The release CI server is currently using the shown attached "jenkins-release" portable storage.) |
|
I have the same vague memory as you. +1 on your suggestions. |
|
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
|
Noticed we've run out of space again on the softlayer host. e.g. https://ci.nodejs.org/job/node-cross-compile/42407/nodes=cross-compiler-rhel8-armv7-gcc-8-glibc-2.28/console 21:14:03 + git gc
21:15:01 fatal: sha1 file '.git/objects/pack/tmp_idx_Dojb52' write error: No space left on device
21:15:01 fatal: failed to run repackOn the host iojs@test-softlayer-ubuntu1804-docker-x64-1:~$ du -hs /home/iojs/*
0 /home/iojs/�
du: cannot access '/home/iojs/test-softlayer-alpine311_container-x64-1/node-tmp/.tmp.2047IpbCEh/middle/leaf': Permission denied
3.4G /home/iojs/test-softlayer-alpine311_container-x64-1
3.4G /home/iojs/test-softlayer-alpine312_container-x64-1
6.1G /home/iojs/test-softlayer-rhel8_arm_cross_container-x64-1
du: cannot access '/home/iojs/test-softlayer-ubi81_container-x64-1/node-tmp/.tmp.20478LZJ1N/middle/leaf': Permission denied
3.3G /home/iojs/test-softlayer-ubi81_container-x64-1
372M /home/iojs/test-softlayer-ubuntu1604_arm_cross_container-x64-1
2.8G /home/iojs/test-softlayer-ubuntu1804_arm_cross_container-x64-1
471M /home/iojs/test-softlayer-ubuntu1804_container-x64-1
du: cannot access '/home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-1/node-tmp/.tmp.2047eB1isj/middle/leaf': Permission denied
3.0G /home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-1
3.2G /home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-2
du: cannot access '/home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-3/node-tmp/.tmp.2047YdGl5b/middle/leaf': Permission denied
2.9G /home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-3
du: cannot access '/home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-4/tmp/.tmp.2130N0UDsX/middle/leaf': Permission denied
3.5G /home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-4
du: cannot read directory '/home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-5/tmp/.tmp.2183JNkJXS/middle': Permission denied
2.9G /home/iojs/test-softlayer-ubuntu1804_sharedlibs_container-x64-5
iojs@test-softlayer-ubuntu1804-docker-x64-1:~$I've removed the 6G cross-compile workspace ( |
|
Softlayer host was out of space again today. root@test-softlayer-ubuntu1804-docker-x64-1:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16443300 0 16443300 0% /dev
tmpfs 3291328 1608 3289720 1% /run
/dev/xvda2 102821812 98460812 0 100% /
tmpfs 16456636 0 16456636 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 16456636 0 16456636 0% /sys/fs/cgroup
/dev/xvda1 245679 107857 124715 47% /boot
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/47e5cf38674966721061004a34503ea379b6aaa73d962908775e22154f9240cf/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/383b99d8ab9bb1e7039652ddb718a7d4593df7efd463885b531176abf08de51e/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/c10c26015d495c80165a1ac0dbaa70f62c0202147775e0bb6c9b1c84b41e3f68/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/2a9afb5a6cbfeff74aa5894e96e2de94c5837ca8d684592f402f7bb59e794346/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/b62ec2f63d4baaa3d9d716a2453c35166936c7c8e7e3289db8d98e95cea6de82/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/8ea5a7396d62e9e8a60e08933a35443cb0072384edc5d8994e58a56bb968e951/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/5b8cd61827b6ca9a9ba3e3d99c194347b9fb9db76327ce074d128dac024bed86/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/1154c46c536260bac80f4d674f43737e7a1cadf925c86b93840430eddaab3c9a/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/b8e764fed9ed28540f025173d864fc81aa9ba63a207f3d52e839d22d5b7ec880/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/9a132e34cf47af1b23ea2efdd725736a8c6ed0ff112b0c653cafd16fb472773a/merged
overlay 102821812 98460812 0 100% /var/lib/docker/overlay2/61dbd42d751bf2683c8d684214cf0c87e9bcfbfeab52d251952363c1d556d50d/merged
tmpfs 3291324 0 3291324 0% /run/user/0
root@test-softlayer-ubuntu1804-docker-x64-1:~#I've run root@test-softlayer-ubuntu1804-docker-x64-1:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 1.6M 3.2G 1% /run
/dev/xvda2 99G 92G 1.9G 98% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/xvda1 240M 106M 122M 47% /boot
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/47e5cf38674966721061004a34503ea379b6aaa73d962908775e22154f9240cf/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/383b99d8ab9bb1e7039652ddb718a7d4593df7efd463885b531176abf08de51e/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/c10c26015d495c80165a1ac0dbaa70f62c0202147775e0bb6c9b1c84b41e3f68/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/2a9afb5a6cbfeff74aa5894e96e2de94c5837ca8d684592f402f7bb59e794346/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/b62ec2f63d4baaa3d9d716a2453c35166936c7c8e7e3289db8d98e95cea6de82/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/8ea5a7396d62e9e8a60e08933a35443cb0072384edc5d8994e58a56bb968e951/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/5b8cd61827b6ca9a9ba3e3d99c194347b9fb9db76327ce074d128dac024bed86/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/1154c46c536260bac80f4d674f43737e7a1cadf925c86b93840430eddaab3c9a/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/b8e764fed9ed28540f025173d864fc81aa9ba63a207f3d52e839d22d5b7ec880/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/9a132e34cf47af1b23ea2efdd725736a8c6ed0ff112b0c653cafd16fb472773a/merged
overlay 99G 92G 1.9G 98% /var/lib/docker/overlay2/61dbd42d751bf2683c8d684214cf0c87e9bcfbfeab52d251952363c1d556d50d/merged
tmpfs 3.2G 0 3.2G 0% /run/user/0
root@test-softlayer-ubuntu1804-docker-x64-1:~# |
|
I've just run an additional |
I've deleted the unattached Dallas 5 portable storage and requested a new 200GB SAN for test-softlayer-ubuntu1804-docker-x64-1. |
root@test-softlayer-ubuntu1804-docker-x64-1:~# sudo fdisk /dev/xvdc
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0xf9d84c67.
Command (m for help): p
Disk /dev/xvdc: 200 GiB, 214748364800 bytes, 419430400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf9d84c67
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-419430399, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-419430399, default 419430399):
Created a new partition 1 of type 'Linux' and of size 200 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
root@test-softlayer-ubuntu1804-docker-x64-1:~# sudo fdisk /dev/xvdc
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/xvdc: 200 GiB, 214748364800 bytes, 419430400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xf9d84c67
Device Boot Start End Sectors Size Id Type
/dev/xvdc1 2048 419430399 419428352 200G 83 Linux
Command (m for help): q
root@test-softlayer-ubuntu1804-docker-x64-1:~# sudo mkfs -t ext4 /dev/xvdc1
mke2fs 1.44.1 (24-Mar-2018)
Creating filesystem with 52428544 4k blocks and 13107200 inodes
Filesystem UUID: 09f6b200-7dda-4b9e-b16a-550b14cc1fd5
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
root@test-softlayer-ubuntu1804-docker-x64-1:~# |
|
Copying |
|
|
Reported via Slack:
From @Trott :
From @danielleadams :
The text was updated successfully, but these errors were encountered: