Debian 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...
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
Command "sudo aptitude install oxygen-icon-theme" return following error:
dpkg: error processing /var/cache/apt/archives/oxygen-icon-theme_4%3a4.6.2-2_all.deb (--unpack): unable to install new version of `/usr/share/icons/oxygen/22x22/apps/preferences-desktop-default-applications.png': No space left on device
[Code]....
As far as I can see oxygen-icon-theme unpacks only in /usr/share, beyond it I can think of only /tmp, /var or /var/tmp that it may use, all of which have plenty more than those ~40 MiB that it supposed to occupy unpacked. All btrfs filesystems were formatted with "-d single -m single". System is Debian Sid 64-bit with linux-image-3.0.0-rc5-amd64.
I 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?
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.
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)
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?
I'm running CentOS 5.2,on a 64-bit x86_64 Linux machine with kernel version 2.6.18-128.el5 smp. I appear to have version 2.9.4 of xfsprogs. I have a 22TB xfs filesystem ,Yesterday, the hard disk is full, today released a 7.7T disk space.But still can not write to new file. software ambience:
[root@Production data5]# uname -a Linux Production 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
I'm using a large xfs partition on a large raid volume using 7 1TB drives. I am currently getting a "no space left on device" error message when creating files or directories. However I see the following output when checking space limitations.
I'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.
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.
I am currently running slackware 12.2 on a 25 GB partition. I like to use slackbuilds, but when I try to compile larger tarballs (like abiword, or a patched version of Ghostscript as I did today) I receive an error-message: 'Not enough space left on device'. I think the size of the partition must be big enough (I never got this message when compiling with Linux From Scratch). I think it has something to do with the size of my /tmp directory, but I don't know how to fix this. Is there a way to solve the problem, so that I could be able to use slackbuild-scripts?
I have searched google for a couple of days, and I keep hearing about an INode limit on filesystems, but that doesn't seem to be the case.
Now whenever I try to download something, watch a ..... video, or listen to Pandora radio, it just stops playing after 2 seconds. Downloading says "No space left on device".I also get the error as root.I do have 5% and more free of HDD space. After reading the similar posts I checked all of this, so if I am overlooking something on the forum, I apologize for an extra post about.
I have been using Natty (11.04) for a while with a 3disk RAID5 via MDADM and all have been ok.I have just stuck in another disk using: mdadm /dev/md0 --add /dev/sdb, then mdadm --grow /dev/md --raid-devices=4I then resize2fs /dev/md0all seemed ok until i tried "tail -f /var/log/syslog" and was given:tail: cannot watch `/var/log/syslog': No space left on devicedf -h gives me loads of space freedf -i no problemsany i have an expensive lump parts just sitting here doing nothing.
I was running a python script tool and got this error. Exception: Command cp -Rfp /home/anil/mydroid/myfs/* /tmp/tmpX2KZDc failed (I am on dual boot ubuntu 10.10 with Win XP.) Here is a partial output from the console. Note the "No space left on device" error, when writing to /tmp.
Quote:
mke2fs 1.41.12 (17-May-2010) Filesystem label=android_fs OS type: Linux
I have had a software raid running on OpenSuse / SUSE 10 & 11 for some time and I have about 8TB on it. I always run close to 100% and once in a while get there but always manage to delete a bunch and clear out about 30-100GB.
Running CentOS 5 x64 And today my httpd is running very slow and I can't find a fix. Looked all over different forums
When starting httpd I get the message: /var/lock/subsys/httpd': No space left on device I checked that directory above and there is no file called httpd tried rebooting server
Can't do updates too: [root@u15438957 ~]# yum update Loaded plugins: fastestmirror, priorities rpmdb: unable to join the environment
Today 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 ... :'-(
just installed debian squeeze KDE after years of ubuntu and suse.. For some reason, after I finally got both scrolling and tapping to work, I have a weird weird touchpad through my xorg.conf: - tapping on a tab in chrome closes the tab.
- tapping in a text field pastes txt that is in the clipboard, each successive click keeps pasting the same thing
- the left side of the touchpad is not enabled for vertical scrolling (?), and for some reason the directions are inverted (move finger up to scroll webpage down)
- when having multiple windows open, tapping that window will highlight it, but the previously selected window stays overtop of the now selected windows. Using the actual left click button the windows change normally.
My laptop has /dev/sda5 mounted on /. It has 10GiB and almost full. I formated Windows XP partition and it is now /dev/sda1 ext4 45GiB free space.When I mounted /dev/sda1 to root (/) directory, df commands showed still the original partition size. (81% used).
I seem to have a major discrepancy between what df reports and what du reports. df tells me that I am using 20G, but I am only able to find 9.5G using du. What follows are the ls -l of root, a df of my system, and the du for every directory in root that is not a symbolic link, mnt, or proc. I would appreciate any suggestions on where to look for the remaining 10.5G that seems to have disappeared. I am running under VM Player code...
i have successfully set up squid3 with squeeze using guide on this forum viewtopic.php?f=16&t=59301 . The only problem that i have is the size of /var/log/access.log is too big and keep increasing so i run out of free space. The size of it always the same size as my free space hard disk (so it make me run out of free space in just one day, it can have size to 30 Gb ) right now , the only workaround i make is using crontab to rm access.log every hour . I'm sure this is not the right solution . Does anybody know the correct workaround about this ? I have searching in google but seems havent yet have luck with this .
so I just installed Squeeze Alpha1 amd64, dual boot with MS Vista using Grub. Everything seemed fine, but I'm apparently missing about 40GB of space. It should be set up as so:
101GB NTFS /dev/sda1 - Vista 12GB NTFS /dev/sda2 - HP Recovery 45GB ext3 /dev/sda3 - / Debian squeeze
