failed: No space left on device (28)
Hello,
I am getting the following the "failed: No space left on device (28)" error while copying files to the server, disc usage status is following, df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LVroot 12G 3.9G 7.1G 36% / tmpfs 1.9G 0 1.9G 0% /dev/shm /dev/sda1 194M 34M 150M 19% /boot /dev/mapper/VolGroup00-LVtmp 3.9G 72M 3.6G 2% /tmp /dev/mapper/VGdata-LVdata 24G 8.0G 15G 36% /data df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/VolGroup00-LVroot 761856 131403 630453 18% / tmpfs 490585 1 490584 1% /dev/shm /dev/sda1 51200 39 51161 1% /boot /dev/mapper/VolGroup00-LVtmp 256000 32 255968 1% /tmp /dev/mapper/VGdata-LVdata 1572864 1572864 0 100% /data I am not able to copy any fine under /data directory, but it shows 15G available, could you please suggest me how to handle this. |
Hello,
I think there may be Reserved space for root on a filesystem. Please let me know how to increase the same. |
You may have free space but you have no free inodes to allocate it.
|
The reserved space is not relevant here - you can eliminate it using tune2fs.
Your problem is you have run out inodes as you are apparently aware. If this is an ext[234] filesystem, you must reformat the filesystem (see the mke2fs "-i" option). Back the current data up, re-format with more inodes, restore, then copy in your new data. You must have a significant number of files. |
Quote:
mke2fs -I 128 /dev/mapper/VGdata-LVdata tune2fs -l /dev/mapper/VGdata-LVdata | grep Inode Inode count: 1572864 Inodes per group: 8192 Inode blocks per group: 256 Inode size: 128 |
deleted.
|
Hi,
I have recreated the LVM too, again fails. |
Fails?
Does the actual LVM creation fail? When you created the 15G partition did you create it with more inodes? |
Hello,
Thank you for all of you for helping me at right time with good tips. The following command helped me to get rid of this issue. mke2fs -i 8192 /dev/mapper/VGdata-LVdata |
All times are GMT -5. The time now is 11:32 AM. |