|
|
| Subject: | /var/lib/docker partition reached 100% |
| Author: | [Not Specified] |
| Posted: | 2015-07-27 06:11 |
Hi,
/var/lib/docker partition reached 100% and unable to clear the partition.
/var/lib/docker/btrfs/subvolumes is having 186 directories and each occupied from 500MB and more. Can any one please help me how to fix this
/dev/sda8 49G 46G 170M 100% /var/lib/docker
zenoss5 subvolumes]# pwd
/var/lib/docker/btrfs/subvolumes
1.4G 00709efa127dc81d69bb4c3c70de8dc9a1bc644bcd4b67e369d669e9e53ec757
1.4G 01485b6df5f4b23cfc158719634734fb0e67167ae1234942a81678bb405586cc
891M 0582ed62775789f7704aa231dec93b977e752b3dd5390df90b3ddf7328519263
1.4G 095ba0627ab66220a9dd9197bb166b4028b504a6bc829c8037019738e596a9ef
2.3G 0bb9cd64318883839cde2feda9c265777d5b29b4d7531163ee80acfff052fea1
0 0bb9cd64318883839cde2feda9c265777d5b29b4d7531163ee80acfff052fea1-init
2.2G 0c4a8ea5b2ecc9c1e1fb986c1fdb3ac508cba1bb3b17f4b45380427d4d80bf39
2.1G 0c4a8ea5b2ecc9c1e1fb986c1fdb3ac508cba1bb3b17f4b45380427d4d80bf39-init
1.5G 0d66ca274becdebfdbe87452e3cee9fc66433df433647a128a50e6c5caae749b
2.2G 11106d62a272a1b9340ea56982b8cd201054e9842eeaa673dd6e5acf0918d862
2.1G 11106d62a272a1b9340ea56982b8cd201054e9842eeaa673dd6e5acf0918d862-init
669M 13160093c48155495bb840e188e3e464e05fb9c970f7a41e8c4d35c4e97cd8a8
2.2G 15968f514207d39ec1f4a1d89ca15f6ec086c33e7bd2a3514d40a9d7c6e9bf95
2.1G 15968f514207d39ec1f4a1d89ca15f6ec086c33e7bd2a3514d40a9d7c6e9bf95-init
764M 15c1ca7eb4a2b412e3dbe40c7b577232259bea8888abc121ec4235d6f7de3c3c
1.5G 169c46d04f8b17b27005fd04c440bb50bba1eaebfa21872844e25a4f6b9c7850
649M 16acca8fbd77234453e4125c0de7d912e5051c6cac54695d554a405c129510ef
2.3G 18217b6c3ffcd3dbff9e873f59bf5cc16a77995f4713fb2c599a3508e3106d1d
1.4G 1a79d37302ec22cbf34e72c64e8a0e6d8da42360a75744886bb4fe75348b5302
650M 1c1534d7b846109298518779494172eef850cf7c86fc6f3b0b92f477868f90ab
2.2G 1f0ea694d2feab876b3c88963f62252383b19afaea38c8da1130eea2976c1dc0
2.1G 1f0ea694d2feab876b3c88963f62252383b19afaea38c8da1130eea2976c1dc0-init
192M 1f818cd47a08223024b7cdb1e72e099500aa3a05fa4ee469ddf90c771e7a490f
1.4G 23adcd0d355b230a7b2e468e8ded5942ddcce75b2aa60d2caf39556590918c25
1.4G 23adcd0d355b230a7b2e468e8ded5942ddcce75b2aa60d2caf39556590918c25-init
209M 27d47432a69bca5f2700e4dff7de0388ed65f9d3fb1ec645e2bc24c223dc1cc3
1.5G 2859ff4b4070005067072207284cceed3c68e9f4739fc77f8ad323cdab9a2093
669M 2bc936091d321999bd997f40ae12de82de95c6bb4ce9a26b225eca5b6fe9964a
1.5G 2eeec3c55e6c8e8e06b88faa393f232d37d12a5b35c2a015493d1f6892b9631e
1.4G 2eeec3c55e6c8e8e06b88faa393f232d37d12a5b35c2a015493d1f6892b9631e-init
2.2G 2f35477c65b8f7213b868163e7f40cc4496cd89c6394ab99e57a8023e1bf3c39
2.1G 2f35477c65b8f7213b868163e7f40cc4496cd89c6394ab99e57a8023e1bf3c39-init
2.1G 30168dc3455b76b623bfb059456adf0f830505fbe8664a03e9d5292aa68a07d8
2.1G 30168dc3455b76b623bfb059456adf0f830505fbe8664a03e9d5292aa68a07d8-init
651M 30c1eaf02d4c5c92d7c8c40d5878ae6a48ce1136d81c6766aed659552b15215b
1.5G 3139e7762feea488723e623b594241ee49f59c1286e888b291c34e76ba604432
1.4G 31bcbbff9088219d87d81c0c6554bd4f533b260e4cc63e9dfb98d1389115d3bc
1.5G 32f3ae49aa21a0eb2dadb9cf2089cd7278265f04b24e31294b36ac7aa0ec2401
2.2G 3304656d0fd010dbfdd689fcd57bc62eb23f7de9d6093abf729a7b323643bb47
2.2G 36ad22751413a1e299cc682c52f312bf4c989ff6937777baaa6f5414a10abb01
Thanks & Regards,
sunnybmv.
| Subject: | Might be related to the logs |
| Author: | [Not Specified] |
| Posted: | 2015-07-27 07:46 |
Might be related to the logs that used to not be cleaned in that partition.
5.0.4 should have that implemented.
For manually configuring that:
Create /opt/serviced/etc/logrotate-docker.conf
Fill it with:
/var/lib/docker/containers/*/*.log {
hourly
rotate 5
size=10M
compress
delaycompress
copytruncate
}
Then execute:
/usr/sbin/logrotate /opt/serviced/etc/logrotate-docker.conf
You can create a cron.daily script for running that often.
5.0.4 has it configured by default.
| Subject: | 5.0.4 has multiple fixes for |
| Author: | Andrew Kirch |
| Posted: | 2015-07-27 08:49 |
5.0.4 has multiple fixes for logging consuming the entire disk.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| < |
Previous Monitoring non-member Servers |
Next Zenoss Core 5.x Source Code |
> |