General :: How To Determine The Space Left On A Tape
May 3, 2010
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.
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)
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 ... :'-(
I have a lvm with 5 disk, I've been doing some benchmarks on the file-system with this lvm know I would like to remove one pv from the volume, I've tried
Code: # pvmove -v /dev/sde1 Finding volume group "test-vol" No extents available for allocation and also
I am a both rhel5 and fedora user.I can not configure my Samsung syncmaster 632nw monitor to display full screen at 1360X768.There is huge black space both left and right side of the monitor. I have tried many times to solve it but unable to do it.The max screen resolution is 1024*768 and minimum is 640*480.
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 am running Ubuntu 10.04 amd64. So I have just returned from a week vacation to see that my / is full. When I had left, the ~80G partition was only consuming around 40G of space. I feel like this is a bug and i haven't tried a custom kernel yet to see if it is kernel level. Here is all the good information though to help debug:
Code: mount # mount /dev/mapper/pdc_cfefedbci3 on / type ext4 (rw,noatime,user_xattr,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev)
[Code].....
I am using a fakeraid with dm-raid on a raid0 for my /dev/mapper discs. I just wonder if anyone else is getting this error or if it is a problem with ext4.
I have been using an LTO-5 Ultrium-3000 tape drive connected to an ATTO HBA without problem. I can control the tape drive using "mt -f /dev/nst0" and have been able to make successful backups using cpio, tar, and dump/restore. I followed some instructions on the web about how to install the HPE Library and Tape Tools application (version 4.21) which relies on conversion of a rpm to a deb file. The software seems to have been installed correctly and runs. However the hardware scan function does not recognize my tape drive. The following is suggested in the user manual if the tape device is not recognized by the software under Linux:
1. Login as root. 2. Edit the following file: vi /etc/modules.conf 3. Add the following line as appropriate: add options scsi_mod max_scsi_luns=128 4. Reboot the computer.
The problem is I don't have an /etc/modules.conf and am not sure exactly which file would be equivalent? If this is even the correct solution.
My tape drive is controllable and functions well using "mt -f /dev/nst0 status" so it seems to be a matter of LT&T software to detect the tape drive.
At the risk of providing too much info here some, possibly relevant, output from lshw
*-pci:3 description: PCI bridge product: 6 Series/C200 Series Chipset Family PCI Express Root Port 1 vendor: Intel Corporation physical id: 1c bus info: pci@0000:00:1c.0 version: b5
On one of my servers the "free" command tells me that a lot of swap space are in use. What I'd like to do is to determine which processes have been swapped out. I tried issuing "top" and sort by the "swap" column, but this doesn't seem to provide correct values - when performing the same excersize on another server with close to no pages swapped out, the sum when adding the swap value for each process greatly exceeds the swap usage reported by "free". So how do I go about determining the swap space used for individual processes?
I am looking at getting a DLT drive for my network; however, I have never used the tar command with a tape drive. What happens if the data is larger then 1 tape? Does the tar application automatically span tapes or do I need to use switches so it spans multipule tapes? Right now my Full backup will take 2 or 3 tapes.
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 have dell poweredge 830 server with tape drive and RHEL 4 running on it....the issue i am facing is,i am unable to insert the tape as i had ejected the tape forcefully from it....
i tried to do a listing of the contents backedup on tape and it got struck in middle throwing below error,
/dev/st0:device input/output error. after which i was unable to eject the tape using mt -f /dev/st0 rewoffl
i removed the tape by holding the eject button and now when i try to insert another tape, it's unable to take the tape in to tape drive...
I've tried doing all except reeboting the server, can any one help me out in this issue, hope the blow information may help in debugging the issue... code....
I am using LVM2 and have shrinked my /home partition and extended my / partition but I'm not sure if I used all the free space when growing my / partition. How can I find out? I prefer using the terminal if there is a graphical way to do this but I would like to know both ways if there are two ways.
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.
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
The 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.
I 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.
