I was getting No space left on device, so I removed some of the files. But again when I try to update my folder with svn update I am getting the same error. Is this the problem with space left?  When I run df -k I get     and when I run df -i , I get     It seems like the system has ran out of inode space as you suggested even though I have the space left in my disk. How do I fix this?
121574
Still a greenee at Linux as there are so many different approaches/ways to do the same thing.  When I attempt to update to Ubuntu 17 I receive:  "The upgrade has aborted. The upgrade needs a total of 317 M free space on disk '/var'. Please free at least an additional 55.4 M of disk space on '/var'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'."  How can I safely reduce the size of this directory?  Filesystem             Size  Used Avail Use% Mounted on udev                   2.0G     0  2.0G   0% /dev tmpfs                  396M  6.0M  390M   2% /run /dev/sda1              9.1G  2.8G  5.9G  32% / tmpfs                  2.0G     0  2.0G   0% /dev/shm tmpfs                  5.0M     0  5.0M   0% /run/lock tmpfs                  2.0G     0  2.0G   0% /sys/fs/cgroup /dev/sda5              9.1G  824M  7.8G  10% /home /dev/sda7              922M  612M  248M  72% /var /dev/sda11             922M  1.2M  858M   1% /run/shm /dev/sda8              922M   21M  839M   3% /var/log /dev/sda10             226M  2.1M  208M   1% /var/tmp /dev/sda6              923M  8.5M  851M   1% /tmp /dev/sda9              922M  8.7M  850M   2% /var/log/audit //10.2.222.31/DOCMgmt  500G  216G  285G  44% /mnt/win1/DocMgmt //10.2.222.31/LOGS     250G   89G  162G  36% /media/logs tmpfs                  396M     0  396M   0% /run/user/1000
38624
I had resized my root partition from 30gb to 70gb using gparted. But Ubuntu still shows that I have the same old disk size while gparted shows that I acually have 70gb and that the other 40gb is somehow used. How can I fix this?  Output of 'df -h':  Filesystem      Size  Used Avail Use% Mounted on /dev/sda5        30G   16G   13G  55% / none            4.0K     0  4.0K   0% /sys/fs/cgroup udev            1.9G  8.0K  1.9G   1% /dev tmpfs           391M  884K  390M   1% /run none            5.0M     0  5.0M   0% /run/lock none            2.0G  284K  2.0G   1% /run/shm none            100M   48K  100M   1% /run/user /dev/sda6       341G  115G  227G  34% /media/Data /dev/sdb1       932G  459G  474G  50% /media/sidharth/passport   Output of mount:  /dev/sda5 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) /dev/sda6 on /media/Data type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfsd-fuse on /run/user/sidharth/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=sidharth) /dev/sdb1 on /media/sidharth/passport type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
73177
I need a way to determine the space remaining on a disk volume using python on linux, Windows and OS X. I'm currently parsing the output of the various system calls (df, dir) to accomplish this - is there a better way?
90163
Here's my problem: over the past couple days I did a really good clean out of my computer and managed to free up several gigabytes of data and was hovering around 233+ gb of free space.   Then in the last couple of days I noticed my trash file was taking a really long time to empty (I don't know if this is part of the problem but wanted to mention it just in case).  Last night I noticed I was missing quite a lot of space on my drive, it was around 205 gigs now. I discovered I had accidentally set some large torrent files to be on my main drive instead of an external. No matter, I figured! I would just delete them and start them over on the external. But my disk space didn't seem to change. So I rebooted - after all I had recently used Photoshop and that tends to hog a bunch of space and I don't get it back until I reboot.  I rebooted and there was still the same ~205 gb of free space. I was very confused. I was even more confused when I checked "About My Mac" and saw that it was telling me that in actual fact I only had around 90gbs of free space. THE HECK!?  I did notice that my "backups" were surprisingly high - 119gb in fact. This was especially curious since I have a time machine drive (time capsule) thats supposed to be backing up hourly. I did get a message this morning telling me it was full, but isn't it supposed to clear itself out?  Running WhatSize (it's still running by the way) I see that my .MobileBackups folder is a gargantuan 134gb! I thought these were temporary! For when I'm not connected to Time Machine (WHICH I AM!)  What in the hell is going on? How did I magically lose close to 25 gigs? And how the hell do I get it back?
7805
I am trying to update Xcode to 8.0. My OS is 10.11.6 El Capitan. However I am getting:     We could not complete your update   There is not enough disk space available to install the product.   I have got 14.22 GB free space. How much do I need?  UPDATE: I do not know the exact figure, though I did manage to update with 17.21 GB free space later on.
22941
I try to do do-release-upgrade but then I get:       Not enough free disk space      The upgrade has aborted. The upgrade needs a total of 25.7 M free   space on disk '/boot'. Please free at least an additional 25.7 M of   disk space on '/boot'. Empty your trash and remove temporary packages   of former installations using 'sudo apt-get clean'.   Output of df:                      237251272 214797108  10402504  96% / udev                    488120         4    488116   1% /dev tmpfs                   198676       668    198008   1% /run none                      5120         0      5120   0% /run/lock none                    496684         0    496684   0% /run/shm /dev/sda1               233191    225867         0 100% /boot   How come there is no space left on boot? Here's the output of ls -as /boot:  total 221839     4 .     4 ..   645 abi-2.6.32-34-generic-pae   698 abi-2.6.35-30-generic-pae   727 abi-2.6.38-12-generic-pae   727 abi-3.0.0-12-generic-pae   727 abi-3.0.0-13-generic-pae   727 abi-3.0.0-14-generic-pae   727 abi-3.0.0-15-generic-pae   727 abi-3.0.0-16-generic-pae   727 abi-3.0.0-17-generic-pae   727 abi-3.0.0-19-generic-pae   761 abi-3.0.0-20-generic-pae   115 config-2.6.32-34-generic-pae   128 config-2.6.35-30-generic-pae   136 config-2.6.38-12-generic-pae   140 config-3.0.0-12-generic-pae   140 config-3.0.0-13-generic-pae   140 config-3.0.0-14-generic-pae   140 config-3.0.0-15-generic-pae   140 config-3.0.0-16-generic-pae   140 config-3.0.0-17-generic-pae   140 config-3.0.0-19-generic-pae   140 config-3.0.0-20-generic-pae     5 grub 10773 initrd.img-2.6.32-34-generic-pae 13619 initrd.img-2.6.35-30-generic-pae 15365 initrd.img-2.6.38-12-generic-pae 16481 initrd.img-3.0.0-12-generic-pae 16487 initrd.img-3.0.0-13-generic-pae 16501 initrd.img-3.0.0-14-generic-pae 16476 initrd.img-3.0.0-15-generic-pae 16481 initrd.img-3.0.0-16-generic-pae 16478 initrd.img-3.0.0-17-generic-pae    12 lost+found   174 memtest86+.bin   176 memtest86+_multiboot.bin  1700 System.map-2.6.32-34-generic-pae  1841 System.map-2.6.35-30-generic-pae  2115 System.map-2.6.38-12-generic-pae  2141 System.map-3.0.0-12-generic-pae  2141 System.map-3.0.0-13-generic-pae  2143 System.map-3.0.0-14-generic-pae  2146 System.map-3.0.0-15-generic-pae  2147 System.map-3.0.0-16-generic-pae  2147 System.map-3.0.0-17-generic-pae  2148 System.map-3.0.0-19-generic-pae  2149 System.map-3.0.0-20-generic-pae     2 vmcoreinfo-2.6.32-34-generic-pae     2 vmcoreinfo-2.6.35-30-generic-pae     2 vmcoreinfo-2.6.38-12-generic-pae     2 vmcoreinfo-3.0.0-12-generic-pae     2 vmcoreinfo-3.0.0-13-generic-pae     2 vmcoreinfo-3.0.0-14-generic-pae     2 vmcoreinfo-3.0.0-15-generic-pae     2 vmcoreinfo-3.0.0-16-generic-pae     2 vmcoreinfo-3.0.0-17-generic-pae     2 vmcoreinfo-3.0.0-19-generic-pae     2 vmcoreinfo-3.0.0-20-generic-pae  4092 vmlinuz-2.6.32-34-generic-pae  4347 vmlinuz-2.6.35-30-generic-pae  4567 vmlinuz-2.6.38-12-generic-pae  4675 vmlinuz-3.0.0-12-generic-pae  4676 vmlinuz-3.0.0-13-generic-pae  4681 vmlinuz-3.0.0-14-generic-pae  4698 vmlinuz-3.0.0-15-generic-pae  4700 vmlinuz-3.0.0-16-generic-pae  4700 vmlinuz-3.0.0-17-generic-pae  4703 vmlinuz-3.0.0-19-generic-pae  4705 vmlinuz-3.0.0-20-generic-pae   Output of uname -a:   Linux kitsch 3.0.0-17-generic-pae #30-Ubuntu SMP Thu Mar 8 17:53:35 UTC 2012 i686 i686 i386 GNU/Linux
83173
I'm trying to identify why, suddenly, 100% of our disk space is in use. I have already rebooted but the issue persists.  Here are the outputs of some commands that are showing some strange (for me) results:  danny@hydrogen:~$ df -h  Filesystem            Size  Used Avail Use% Mounted on /dev/cciss/c0d0p1     130G  122G  949M 100% / none                  1.9G  196K  1.9G   1% /dev none                  2.0G     0  2.0G   0% /dev/shm none                  2.0G   40K  2.0G   1% /var/run none                  2.0G     0  2.0G   0% /var/lock none                  2.0G     0  2.0G   0% /lib/init/rw   danny@hydrogen:/$ sudo du -chs /  du: cannot access `/proc/1662/task/1662/fd/4': No such file or directory du: cannot access `/proc/1662/task/1662/fdinfo/4': No such file or directory du: cannot access `/proc/1662/fd/4': No such file or directory du: cannot access `/proc/1662/fdinfo/4': No such file or directory   danny@hydrogen:/$ df  Filesystem           1K-blocks      Used Available Use% Mounted on /dev/cciss/c0d0p1    135342296 128144108    323104 100% / none                   1991336       196   1991140   1% /dev none                   1995788         0   1995788   0% /dev/shm none                   1995788        40   1995748   1% /var/run none                   1995788         0   1995788   0% /var/lock none                   1995788         0   1995788   0% /lib/init/rw   danny@hydrogen:/$ mount  /dev/cciss/c0d0p1 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) none on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) none on /dev type devtmpfs (rw,mode=0755) none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) none on /dev/shm type tmpfs (rw,nosuid,nodev) none on /var/run type tmpfs (rw,nosuid,mode=0755) none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)   danny@hydrogen:/$ sudo du -h --max-depth=1  634M    ./premvet_sync 5.6M    ./etc 4.0K    ./opt 16K ./lost+found 7.4M    ./bin 623M    ./lib 196K    ./dev 0   ./sys 4.0K    ./srv 4.0K    ./cdrom 8.0K    ./media 52K ./tmp ... it hangs for ages here.....   The server is running Ubuntu 10.04.4 LTS.  System load:  2.85                Temperature:         8 C Usage of /:   94.7% of 129.07GB   Processes:           132 Memory usage: 39%                 Users logged in:     0 Swap usage:   0%                  IP address for eth0: 192.168.1.124  =&gt; / is using 94.7% of 129.07GB   I'm struggling to comprehend why this is happening! Any pointers would be appreciated.
12673
I've run into a problem on one of my servers running 16.04: there is no disk space left.  I have no idea what is taking up the space. Is there a command to list the current directory sizes, so I can traverse and end up in the directory taking up all the space?
57656
I have a strange discrepancy in the amount of free disk space that's being reported. The finder says:  My iStat Menus says:  Which is the same as df -h reports: remco@Prosperpine ~  $ df -h Filesystem                          Size   Used  Avail Capacity  iused   ifree %iused  Mounted on /dev/disk0s2                       148Gi  127Gi   21Gi    87% 33479179 5383643   86%   / devfs                              187Ki  187Ki    0Bi   100%      646       0  100%   /dev map -hosts                           0Bi    0Bi    0Bi   100%        0       0  100%   /net map auto_home                        0Bi    0Bi    0Bi   100%        0       0  100%   /home  Why would such a large difference occur? I've checked the disk using the disk utility and it does not report having any issues. Specs: Late 2011 MacBook Pro 17&quot;, non-Apple Intel 160GB SSD, OSX Mountain Lion 10.8.2
85413
Possible Duplicates:             df -h says that I have 494G used on /var:  Filesystem            Size  Used Avail Use% Mounted on /dev/sda3             564G  494G   41G  93% /var   But du -sh /var says it's 350G  What makes them different?
34502
I have backups up everything, but I'm still uneasy about the process and would like confirmation. I'd rather do this one time correctly. I want to shrink /dev/sda6/ by 200GB and reallocate it to /dev/sda2. I boot a LiveCD and turn off LinuxSwap (locked otherwise). I've been reading that it is very hard to move &quot;left&quot; when partitioning and other AskUbuntu threads are confusing me. Do I need to resize /dev/sda6 by 200GB &quot;preceding&quot; (rather than &quot;following&quot;), and then resize /dev/sda4 by 200GB? A little guidance would ease my nerves of messing everything up. Thank you ahead of time.
103766
So, I have a friend who has a flash drive that was playing music on a dvd player. Everything was great then all of a sudden it just stopped. First, I tried to do some data recovery on it but the software i use couldn't find the USB. The usb was sending us the usual error not formatted messages.  I then did a quick format of it and now it only shows 4 megabytes of space. I tried using Disk manager, then DISKPART, but nothing i have tried works.  Disk Managment looks like this:    As you can see it doesn't even show the unallocated space. It doesn't look like it is anything but a 4 mega byte flash drive.  Is it still possible to, at the very least, resurrect the USB?
49522
I started getting warnings about running out of space on my E: drive.  I've read many articles, threads and posts online about how to clean the drive but none of them resolved my issue.  My machine specs:  OS: Win 10 Pro  Version: 1803  OS build: 17134.1  I disabled hiding of protected/system files to see what's on the E: drive but I don't see any clutter. I ran the disk clean up several time as an admin to no avail. Any tips and suggestions how to clean up the E: drive would be much appreciated! Thanks.
30739
I have file servers which are used to store files. Files might reside there for a week, or for a year. Unfortunately, when I remove files from the server, df command doesn't reflect the freed up space. So eventually, the server gets filled up (df shows 99%), and my script doesn't send any more files there, except there might be a few dozen GB of free space on there.   I got noatime flag on the mounted partitions if that makes any difference.
35383
I had a problem (new to me) last week. I have a ext4 (Fedora 15) filesystem. The application that runs on the server suddenly stopped. I couldn't find the problem at first look.   df showed 50% available space. After searching for about an hour I saw a forum post where the guy used df -i. The option looks for inodes usage. The system was out of inodes, a simple problem that I didn't realize. The partition had only 3.2M inodes.  Now, my questions are: Can I make the system have more inodes? Should/can it be set when formatting the disk? With the 3.2M inodes, how many files could I have?
80593
My root filesystem is running out of inodes.  If this were an issue of disk space, I'd use du -s to get a top-level overview of where the space is going, then head down the directory tree to find particular offenders.  Is there an equivalent option for inodes?   will point out individual directories with high usage, but in my case, that's no good: the Linux source directory, for example, gets scattered across 3000+ directories with low inode counts, rather than showing up as /usr/src/linux-4.0.5 52183.
30197
I'm trying to extend  the D: partition using unallocated 30.91 GB space at its left side.   states it can't be done using Disk Management's UI and it suggests using 3rd-party tools.  However, how can we do this natively (e.g. diskpart) without installing/downloading additional software?