MOTOSHARE 🚗🏍️
Turning Idle Vehicles into Shared Rides & Earnings

From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.

With Motoshare, every parked vehicle finds a purpose. Owners earn. Renters ride.
🚀 Everyone wins.

Start Your Journey with Motoshare

write of 2225 bytes failed with errno=28 no space left on device

The error message you’re seeing, “write of 2225 bytes failed with errno=28 no space left on device,” indicates that there is no available space on the device where you are trying to write data. The error code “28” corresponds to the “ENOSPC” error in Unix-like operating systems.

Check Disk Space: Ensure that you have enough free space on the device where you are trying to write data. You can check the available disk space using the df command.

df -h

This will show you the disk space usage on different mounted file systems.

Free Up Space: If the disk space is low, you need to free up some space. You can remove unnecessary files, especially large ones, to make more space available. Use the du and rm commands to identify and delete unnecessary files.

du -h --max-depth=1 /path/to/directory
rm /path/to/unneeded/file

Check Inodes: In addition to checking disk space, check the available inodes. Sometimes a filesystem can run out of inodes even if there is free space. You can use the df -i command to check inode usage.

df -i

Rotate or Clear Log Files: Log files can consume a significant amount of space. Check and rotate or clear unnecessary log files.

ls -lh /var/log

Temporary Files: Check for and delete temporary files that may be taking up space. The /tmp directory is a common location for temporary files.

rm -rf /tmp/*

Consider Deleting Cached Files: Some applications cache data, and these caches can consume a considerable amount of space. Clearing unnecessary caches may help.

rm -rf ~/.cache

Related Posts

Become a DevOps Engineer in Mumbai with Real Projects

Introduction: Problem, Context & Outcome Engineers across Mumbai work in fast-paced delivery environments where releases happen frequently, systems scale continuously, and downtime costs money. However, many professionals…

DevOps Expertise for CI/CD, Cloud, and Automation—Malaysia

Introduction: Problem, Context & Outcome Engineering teams across modern organizations adopt DevOps to accelerate releases and improve system reliability. However, many teams still experience deployment failures, slow…

DevOps Expertise for CI/CD, Cloud, and Automation—Kolkata

Introduction: Problem, Context & Outcome Many engineering teams invest in DevOps tools expecting faster releases and improved stability. However, deployments still fail, recovery remains slow, and coordination…

DevOps Expertise for CI/CD, Cloud, and Automation—Hyderabad.

Introduction: Problem, Context & Outcome Many engineering teams adopt DevOps tools expecting faster delivery and higher stability. However, releases still fail, recovery takes too long, and teams…

DevOps Expertise for CI/CD, Cloud, and Automation—Delhi.

Introduction: Problem, Context & Outcome Many engineering teams adopt DevOps tools expecting faster releases, yet they still face unstable deployments, frequent rollbacks, and unclear accountability. Although automation…

DevOps Expertise for CI/CD, Cloud, and Automation—Chennai

Introduction: Problem, Context & Outcome Many engineering teams adopt DevOps tools with high expectations, yet they continue to face slow releases, unstable deployments, and repeated operational issues….

0 0 votes
Article Rating
Subscribe
Notify of
guest
1 Comment
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
trackback

[…] write of 2225 bytes failed with errno=28 no space left on device […]

1
0
Would love your thoughts, please comment.x
()
x