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

DataOps Practices: A Comprehensive Guide for Modern Data Teams

Introduction: Problem, Context & Outcome Data teams often struggle with slow pipelines, inconsistent data quality, and fragile analytics workflows. Engineers manually move data across systems, analysts wait…

Datadog Observability: A Comprehensive Guide for DevOps Teams

Introduction: Problem, Context & Outcome Modern engineering teams struggle with poor system visibility across infrastructure, applications, and cloud services. Logs remain scattered, metrics lack context, and alerts…

Datadog Monitoring: A Comprehensive Guide for DevOps —Pune

Introduction: Problem, Context & Outcome Engineering teams struggle daily with limited visibility across applications, infrastructure, and cloud services. Logs remain scattered, metrics feel disconnected, and alerts often…

Chef Configuration Management: A Comprehensive Guide —Pune

Introduction: Problem, Context & Outcome Infrastructure teams often struggle with configuration drift, manual server setups, and inconsistent environments. Engineers repeatedly fix the same issues because systems behave…

Chef Configuration Management: A Comprehensive Guide —Bangalore

Introduction: Problem, Context & Outcome Infrastructure teams still struggle with configuration drift, inconsistent environments, and deployment failures. Engineers often configure systems manually, which introduces errors and delays…

Amazon AWS Experts: A Comprehensive Guide to Skills —Pune

Introduction: Problem, Context & Outcome Cloud adoption continues to accelerate, yet many engineers struggle to move from theory to real-world AWS implementation. Teams often deploy workloads on…

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