General :: No Space Left On Device Error With Plenty Of Free INodes After Cross Compiler Setup
Jan 15, 2011
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'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.
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)
I have 160gb laptop. i installed vista in c primary partition which is 25gb and installed ubuntu in d primary partition which is 20gb. A remainig for my data. Now i tried to install CENT OS by formatting ubuntu. I inserted CENT OS DVD and restarted and i selected to delete my /dev/sda2 which is showing 20480mb and it shown me free space. but i tried to add partion /boot of 100mb it got added. but, when i am trying to add / of 3000mb in the remaining 20380mb free space it showing an error message that no free space is available.
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 am reasonable linux skilled. I am running a VPS account with Debian Linux Lenny, Virtualmin/Webmin. This has only recently started but I don't know at what point, as haven't done much on it recently but applied some updates. There's always at least 50% free ram when it happens (of 512mb) and basically no CPU activity. I've even tried killing off all process's apart from what I believed to be needed to test, (init, sshd, loggers). I can find mention of the action anywhere in any logs, even though I have klogd and syslog running. It seems to happen at varying intervals fairly regularly with certain processes. I've had it happen with a big 'rm -r' but more regularly with make's , make install's, apt-get (while its awaiting your reply to proceed), and rtorrent.
All I get is "Killed" and back to prompt, If I type "echo $?" I get '137'
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?
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 using a arm compiler to build my program but getting following compiler error at the end - init.c.text+0x2c): undefined reference to '__libc_csu_fini' init.c.text+0x34): undefined reference to '__libc_csu_init'
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
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'm creating a bash script to check how much free space is left in /var directory then, if it hits a certain threshold, delete certain files with numbers for extensions (e.g. fileA.1, fileA.2 fileA.3, and fileA.4, fileB.1, fileB.2 fileB.3, and fileB.4 ). Here's a snippet from my script:
[Code]...
If I use a * as a wildcard for the number extension, the script fails. Maybe regex would work here, but I'm not particularly accomplished at it. Or some other construct.
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?
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
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.
When I use top to see memory usage, I have 65gb ram but only 1.3gb of it free and remaining is shown as used. When I ran my program It gives memory insufficiency error. Although no other program is using the remaining 63.7gb ram it is hold. How can I get free the unused ram?
first of all, i will be glad if i can get prebuild toolchain for target=arm1176jzf-s on host= sparc-sun-solaris2.10. ( i hav browsed but can't find prebuild one) so, i tried to establish by myself i hav established binutils first, but while trying to configure& build gcc(gcc4.4.0) , i was interrupted with following error.. error message: this error has come while building boot strap gcc for cross complier tools chain
checking build system type... sparc-sun-solaris2.10 checking host system type... arm-unknown-linux-gnu checking target system
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 am trying to install Oracle ebs and it falls over with this message:-
Code:
File Space Check :
-- database node space checks --
RW-20013: Error: - Not enough free disk space on system: Database ORACLE_HOME = /d01/oracle/VIS/db/tech_st/11.1.0 required = 9967.0 actual = 9898.0390625
I need to generate 64-bit executable(utility) using PowerPC-linux cross compiler? i.e. Any options need to pass ppc-gcc other then "-m64". I have written a small test program on 64-bit server and generated 64-bit executable using gcc alone.
Ex: # file a.out a.out: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped #
Actually I want to generate a executable(using PowerPC-linux cross compiler),which will run on 64-bit machines. In my Makefile I am trying to use CC = XXXXX/powerpc-linux/bin/powerpc-linux-gcc -m64 to ppc-linux-gcc,but giving error. error: -m64 not supported in this configuration If I remove -m64 its generating 32-bit executable.
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.
