This Article explains the reason behind the /.mount: write failed, filesystem is full error, while copying file between Routing-engine.
Device> file copy re0:/var/tmp/junos-install-mx-x86-64-19.4R3-S10.3.tgz re1:/var/tmp/
/.mount: write failed, filesystem is full
cp: /var/home/JUNOS-RW/...transferring.file.........LHg0uf/junos-install-mx-x86-64-19.4R3-S10.3.tgz: No space left on device
error: file-fetch failed
error: could not fetch local copy of file
Following log/error will be observed while copying the file :
While copying the file between the Routing-engine, sometime we could see below error :
This error is due to less storage space on the RE's. In order to solve this, we need to clear some space in both the RE's:
1.Check available storage in both the RE's:
{master}
device> show system storage invoke-on all-routing-engines
re0:
--------------------------------------------------------------------------
Filesystem Size Used Avail Capacity Mounted on
/dev/gpt/junos 20G 16G 2.1G 88% /.mount
tmpfs 10G 228K 10G 0% /.mount/tmp
tmpfs 2.7G 1.6M 2.7G 0% /.mount/mfs
re1:
/dev/gpt/junos 19G 11G 6.2G 65% /.mount
tmpfs 633M 48K 633M 0% /.mount/tmp
tmpfs 2.7G 1.2M 2.7G 0% /.mount/mfs
In this case, we could see that RE 1 has enough space , however we still see the file not getting copied and observe same error.
The reason file-copy is failing when initiated at the source is that the file is locally copied to the same RE and then to the other RE. This means that we would need 2x the size of the package free space on the source RE for this to succeed.
2.Run below command to get the files that could be deleted :
>request system storage cleanup dry-run
3.Delete any unwanted file, which is occupying space. Once done, no more errors will be seen - file copy will be successful.
device> file list /var/tmp/ detail | match junos-install-mx-x86-64-19.4R3.11.tgz
-rwxr-xr-x 1 JUNOS-RW wheel 3401881401 Jan 16 16:10 junos-install-mx-x86-64-19.4R3.11.tgz*
{backup}
-rwxr-xr-x 1 JUNOS-RW wheel 3401881401 Jan 19 01:00 junos-install-mx-x86-64-19.4R3.11.tgz*
Incase the issue is still seen, please engage JTAC to investigate the issue.