I was saving a few pictures, and I realized that none of them were actually being saved. I went to my home folder and I noticed that I only had 0 bytes left, then I deleted everything in my trash, got some space back, then it disappeared.
View 3 RepliesToday I was installing a lot of software since I'm just setting up my Slackware system again after a fresh install, and I realized that my root partition has very little space left.
Here is the output of df -h:
Code:
As you can see, I have a 20G (19G here for some reason) root partition, 8G /var, and 86G of /home. I thought this would be plenty since many recent recommendations for / are 10-15G. Now, though, 17G are used up for some reason! How is this possible? I thought a full slackware install only had about 4G of software! I don't have any music or movies or any crazy huge files that I know of, and those would be in my /home directory anyway. Is there any way I can see which files are taking up all this space?
If it's necessary to allocate more space to my / partition, is it still possible to boot up a GParted live Cd, shrink /home a bit, move some partitions to the right, and expand my root partition? I would REALLY prefer I don't have to reinstall since I just spent a ton of time setting up my system again, but if worst comes to worst ... :'-(
In case you're curious, here's my /etc/fstab:
Code:
df -h [URL] I did the following command to find everything is in /usr or /var, then tracked it down to /usr/lib and /usr/share as the main offenders, but out of all the directories none are more than 1mb or so.
du -sh /* | sort -gr | head -n 5
I tried to uninstall firefox, which is what got me in this mess in the first place, the log claims it will remove ~240 mb but failes on a "E: Write error - write (28 No space left on device)" [URL] If I could juggle something onto an external hard drive so I can uninstall firefox I would be out of the wood. Failing that I believe a new install is in order.
For our workgroup I set up a server which is basically 10.04.2 with kernel 2.6.32-32-server on a SSD and all the data on a RAID 5 consisting of 4 2TB hard disks, thus a maximum of 6TB space for data on the RAID. Having multiple users with different amounts of data from different scientific data source I set up an lvm on top of the RAID
--- Physical volume ---
PV Name /dev/sdb2
VG Name home-data
PV Size 5,45 TiB / not usable 3,00 MiB
[code]...
Here is the problem: The volume Genomes (or /genomes) is half full
sudo df -ah
/dev/mapper/home--data-Genomes
1,9T 850G 920G 49% /genomes
but the system states it as full whenever I try to add more data (tried cp and rsync). There is no quota set to the volume (I have quotas in place for users home folders. These are only for max amount of disk space, not max file number, and I am still able to move/add files elsewhere so there seems to be no interference).
I recently had to move to a new machine, everything went well except for one thing. I did fresh installation of LAMP server all with default configs. Every time I'm using PHP script to that invokes include, require or require_once I get the following error:
Code: Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 7680 bytes) in /var/www/index.php on line 2 index.php file: PHP Code:
<?php include "index.php";?>
icukapi.php file:
PHP Code:
<?php echo "test";?>
My memory_limit in php.ini is set to 20M. I tried to increase that however it didn't quite work. PHP seems to allocate all possible space and return that message every time i try. If somebody has an idea of how to fix it I would be more than grateful. I spend quite a long time searching for an answer however the all things i found suggested increating memory_limit which in this case doesn't work.
My system currently runs mdadm with three mirrored volumes (4 disks, two mirrored partitions on the first two (a) and (b), entire disks mirrored on the second two (c) and (d)), giving me some redundancy in case of disk failure, which it appears I now have. The root volume is mirrored on sda1 and sdb1, and this morning I noticed a mail from mdadm telling me the two RAIDs on (a) and (b) were degraded. It appears things went a step further and /dev/sda is completely gone.
mdadm has come through, though. The system is still running normally with the mirrored partitions on disk (b). What's got me concerned is that disk (a) is only about a month old and was bought brand new. I'm not at home right now to check the actual hardware, but seeing as the signs are pointing this way, do they necessarily mean the disk has failed? Is there something in the logs I could check that would tell me if, say, the PCI SATA card is playing up instead? I know hard disks fail, but I'm paranoid in case tings get worse as I'm running a reasonably important website on this machine, and just wondering if I should be considering setting up a backup server in case there's a bigger problem here. Edit: Sorry, forgot to say. I'm running Squeeze and it's fully up to date. Hardware is a 1.2GHz Celeron, 512MB RAM, Silicon Image SiI 3114 PCI SATA Controller, 2x 500GB SATA disks (a and b), 2x 1TB SATA disks (c and d).
How do you calculate the number of usable bytes on a disk partition? When I do an fdisk -l I get this:
Disk /dev/md0: 192.0 GB, 192069500928 bytes
2 heads, 4 sectors/track, 46891968 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
[code]...
Mounted second hard disk still report 0 bytes even when files are already deleted in rhel5 . I already checked the lost+found and trash . It only happen that disk space on deleted files cannot be recovered after the disk reach full capacity , but if it does not reach yet its full capacity , deleting files will recover the disk space . The format of the disk I have mounted is ext3 also have tried ntfs using fuse but the same problem , once allowed to reach 0 bytes I can no longer recover space with deleting files and had to reformat and restore the backup
View 4 Replies View RelatedI just tried to download a torrent and got an error message indicating there was no space left in the download location I'd specified.
This happened earlier when df -h showed ~900M of free space. Just now, I'm showing ~2.2G of free space. Anyone have ideas what could be causing this?
cp: writing `/tmp/tmpX2KZDc/system.image': No space left on device However, when I right-click on properties, I see it has 51 items, totalling only 130.5 KB!this is a dual boot system with Win XP and Ubuntu 10.10 (~58Gb partition)Quote:
anil@anil-HP-EliteBook-8440p:/tmp$ mount
/dev/sda5 on / type ext4 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
[code]...
root@localhost:~ $ df /dev/sdb1
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb1 1922858352 23247088 1801935664 2% /mnt/external/sdb1
[code]....
OS: RHEL AS 5 64-bit
HDD:300 GB Hardware mirror (HP blade bl460c)
While installing OS, in partition window after OS file system structure I've left 277 GB. But after installation it shows Size - 255GB and available disk space is 242 GB.
Isn't it weired? How can I use the total amount of space in Linux? I need the whole 277GB exactly. What should be my workaround?
I recently upgraded from Lucid to Maverick, which went fairly smooth. Then I upped my RAM with some new memory sticks (4Gb to 8Gb). Since about then, I'm seeing these errors in syslog:
Code:
Jun 6 22:23:52 howler console-kit-daemon[1224]: WARNING: Failed to add monitor on '/dev/tty2': No space left on device
Jun 6 22:23:59 howler console-kit-daemon[1224]: WARNING: Failed to add monitor on '/dev/pts/0': No space left on device
I also get errors when running "tail -f" as root:
Code:
tail: cannot watch `/var/log/syslog': No space left on device
I searched around and I found some other reports of the tail -f error, with the suggestion of increasing fs.inotify.max_user_watches. I set it to 16384, and that at first resolved the tail -f problem, but now I'm getting that error again even after upping max_user_watches.
I know swap is suggested to be approx. the same size as RAM, but with this upgrade RAM is now bigger than the 5.7G of swap.
i'm using Ubuntu virtual machine.latly, i've moved the VM image to other PC. something with the user privileges got wrong. i when i edit a file using nano for example from a simple user, it says: "no space left on device" but when i use
# sudo nano filename
it works.i used
#chmod 777 filename
and it still dosent work. i cant save/write to disk while i'm in the user account. but with sudo, or root account it works.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Yes I tried 'sudo dpkg --configure -a' Should I do a reinstall.
"Setting up initramfs-tools (0.92bubuntu53) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.31-17-generic
gzip: stdout: No space left on device update-initramfs: failed for /boot/initrd.img-2.6.31-17-generic dpkg: subprocess installed post-installation script returned error exit status 1"
I've just upgraded to kubuntu 9.10, and I'm getting strange errors when trying to copy files onto my MP3 player, a SANSA M250 (2GB). df claims it's at 57% capacity (and the figures make sense for that, as well as having about the quantity of music which half fills the SANSA) but when I try to copy a file - from the command line, from exaile, or with the file manager, I get a "No space left on device" error:
Code:
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 73939452 42184580 27998880 61% /
udev 512472 264 512208 1% /dev
none 512472 1752 510720 1% /dev/shm
none 512472 96 512376 1% /var/run
none 512472 0 512472 0% /var/lock
none 512472 0 512472 0% /lib/init/rw
/dev/sdc 1996000 1125056 870944 57% /media/SANSA M250
$ cp test.mp3 /media/SANSA M250/
CP: cannot create regular file `/media/SANSA M250/test.mp3': No space left on device
The MP3 being copied is 2MB in size so should fit easily.
There were no problems until upgrading, when I also moved from amarok to exaile - because amarok2 doesn't have the functionality I want from a player. But this happens even if exaile isn't running, so exaile shouldn't be the problem. How can I diagnose what's going on?
If I run low on free space, and I/system need to write something, then the files are just truncated. With no way to revert to their previous content.
First I installed the Windows on the VirtualBox, it sucked up all free space, so I couldn't even login to the system afterwards.
Then I, once again, silently ran out of free space, and my php editor broke. Later I discovered that it tried to write its config files, but failed, truncating them all. I lost a half a year of configurations, custom color scheme and custom code snippets.
Then one day the system just froze. Later I understood, there wasn't enough free space for it to run.
Today I was working on my php script, for like the second day, when, again, free space ran out, so with another file-save, I got a wonderfully impressing blank php-file. It was auto-reloaded from the external change, which was failure to write to file, obviously, so no ctrl-z worked, leaving me with two days work wasted and an urge to hit the monitor
My questions are:
1 How can this be fixed? Besides the obvious awesome fix "watch your free space, buddy".
2 Could somebody explain why these sorts of things happen, just so I know why the ultra-safe and durable 'nix operating system wants to destroy itself sometimes?
3 Anyone else encountered this issue?
So i am using xubuntu from wubi and i need more space to instal all the important security updates, How do i free up space? i think i made a mistake and did not allow it much space when i made the partition for it
View 4 Replies View RelatedThe wubi install of Ubuntu is saying it only has 125 MB left. I gave the install 10 GB to start with. I know the OS takes about 3 GB and I didn't install 7 GB worth applications. I'm thinking some how it confused itself. I've done run the Disk Analysis And it's rather confusing, but it seems to be looking at more then its alloted 10 GB.
View 6 Replies View RelatedI have an WD 1TB external hard disk. When I try to write any file to it - even a 1kb text file - I get the message "no space left on device". I cannot write to the disk at all anymore - not files, not directories.The drive is formatted as an NTFS drive. I use F13. I can read from the drive without any apparent problem. Would anyone know what's causing this problem?
View 2 Replies View RelatedI am trying to copy some files onto a flash card. The first thing that i do is mount to the flash card:
mount /dev/sdc1 /mnt
then i try and copy a file
cp dev.bin /mnt
but i get a message saying:
cp: writing `/mnt/dev.bin': No space left on device
I was able to copy some files before but i cant seem to do it anymore.
how can i delete everything thats on the flash card so that i can copy files onto it?
Some thing is using up a huge amount of my disk space about 10G and I can not determine what it is. When I look at my disk usage in system monitor it say I have used about 25G and when I scan the directory in disk usage analyzer the entire file system used is 15G.
View 1 Replies View RelatedI have noticed that the initial ordering of icons of my desktop is leaving a blank space on the top left corner. Recently I have changed my language but I am not sure when this began to happen.
View 7 Replies View RelatedMy boot partition doesn't have any space left, rendering me unable to install any updates. Most space in the boot directory (85 MB) is taken by the following files:
initrd.img-2.6.32-24-generic
initrd.img-2.6.32-26-generic
initrd.img-2.6.32-27-generic
initrd.img-2.6.32-28-generic
initrd.img-2.6.32-29-generic
initrd.img-2.6.32-30-generic
It seems to me that I�d need at most one of these. What exactly do (or did) these initial ramdisks do, and is it safe to delete them?
I have a backup drive formatted ext4 which got filled to no space left, so I deleted some files and folders to make space on it , emptied the trash, files and folders are gone , but it stll says I got no drive space left on it and cant copy a file to it because it thinks its full lol I freed up like 15gb of space on it , have rebooted several times ..
View 7 Replies View RelatedDebian Version: 8.3 (Jessie) KDE (although this is NOT a desktop issue)
Basic Hardware:
Gigabyte Motherboard GA-970A-D3P
AMD 8350 CPU (8 cores)
32 GB DDR3 RAM
120GB SSD SATA-6GB/s
750 WD Black SATA-6GB/s
I am getting "Error: No space left on device" regularly during updates or installs, but why. Here is data on the disks, filesystems, etc...
Code: Select all df -h
Filesystem   Size Used Avail Use% Mounted on
/dev/sda1Â Â Â Â 81GÂ Â 27GÂ Â 50GÂ 35% /
devtmpfs     16G   0  16G  0% /dev
tmpfs      16G  76K  16G  1% /dev/shm
tmpfs      16G  18M  16G  1% /run
[code]...
Seems very doubtful that inodes are the killer.I have googled and followed all the threads, and search these forums and found nothing that fits - every answer there was focused on avaiolable space and inodes..And to make the cheese even more binding, the issue has cropped up on another 8.3 system with far more disk space (larger hard drives) and lots more unused inodes
Code: Select alldf -h
Filesystem            Size Used Avail Use% Mounted on
/dev/dm-0Â Â Â Â Â Â Â Â Â Â Â Â Â 907GÂ 6.6GÂ 855GÂ Â 1% /
udev                10M   0  10M  0% /dev
tmpfs               995M 9.2M 986M  1% /run
tmpfs               2.5G  76K 2.5G  1% /dev/shm
tmpfs               5.0M 4.0K 5.0M  1% /run/lock
tmpfs               2.5G   0 2.5G  0% /sys/fs/cgroup
[code]...
You would think it would be easy to do this (and essential to maximizing and predicting the usage of tapes), but apparently this isn't so. The program MT(1) actually had some commands that give the block positition (if supported by the drive) from which the remaining space could be deduced (even if you couldn't predict exactly how much space the next archive would take up). However I'm using MT(1L) which no longer has such commands.
View 1 Replies View Relatedran out of space in my /home dir. Have a second hard drive to install and would like to designate it as additional space for /home. I do not want to mount it as a dir inside my home I would like it to simply work as though my /home simply has more space available to it.
View 1 Replies View RelatedI'm unable to login to my Kubuntu Lucid. The login screen takes my password, blanks, then returns me to the login screen. I'm getting some graphics errors when running from recovery mode as well as the no space left on device error when attempting to start x from the terminal. Here are some outputs: When starting from recovery mode, selecting failsafeX from the Recovery Menu:
[Code]...
I've come to the conclusion that my root partition is full, but I'm not sure how to clear space, or how much to clear once I work out how to do it. I removed a few packages with apt, but it doesn't seem to have any effect. df -h shows that root is 100% full, yet it has 3GB free. I've grown comfortable with Ubuntu in the couple years I've been using it, yet this level of problem-solving is a bit nerve-wracking to me. I've been considering reinstalling (this machine is running Lucid upgraded from Karmic and Jaunty and has a few oddities), but I hate the idea of being forced to reinstall because I can't overcome this problem. If you need any other information or outputs from terminal commands, I'm happy to provide it.
I am trying to write to a Ramdisk because I suffer from terrible IO speeds on my VPS. It uses openVZ and I run a Centos 5 distro.
So i created my ramdisk with '/bin/mount -t tmpfs -o size=1G,nr_inodes=10k,mode=0775,noatime,nodiratime tmpfs /tmp'
but whenever I try and copy files to it, it just spams me with 'no space left on device even though there is!
Here is the output of df:
/dev/simfs 157286400 6511452 150774948 5% /
none 16441412 4 16441408 1% /dev
tmpfs 5242880 1296 5241584 1% /disk/test
tmpfs 5242880 1296 5241584 1% /disk/test
[Code]....