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.
View 3 RepliesFor 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 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?
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]...
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)
[code]...
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 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]....
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
[code]....
i'm sorting 8GB text file but came up with this error for an investigation
/tmp/sortA3aLjF: No space left on device
is there anyway that sort won't use /tmp?
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.
df -h
[root@system]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdd3 18G 775M 16G 5% /
/dev/hdd1 99M 15M 80M 15% /boot
[Code].....
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.
ibv4l2: error turning on stream: No space left on device
Webcam work in:
fps: 1/30
formate:JPEG/WMV
it works not perfect on guvcview
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?
View 4 Replies View RelatedI 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.
View 9 Replies View RelatedI 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
[code]....
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
[Code]...
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:
Ok, as the title indicates I have a RAID5 array with 4 500GB SATA drives. This is the only drive configuration on the system (i.e. the OS also resides in the RAID array). I'm running CentOS 5 and need to know how to go about increacing the space in the RAID array by replacing the drives with 4 1TB drives.
View 3 Replies View RelatedThe weirdest thing I have ever saw happened today after i rebooted my server.I have an IDE drive with fedora core 12 installed.I have 4 500g sata drives that I made a FD partition on.
Created the raid using mdadm and had a sh script that assembled and mounted.This worked just fine for 4 days and about 6 reboots.then the other day I noticed an odd amount of net traffic coming in and out of the box and took it down to do some router configuring.
After I brought it back up and ran the sh script, I got a weird error, /dev/sdc device was busy. so I did an fdisk /dev/sdc, and sure enough it had a swap space and boot partition. I deleted em, rebooted and now I'm stuck at the grub screen. Somehow my drive names got fubared and I don't know how to recover my system.
I am working on an embedded system, which is an USB MSC device that supports some vendor specific scsi commands. I am using FC10 laptop as USB host for testing, and it runs some small apps based on sg3. All has been well for ~ a week. The FC10 laptop is able to communicate with the device and retrieve data. Suddenly, starting from today, the laptop is not able to properly detect the device. When plugged-in, the MSC device is detected as input device (I thought). This is observed from "dmesg" output and changes in "/dev/input/".The device under development is running at full speed. When I connect to winXP, no problem. A windows file explorer pops up, showing the content of the drive.Also, the FC10 has no problem with other USB flash drive (high speed).
View 1 Replies View RelatedI have just bought 4 1TB drives and set up a Software Raid level 5. Using Disk Utility tool I have created a GPT partition table and now when I want to create a partition, I get:
Error creating partition: helper exited with exit code 1: In part_add_partition: device_file=/dev/md0, start=0, size=3000610848768, type=
Entering MS-DOS parser (offset=0, size=3000610848768)
MSDOS_MAGIC found
found partition type 0xee => protective MBR for GPT
[Code].....
it does say nothing about creating an partition on the /dev/md0, although Gnome Disk Utility allows to do that - if I just run mkfs.xsf /dev/md0 - it works fine, yet Disk Utility tells me that disk has not been partitioned, see image:
I am setting up a Raid5 and torture testing it. I added two eSata ports to my machine. When a drive is installed in that eSata port and the machine then booted up the device name (e.g. /dev/sdc) is inserted in the middle of my Raid devices. And that is just one example of how the device names can change.I did a search on 'static device names' but I saw nothing directly related to Raid. What I did see were suggestions to create udev rules based on UUID. But that was for single disks, not Raid, where each drive/partition in the raid array appears to have the same UUID.I'm surprised this does not come up in the various Raid howtos because it is impossible to keep a Raid array intact without solving this problem unless the machine is never touched thereafter.
View 1 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?
Something weird happened last night and my raid5 failed. I am trying to re activate it and see if my data is dead or what. When I run mdadm -Asv /dev/md0 I get
Code:
mdadm: looking for devices for /dev/md0
mdadm: cannot open device /dev/dm-1: Device or resource busy
mdadm: /dev/dm-1 has wrong uuid.
mdadm: cannot open device /dev/dm-0: Device or resource busy
mdadm: /dev/dm-0 has wrong uuid.
mdadm: cannot open device /dev/sde2: Device or resource busy
mdadm: /dev/sde2 has wrong uuid.
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: /dev/sde1 has wrong uuid.
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: /dev/sde has wrong uuid.
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: /dev/sdd has wrong uuid.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has wrong uuid.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: /dev/sdb has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.