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 RepliesI am attempting to install a small rpm that will give command line access to an integrated array controller on my system so that I can add more local disk. When attempting to apply the package I am receiving an error indicating that there is not enough space available on the filesystem. I have expanded the filesystem several times today in order to try and resolve this issue and also moved ~1.5G of files to another filesystem but I am still receiving the error.
Code:
[root@frenzy1a.mgmt.qa:~]# rpm -ivh /tmp/hpacucli-8.35-7.0.noarch.rpm
Preparing... ########################################### [100%]
installing package hpacucli-8.35-7.0.i386 needs 18MB on the /opt filesystem
[root@frenzy1a.mgmt.qa:~]#
[code]....
I have rebooted the server a couple of times and ran fsck as well.
We had a perfectly working SUSE OES netware server for some months, and wanted to create a new image backup. Using Acronis Backup and Recovery Advanced Server Software. This worked a treat on our SBS 2008 Server. We went to run it for Novell OES and a system lock up occurred and services such as Iprint then disabled. A server restart recovered the server after a few attempts. We then learnt that the server could not write files to an NTFS formatted USB drive. This was the ideal destination to test the backup. However we could not even write a simple file to the drive without an error message about permissions.
We then learnt that Linux needs a package called NTFS-3G to enable NTFS writing permissions. This did fix the writing issues. We attempted to run another back up which again failed, bringing down the server. We again attempted to reboot the server this time we fail to get to the graphical user login. At the suse Linux Enterprise boot screen we select "boot from hard disc". Which fails immediately with "GDM could not write a new authorisation entry to disk...Error no space left on drive". When the boot eventually continues, a number of things fail with the same message about "No space left on device".
The next message starts "Could not start the X server due to some internal error."
Further to the above, starting "recovery" instead, the checks of partition fail and it seems obvious that the partition definitions have become corrupted. In the expert partion manager the lines for partitions seem correct except that there are no entries for 'mount point' and 'mount by' columns. Trying to edit these lines does not appear to allow entries for mount point or mount by - they are disabled. It seems likely the server is not mounting some partitions at boot which is why the kernel thinks the server is full. Is there some simple way we can use say fdisk to repair the partition definition without loosing anything of the server OS and data ?
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 ... :'-(
In case you're curious, here's my /etc/fstab:
Code:
Wierd problem, when I map a Windows Drive to my Ubuntu HTPC Samba share, Windows reports the free space as the free space on my root partition?!!?
HTPC Ubuntu server:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 12G 6.5G 4.0G 62% /udev 1.6G 308K 1.6G 1% /dev
[code]....
So my root partition has 4gb free, and my samba share (/mnt/data) has 97gb free.
From Windows machine:
net use
Status Local Remote Network
-------------------------------------------------------------------
OK Z: \xbmcfiles MS Windows Network
[code]....
I 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]...
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 running a laptop with a windows partition and a ubuntu partition. I partitioned from windows, then setup the linux partition from the ubuntu cd and formatted it to ext4. I am running the Ubuntu 11.0.4 and Windows 7. PROBLEM: All reports indicate that the Ubuntu /home directory is eating 66 GB when there is no indication that is using even a fraction of that space. What can I do to reclaim the space?
Here is the report on the disks and usage:
Code:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x32286323
[Code]...
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 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 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?
I am attempting to get Debian Lenny 5.0.8 to run on an OpenSolaris snv_134 lx-branded zone. Debian 6.0.0 is a total flop due to the included udev requiring a kernel >= 2.6.26 and the kernel provided by the lx26 brand being only 2.6.18.So I installed Debian 5.0.8 into a VirtualBox VM, configured it, then tarred up the install with the following command as root, from /:
tar -cjf /mnt/share/debian-5.0.8.tar.bz2 --exclude dev --exclude sys --exclude mnt --exclude proc *
I then installed that archive into a solaris zone, booted it, and had to run
perl -pi -e "s,1 1,1 0," /etc/fstab
in order to fix up the fstab. Now it boots (with a handful of warnings), but the problem I'm having is that I can't run apt. I get:
E: Couldn't determine free space in /var/cache/apt/archives/ - statvfs (75 Value too large for defined data type)
A few days ago I made the mistake of upgrading to Ubuntu 10.04 LTS, and subsequently had nothing but trouble. My volume icon disappeared and for the life of me I couldn't find it or reinstall it. An eerily Windows-like chat icon has appeared next to my login name that I didn't ask for, and more importantly my handbrake program (Matroska encoder) completely stopped working.
I've learned in the past that LTS editions are not normal upgrades, and I should best avoid them. But this one appears from the Ubuntu homepage to be the standard upgrade from Karmic to Lucid. I've had to completely reinstall Karmic on my workstation just to be able to carry on as normal, but the laptop seems to be coping ok with the LTS edition. Can anybody tell me if this LTS is now the default upgrade for Lucid, or is this just a regular LTS and I should wait for my standard one to come out?
Code...
but 'top' shows 2GB of swap...
top - 18:38:42 up 4:22, 5 users, load average: 0.54, 0.61, 0.64
Tasks: 369 total, 1 running, 368 sleeping, 0 stopped, 0 zombie
Cpu(s): 7.4%us, 1.4%sy, 0.0%ni, 86.9%id, 3.4%wa, 0.0%hi, 0.9%si, 0.0%st
Mem: 33265832k total, 24859468k used, 8406364k free, 379892k buffers
Swap: 2031608k total, 0k used, 2031608k free, 2030328k cached
Why is that?
Upgraded x86 Karmic (which had OpenOffice.org 3.1) to Lucid via the Alternate CD. Why was OpenOffice.org not upgraded to 3.2?
View 2 Replies View RelatedI recently upgraded from 8.04 (Hardy) to 10.04 (Lucid). I usually leave my Linux box running as an SSH server (setting on never sleep) while traveling so I can access files, and so on, but since upgrading, I am no longer able to connect via SSH, and upon my return the fan suggests the computer is still running (not sleeping), but the screen is dark and keyboard/mouse cues will not "wake it up".
View 4 Replies View RelatedI have linux and windowsxp on one machine. I have only 3gigs free on the windowxp machine and 20gigs free on the linux machine. I want to transfer space from the linux box to the windows machine.Is this possible and what steps would I need to follow to do this?
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?
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...
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 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.