SMS.1315 Insufficient Free Disk Space on Target Partition xxxx
Symptom
SMS.1315 is reported during the migration.
Possible Causes
The target disk may be full due to any of the following causes.
- Cause 1: If resumable data transfer is triggered for a Linux file-level migration task, the rsync component first creates a temporary file and overwrites it later. As a result, the target server may use one to two times the storage space of the source file, especially when large files are migrated.
- Cause 2: After migration, rsync handles sparse files differently, causing them to occupy more space on the target than on the source.
- Cause 3: The target server is formatted with the default inode settings, resulting in fewer inodes than the source. Once all inodes are exhausted, the target disk will not allow new files to be created.
Solution
Delete large files on the target server to ensure sufficient space for the migration. Deleted files may appear to have not been synchronized to the target server.
- Log in to the target ECS console and reset the ECS password.
- Mount the disk based on the error message reported by the target ECS. For example:
- If the error message "Insufficient disk space in the /mnt/mapper/rhel-root partition on the target server" is displayed, mount /dev/mapper/rhel-root to /mnt/mapper/rhel-root.
mount /dev/mapper/rhel-root /mnt/mapper/rhel-root
- If the error message "Insufficient free disk space on target partition /mnt/vdc1" is displayed, mount /dev/vdc1 to /mnt/vdc1.
mount /dev/vdc1 /mnt/vdc1
- If the error message "Insufficient disk space in the /mnt/mapper/rhel-root partition on the target server" is displayed, mount /dev/mapper/rhel-root to /mnt/mapper/rhel-root.
- Run df -i to check whether the inodes are used up. If they are used up, release unnecessary files, for example, log files, on the target server.
- Check the large files in the partition.
For example, run the following command to check the top 10 files occupying the largest disk space in /mnt/vdc1.
cd /mnt/vdc1 find . -type f -print0 | xargs -0 du -h 2>/dev/null | sort -rh | head -10
- Delete the large files, restart the target server, and restart the migration task.
- Check whether the deleted files are synchronized after the migration. If not, manually synchronize them or click Synchronize again.
If the fault persists, provide logs to the technical support personnel for further analysis and troubleshooting.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot