19%
07.10.2014
.snap
s ntestvm1.img 5 8.0 GB 292 MB 2.4 GB 2014-03-01 11:42 982a3a 2 mar.snap
s ntestvm1.img 6 8.0 GB 128 MB 2.6 GB 2014-03-10 19:48 982a3b 2 mar2.snap
ntestvm1.img 0 8.0 GB
19%
25.03.2021
[1] sdc1[0]
244065408 blocks super 1.2 [2/2] [UU]
[=>...................] resync = 6.4% (15812032/244065408) finish=19.1min speed=198449K/sec
bitmap: 2/2 pages [8KB], 65536KB chunk
19%
12.05.2020
68e152db7e5bb36b1cca638",
"sha256:37b9a4b2218692d028f9f26aa9cb85bf1f56d9abe612ba31304643bdb448484f",
"sha256:b16af11cbf2977eb52ba4d6cee5b713721cc19812b8c90ea1f22e7e
19%
11.02.2016
there are normally two. The size of these two files influences the speed of write access to InnoDB. This value was far too small for many years (5MB). The new default values in MySQL 5.6 take this into account
19%
07.06.2019
_web latest c100b674c0b5 13 months ago 19MB
nginx alpine bf85f2b6bf52 13 months ago 15.5MB
With the image ID in hand, you can inspect the image manifest:
docker inspect bf85f2b6bf52
19%
07.01.2013
OS
01 name: centos
02 summary: CentOS installation with BoxGrinder
03 os:
04 name: centos
05 version: 6
06 hardware:
07 partitions:
08 "/":
09 size: 4
10 "/home":
11 size: 1
12
19%
18.02.2018
public_key = "${file("${var.ssh_pub_key}")}"
07 }
08 resource "digitalocean_droplet" "mywebapp" {
09 image = "docker-16-04"
10 name: guest
11 region = "fra1"
12 size = "512mb"
13 ssh
19%
30.01.2020
=1): err= 0: pid=1634: Mon Oct 14 22:18:59 2019
write: IOPS=118k, BW=463MiB/s (485MB/s)(10.0GiB/22123msec); 0 zone resets
[ ... ]
Run status group 0 (all jobs):
WRITE: bw=463MiB/s (485MB/s), 463Mi
18%
19.11.2019
volume "/dev/sdb" successfully created.
Then, I verify that the volumes have been appropriately labeled:
$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/nvme0n1 lvm2 --- <232.89g <232.89g
/dev/sdb lvm2 --- <6
18%
17.02.2015
5420 Octa
Quad ARM Cortex-A15 (32KB instruction/32KB data/2MB L2) @1.8GHz, Quad-core ARM Cortex-A7 (32KB/32KB/512KB) @1.3GHz
Mali T-628 MP6
3GB LPDDR3e RAM (14.9GBps memory
