I am about to embark on the image upgrade of more than 200 EX2300s. Since I have been doing this before, I know I will face disk space issues on any number of switches.
. Does anybody have any contraindication to cleaning the /packages/db directory of files belonging to a previous image ????I found that I can get an impressive amount of space this way.
here is an exemple of removing remnants of the 15.1X53 image on a switch running on 18.2R3.
I was able to save 208 easily.
Good idea ? bad idea ?? what do you think ?????
Last login: Tue Aug 18 11:22:26 2020 from 192.168.169.156--- JUNOS 18.2R3-S2.9 Kernel 32-bit JNPR-11.0-20191022.14c2ad5_buil
root@SWA-UQAT-ROU02:RE:0% ls /packages/db/fips-mode-arm-32-20181114.201826_builder_junos_151_x53_d590fips-mode-arm-32-20191115.190104_builder_junos_182_r3_s2jail-runtime-arm-32-20180119.e26d166_builder_masterjail-runtime-arm-32-20191022.14c2ad5_builder_stable_11jdocs-ex-arm-32-20181114.201826_builder_junos_151_x53_d590jdocs-ex-arm-32-20191115.190104_builder_junos_182_r3_s2jpfe-EX34XX-arm-32-20181114.201826_builder_junos_151_x53_d590jpfe-EX34XX-arm-32-20191115.190104_builder_junos_182_r3_s2jphone-home-arm-32-20191115.190104_builder_junos_182_r3_s2jsd-arm-32-18.2R3-S2.9-jet-1jsdn-arm-32-18.2R3-S2.9junos-arm-32-15.1X53-D590.1junos-arm-32-18.2R3-S2.9junos-daemons-arm-32-20181114.201826_builder_junos_151_x53_d590junos-daemons-arm-32-20191115.190104_builder_junos_182_r3_s2junos-dp-crypto-support-arm-32-20181114.201826_builder_junos_151_x53_d590
root@SWA-UQAT-ROU02:RE:0% du -hs /packages/db/708M /packages/db/root@SWA-UQAT-ROU02:RE:0% rm -R /packages/db/*151_x53*root@SWA-UQAT-ROU02:RE:0% du -hs /packages/db/500M /packages/db/
root@SWA-UQAT-ROU02> show system storage
Filesystem Size Used Avail Capacity Mounted on
/dev/gpt/junos 1.3G 810M 447M 64% /.mount
root@SWA-UQAT-ROU02> show system storageFilesystem Size Used Avail Capacity Mounted on/dev/gpt/junos 1.3G 602M 655M 48% /.mount
follow up question ...
is there any use of keeping more than 100M of files from 15.1X53 on a 2300 switch running 18.2R3-S2 ???
root@csob-valdor-02-BYPASS:RE:0% du -h /packages/db39M /packages/db/junos-arm-32-15.1X53-D590.1/upgrade12K /packages/db/junos-arm-32-15.1X53-D590.1/scripts20M /packages/db/junos-arm-32-15.1X53-D590.1/contents59M /packages/db/junos-arm-32-15.1X53-D590.116M /packages/db/junos-arm-32-18.2R3-S2.9/contents12K /packages/db/junos-arm-32-18.2R3-S2.9/scripts16M /packages/db/junos-arm-32-18.2R3-S2.93.5M /packages/db/jsdn-arm-32-18.2R3-S2.9/contents8.0K /packages/db/jsdn-arm-32-18.2R3-S2.9/scripts3.5M /packages/db/jsdn-arm-32-18.2R3-S2.9
Follow up answer, pas du tout, as mentioned these are just taking space.
If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/
Lil DexxJNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB
Merci beaucoup pour la réponse.
can you suggest any other place where old useless stuff is lying around that I can clean ?
Avec plaisir 🙂 you can also try this :
root@LapointeMichel:RE:0% ls /packages/sets/
active previousroot@LapointeMichel:RE:0% rm -ft /packages/sets/previous/
those images need all the space they can get
It is a good idea and you should not see any counterindications, these files are just cluttering the file system. If for some reasons you still have some issues with space after deleting those old codes please use this KB31198