Re: No space left on device ...
On Sat, May 20, 2023 at 08:12:39AM +, Albretch Mueller wrote: > On 5/17/23, Jeffrey Walton wrote: > > On Wed, May 17, 2023 at 1:06 PM Dan Ritter wrote: > >> Albretch Mueller wrote: > >> Assuming you have network access close to boot time, you might > >> want to run an NTP daemon to get the time from a selection of > >> other servers. > > Nowadays, time is something that can be handled locally with a Gossip > > protocol. Let your watch or phone or television or toaster tell your > > computer what time it is. No need for a remote call to a server. > > > >> Debian runs a pool, which is configured by default in ntp-server > >> and chrony, at least. > > I have to use a Debian Live DVD to access the Internet; so, probably > these utilities should be included. > > lbrtchx > Hi, Most of this message from you is very off topic: please bear in mind that this goes to a *wide* variety of people and places. That's one of the reasons why the FAQ posted each month asks people to not post political and other opinions that may be meaningless to large parts of the world. Can we try and get this list back onto topics that are constructive (and don't last for thirty or more posts in one thread), please? Thanks for your consideration. Andy Cater [For the Debian Community Team]
Re: No space left on device ...
On 5/17/23, Jeffrey Walton wrote:
> On Wed, May 17, 2023 at 1:06 PM Dan Ritter wrote:
>> Albretch Mueller wrote:
>> Assuming you have network access close to boot time, you might
>> want to run an NTP daemon to get the time from a selection of
>> other servers.
> Nowadays, time is something that can be handled locally with a Gossip
> protocol. Let your watch or phone or television or toaster tell your
> computer what time it is. No need for a remote call to a server.
>
>> Debian runs a pool, which is configured by default in ntp-server
>> and chrony, at least.
I have to use a Debian Live DVD to access the Internet; so, probably
these utilities should be included. I can't entertain functional
illusions about taking care of my business in any other way. It is
thoroughly annoying and time wasting, but you also "live and learn". I
have been running dmesg and comparing its output as I access the
Internet (all problems go away when you close all browser windows and
disconnect yourself from the Internet) one of their jokes is making
the hard drive crazily rev and then you find the message:
[70778.162999] Thunar[1669]: segfault at 48 ip 55a03faca360 sp
7ffc52dc2088 error 4 in thunar[55a03fa9f000+7f000]
When our AI-based "Miss Information" Godmother gets angry with you ;-)
They are even able to change BIOS settings while your computer is
running through your browser!
// __ List BIOS Settings using PowerShell (Posted onJune 22, 2016AuthorMrNetTek)
http://eddiejackson.net/wp/?p=10909
~
so, at some point I will have to get diffable dumps of the BIOS in
addition to running diffing the output of dmesg.
The main problems I am having are brought about by:
1) the BIOS of the laptop I use these days having wireless networking
which is started by the BIOS (at some point I will try dealing with
that by disconnecting the built-in hardware). In the ways I understand
"reality" (and "quid est verum?", right?) the BIOS should not be
taking care of networking, "have a mind of its own";
2) javascript is the main attacking framework used by "the
government" and how can you use the Internet these days with
javascript disabled? (it would be like trying to breathe underwater)
3) "the government" is using AI for their societally-wide
Zersetzung-like "social control" (as "good Christian" "freedom lovers"
call -repression-)
How do I know, am so sure about it? Well, this is a pattern that I
have been noticing for 30 years I have lived in "'the' land of 'the'
'free' ...": you post an "unAmerican" comment (here in the U.S. you
can say "eff 'the establishment' ..." and no one cares about it, in
fact, you didn't say anything even in a physical/acoustic sense, but
in a "lexical priming" kind of way, if you elaborate on your
statements even if in a jestful way, "patriots"/their "'patriotic'
'AI'" seem to go crazy about it).
This is what happened last/this time: you notice the people you get
the news from (I don't watch TV, read newspapers, nor am I on social
networks, ... in fact, I wonder from where people find the time for
such thoroughly stupid, morally debasing pastimes) have been black
holed -again-, to then after some barely sophisticated be found here:
// __ Introducing: Miss Information, Your Fairy Government Godmother
https://odysee.com/@Odysee:8/missinfo:d
~
About our new Godmother "Miss Information". Do you remember when she
decided it was about time for "Vladimir Putin" to suicide Michael
Hastings for spreading misinformation?
https://en.wikipedia.org/wiki/Michael_Hastings_(journalist)
Two days after the crash, the Los Angeles Police Department declared
that there were no signs of foul play.[65] The coroner's report ruled
the death to be an accident.[66] An autopsy showed that the cause of
death was massive blunt force trauma consistent with a high-speed
crash.[66]
~
I cracked jokes around how unjust and non-sensical was it that that
not only "unAmerican", but also, as if it were not enough, "pro
Russia" "Vladimir Putin" suicided Hastings when all he did was the
same as Biden did only 20 years earlier. Do we need either "Vladimir
Putin" or our, not exactly fair and clarifying government appointed
Godmother?
~
The aim of that Zersetzung-like (as they "freedom-lovingly" call it
themselves: "relentless pursuit"), which was thoroughly "studied" with
social animals and humans as part of their „Operativer Vorgänge"
("operational procedures") by the East German stasi is not to kill
you, but thoroughly destroy your existence to the point of inducing
the belief in people of committing suicide as a way "not to let them
get you" ... Does it actually work? Well, you don't have to take it
from me; Ian Murdock, Aaron Swartz, Sandra Bland, Myron May, John
McAfee, ... will tell you.
I know, as some of you have told me, that "the U.S. Constitution
doesn't include any clauses relating to 'privacy'" ..., that "all I am
saying is being archived" ... (yes, "we the people" in the U.S. have
started to talk as if
Re: No space left on device ...
On Thu, 2023-05-18 at 10:42 -0600, Charles Curley wrote: > On Thu, 18 May 2023 10:07:05 -0400 > Default User wrote: > > > If I am running systemd-timesyncd on a single-user, internet- > > connected > > computer, not needing to serve time signals to any other device, > > would > > there be any reason to use ntp instead? > > NTP is a protocol, like TCP or UDP. One program that uses NTP is > ntpd, > which Debian packages in the confusingly named package ntp. > > To answer your question, probably not. I'm not even sure you can run > ntpd and systemd-timesyncd on the same computer. I have ntpd on two > computers here, both available as local time servers on my network. > Everything else uses systemd-timesyncd and uses the two ntpd > machines. > Got it. That's sort of what I was thinking. Thanks!
Re: No space left on device ...
On Thu, 18 May 2023 10:07:05 -0400 Default User wrote: > If I am running systemd-timesyncd on a single-user, internet-connected > computer, not needing to serve time signals to any other device, would > there be any reason to use ntp instead? NTP is a protocol, like TCP or UDP. One program that uses NTP is ntpd, which Debian packages in the confusingly named package ntp. To answer your question, probably not. I'm not even sure you can run ntpd and systemd-timesyncd on the same computer. I have ntpd on two computers here, both available as local time servers on my network. Everything else uses systemd-timesyncd and uses the two ntpd machines. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: No space left on device ...
On Thu, 2023-05-18 at 10:20 -0400, Dan Ritter wrote: > Default User wrote: > > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > > > On Wed, 17 May 2023 12:48:28 -0400 > > > Dan Ritter wrote: > > > > > > > Assuming you have network access close to boot time, you might > > > > want to run an NTP daemon to get the time from a selection of > > > > other servers. > > > > > > Concur. > > > > > > > > > > > Debian runs a pool, which is configured by default in ntp- > > > > server > > > > and chrony, at least. > > > > > > Also systemd-timesyncd, which is probably the easiest of these > > > three > > > to > > > set up. > > > > > > > > > > > > If I am running systemd-timesyncd on a single-user, internet- > > connected > > computer, not needing to serve time signals to any other device, > > would > > there be any reason to use ntp instead? > > systemd-timesyncd, ntp-server and chrony are all supposed to > speak the NTP protocol. Nothing, to a first approximation, uses > any other protocol to set time reliably for the system as a > whole. > > -dsr- Okay, thanks!
Re: No space left on device ...
Default User wrote: > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > > On Wed, 17 May 2023 12:48:28 -0400 > > Dan Ritter wrote: > > > > > Assuming you have network access close to boot time, you might > > > want to run an NTP daemon to get the time from a selection of > > > other servers. > > > > Concur. > > > > > > > > Debian runs a pool, which is configured by default in ntp-server > > > and chrony, at least. > > > > Also systemd-timesyncd, which is probably the easiest of these three > > to > > set up. > > > > > > > If I am running systemd-timesyncd on a single-user, internet-connected > computer, not needing to serve time signals to any other device, would > there be any reason to use ntp instead? systemd-timesyncd, ntp-server and chrony are all supposed to speak the NTP protocol. Nothing, to a first approximation, uses any other protocol to set time reliably for the system as a whole. -dsr-
Re: No space left on device ...
On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote: > On Wed, 17 May 2023 12:48:28 -0400 > Dan Ritter wrote: > > > Assuming you have network access close to boot time, you might > > want to run an NTP daemon to get the time from a selection of > > other servers. > > Concur. > > > > > Debian runs a pool, which is configured by default in ntp-server > > and chrony, at least. > > Also systemd-timesyncd, which is probably the easiest of these three > to > set up. > > If I am running systemd-timesyncd on a single-user, internet-connected computer, not needing to serve time signals to any other device, would there be any reason to use ntp instead? [INB4: "If it ain't broke, don't fix it!"] :)
Re: No space left on device ...
On Wed, 17 May 2023 12:48:28 -0400 Dan Ritter wrote: > Assuming you have network access close to boot time, you might > want to run an NTP daemon to get the time from a selection of > other servers. Concur. > > Debian runs a pool, which is configured by default in ntp-server > and chrony, at least. Also systemd-timesyncd, which is probably the easiest of these three to set up. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: No space left on device ...
On Wed, May 17, 2023 at 1:06 PM Dan Ritter wrote: > > Albretch Mueller wrote: > > In case someone runs into the same problem, for some reason I can't > > quite understand "sudo hwclock --set" wasn't working. Someone helped > > me: > > > > https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html > > https://wiki.debian.org/DateTime > > > > and "date" worked! Which I has always taken to be a wrapper command to > > hwclock! > > > > $ date > > Sun 07 Aug 2022 01:35:45 PM UTC > > > > $ sudo date --set "2023-05-16 11:13:00 AM" > > Tue 16 May 2023 11:13:00 AM UTC > > > > $ sudo hwclock --get > > 2022-05-11 02:02:36.883165+00:00 > > > > $ sudo hwclock --systohc > > > > $ sudo hwclock --get > > 2023-05-16 11:15:22.564093+00:00 > > Assuming you have network access close to boot time, you might > want to run an NTP daemon to get the time from a selection of > other servers. ++. Let the software handle it. Nowadays, time is something that can be handled locally with a Gossip protocol. Let your watch or phone or television or toaster tell your computer what time it is. No need for a remote call to a server. > Debian runs a pool, which is configured by default in ntp-server > and chrony, at least. Jeff
Re: No space left on device ...
Albretch Mueller wrote: > In case someone runs into the same problem, for some reason I can't > quite understand "sudo hwclock --set" wasn't working. Someone helped > me: > > https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html > https://wiki.debian.org/DateTime > > and "date" worked! Which I has always taken to be a wrapper command to > hwclock! > > $ date > Sun 07 Aug 2022 01:35:45 PM UTC > > $ sudo date --set "2023-05-16 11:13:00 AM" > Tue 16 May 2023 11:13:00 AM UTC > > $ sudo hwclock --get > 2022-05-11 02:02:36.883165+00:00 > > $ sudo hwclock --systohc > > $ sudo hwclock --get > 2023-05-16 11:15:22.564093+00:00 Assuming you have network access close to boot time, you might want to run an NTP daemon to get the time from a selection of other servers. Debian runs a pool, which is configured by default in ntp-server and chrony, at least. -dsr-
Re: No space left on device ...
> Yes, I did. I had to reset the BIOS to "factory settings" which also > changed the clock time which then I couldn't change with hwclock ... "Another day another problem": computer clock back to BIOS factory settings Your Computer Clock is Wrong: Your computer thinks it is 8/7/2022, which prevents Firefox from connecting securely. To visit www.google.com, update your computer clock in your system settings to the current date, time, and time zone, and then refresh www.google.com. www.google.com has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site. ~ In case someone runs into the same problem, for some reason I can't quite understand "sudo hwclock --set" wasn't working. Someone helped me: https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html https://wiki.debian.org/DateTime and "date" worked! Which I has always taken to be a wrapper command to hwclock! $ date Sun 07 Aug 2022 01:35:45 PM UTC $ sudo date --set "2023-05-16 11:13:00 AM" Tue 16 May 2023 11:13:00 AM UTC $ sudo hwclock --get 2022-05-11 02:02:36.883165+00:00 $ sudo hwclock --systohc $ sudo hwclock --get 2023-05-16 11:15:22.564093+00:00 "Amazing!" lbrtchx
Re: No space left on device ...
> Has this ever worked in the past? It is my understanding that the Linux NTFS > driver is read-only. > Mounting how exactly? And what is the contents of /proc/mounts? Maybe > you mounted the partition read only? Well, actually, yes. This is how I have been mounting the Windows NTFS of my laptop and my employer's as well without any problems whatsoever. I just open the file browser/viewer and click the drive to mount it in order to unmount, eject it you right click on it. It works. >> $ cp "No space left on device" > No_space_left_on_device.txt >> bash: No_space_left_on_device.txt: No space left on device >That *shouldn't* work. I get: my mistake I meant: echo "No space left on device" > No_space_left_on_device.txt > Does anybody read signatures any more? Apparently, some of us do. ;-) My obfuscation of the path didn't relate to the error. > First thing to try is to boot back into Windows and see if there is a message about the drive. If so, let Windows 'fix' it. I've had cases where the drive was not cleanly unmounted and Linux has mounted it read-only. Windows was able to repair it, whatever the problem was. THis is the second thing I did. I booted into the BIOS and run an exhaustive test/diagnostic on every physical part of it twice. It all tested fine, including the hard drive. Then something spooky happened. I couldn't care less about Windows, but then "'the BIOS' 'told me'" it would fix my laptop and it effing did without messing with any of my data!!! Then I could boot into windows again ... once I checked everything was fine I went back to my Debian live ways. Every electronic thing I use has a mind of its own, that makes your life so much more enjoyable! ;-) > Did you disable the Fast Boot feature in Windows? Yes, I did. I had to reset the BIOS to "factory settings" which also changed the clock time which then I couldn't change with hwclock ... but when I booted the laptop with a network access at the library. It did reset the clock apparently using WIndows time servers. That fix took me like four hours (dealing with the nonsense of the installation ...), but at the end of th eday I was able to go back to my do, do, do, ... mode. Thank you, lbrtchx
Re: No space left on device ...
Albretch Mueller writes: > I have been mounting an NTFS file system on a Windows laptop without > any problems whatsoever with a Debian Live DVD: Mounting how exactly? And what is the contents of /proc/mounts? Maybe you mounted the partition read only?
Re: No space left on device ...
Joe wrote: > > First thing to try is to boot back into Windows and see if there is a > message about the drive. If so, let Windows 'fix' it. I've had cases > where the drive was not cleanly unmounted and Linux has mounted it > read-only. Windows was able to repair it, whatever the problem was. Oh! Reminds me on the fact, that Fast Boot of Windows locks the disk devices, and they can't be accessed by any other system on the same computer, even after Windows shutdown - to avoid disk corruption. Did you disable the Fast Boot feature in Windows? https://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/ Best regards, Klaus. -- Klaus Singvogel GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Re: No space left on device ...
On Sun, 14 May 2023 21:04:01 -0400 Jeffrey Walton wrote: > On Sun, May 14, 2023 at 8:32 PM Albretch Mueller > wrote: > > > > I have been mounting an NTFS file system on a Windows laptop without > > any problems whatsoever with a Debian Live DVD: > > > > $ uname -a > > Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) > > x86_64 GNU/Linux > > > > and even though Linux utilities are telling me I do have space on > > the drive: > > > > $ date; sudo df -h | grep "Filesystem\|/dev/sd" > > Sun 14 May 2023 06:55:23 PM UTC > > Filesystem Size Used Avail Use% Mounted on > > /dev/sda1 286G 167G 120G 59% /media/user/60320G593EB7250F > > $ > > > > $ date; time sudo du --summarize --human-readable > > /media/user/60320G593EB7250F Sun 14 May 2023 07:13:43 PM UTC > > 166G/media/user/60320G593EB7250F > > > > real0m45.230s > > user 0m1.073s > > sys 0m15.443s > > $ > > > > when I try to save or download a file I consistently get the same > > error message: > > > > $ cp "No space left on device" > No_space_left_on_device.txt > > bash: No_space_left_on_device.txt: No space left on device > > > > that started happening right after a WiFi connection at a library > > was shutdown, which I waited for with my script running, accessing > > the Internet, because I wanted to test such a case. Script > > "gracefully" worked as programmed to do, but that other error > > started right after the connection was cut off. > > > > I have no idea how could those two things be related! Why would that > > happen? Any suggestions, please? > > I don't know if it's related... > > I seem to recall the GNUlib folks talking about a cp bug on sparse > files. It looks like it may be fixed in coreutils release 9.2 > (2023-03-20): > https://github.com/coreutils/coreutils/blob/master/NEWS#L233 > > If I recall correctly, it had something to do with the way > copy_file_range worked. (Or maybe, it did not work as expected). > First thing to try is to boot back into Windows and see if there is a message about the drive. If so, let Windows 'fix' it. I've had cases where the drive was not cleanly unmounted and Linux has mounted it read-only. Windows was able to repair it, whatever the problem was. -- Joe
Re: No space left on device ...
On Mon, 15 May 2023 00:32:01 + Albretch Mueller wrote: > when I try to save or download a file I consistently get the same > error message: > > $ cp "No space left on device" > No_space_left_on_device.txt > bash: No_space_left_on_device.txt: No space left on device That *shouldn't* work. I get: charles@jhegaala:~$ cp "No space left on device" > No_space_left_on_device.txt cp: missing destination file operand after 'No space left on device' Try 'cp --help' for more information. charles@jhegaala:~$ But I do get a file created with length 0. Try echo instead of cp: charles@jhegaala:~$ echo "No space left on device" > No_space_left_on_device.txt charles@jhegaala:~$ cat No_space_left_on_device.txt No space left on device charles@jhegaala:~$ ll No_space_left_on_device.txt -rw-r--r-- 1 charles charles 24 May 14 21:04 No_space_left_on_device.txt charles@jhegaala:~$ Also, I have no reason to believe from what you've shown that your current directory is /media/user/60320G593EB7250F. Did you run cd /media/user/60320G593EB7250F before running the above commands? I would expect to get an out-of-space error if I were still on the CD. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: No space left on device ...
On Sun, May 14, 2023 at 8:32 PM Albretch Mueller wrote: > > I have been mounting an NTFS file system on a Windows laptop without > any problems whatsoever with a Debian Live DVD: > > $ uname -a > Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) > x86_64 GNU/Linux > > and even though Linux utilities are telling me I do have space on the drive: > > $ date; sudo df -h | grep "Filesystem\|/dev/sd" > Sun 14 May 2023 06:55:23 PM UTC > Filesystem Size Used Avail Use% Mounted on > /dev/sda1 286G 167G 120G 59% /media/user/60320G593EB7250F > $ > > $ date; time sudo du --summarize --human-readable > /media/user/60320G593EB7250F > Sun 14 May 2023 07:13:43 PM UTC > 166G/media/user/60320G593EB7250F > > real0m45.230s > user0m1.073s > sys 0m15.443s > $ > > when I try to save or download a file I consistently get the same error > message: > > $ cp "No space left on device" > No_space_left_on_device.txt > bash: No_space_left_on_device.txt: No space left on device > > that started happening right after a WiFi connection at a library was > shutdown, which I waited for with my script running, accessing the > Internet, because I wanted to test such a case. Script "gracefully" > worked as programmed to do, but that other error started right after > the connection was cut off. > > I have no idea how could those two things be related! Why would that > happen? Any suggestions, please? I don't know if it's related... I seem to recall the GNUlib folks talking about a cp bug on sparse files. It looks like it may be fixed in coreutils release 9.2 (2023-03-20): https://github.com/coreutils/coreutils/blob/master/NEWS#L233 If I recall correctly, it had something to do with the way copy_file_range worked. (Or maybe, it did not work as expected). Jeff
No space left on device ...
I have been mounting an NTFS file system on a Windows laptop without any problems whatsoever with a Debian Live DVD: $ uname -a Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux and even though Linux utilities are telling me I do have space on the drive: $ date; sudo df -h | grep "Filesystem\|/dev/sd" Sun 14 May 2023 06:55:23 PM UTC Filesystem Size Used Avail Use% Mounted on /dev/sda1 286G 167G 120G 59% /media/user/60320G593EB7250F $ $ date; time sudo du --summarize --human-readable /media/user/60320G593EB7250F Sun 14 May 2023 07:13:43 PM UTC 166G/media/user/60320G593EB7250F real0m45.230s user0m1.073s sys 0m15.443s $ when I try to save or download a file I consistently get the same error message: $ cp "No space left on device" > No_space_left_on_device.txt bash: No_space_left_on_device.txt: No space left on device that started happening right after a WiFi connection at a library was shutdown, which I waited for with my script running, accessing the Internet, because I wanted to test such a case. Script "gracefully" worked as programmed to do, but that other error started right after the connection was cut off. I have no idea how could those two things be related! Why would that happen? Any suggestions, please? lbrtchx
Re: question regarding no space left on device message
Hi, Semih Ozlem wrote: > However I do not know how to install new programs in knoppix > (still there is apt-get install as a command, but debian packages > no longer seem to work, and I do not know which packages work with > knoppix system, [...] https://www.knopper.net/knoppix/knoppix861-en.html says "Version 8.6.1 of KNOPPIX is based on → Debian/stable (buster), with some packages from Debian/testing and unstable (sid) for newer graphics drivers or desktop software packages. It uses Linux kernel 5.3.5 and Xorg 7.7 (core 1.20.4) for supporting current computer hardware." So a Debian mirror for current stable should be able to provide compatible packages. > I am not sure where to ask the knoppix questions. Try debian-knop...@lists.debian.org https://lists.debian.org/debian-knoppix/ or http://www.knoppix.net/forum/ Have a nice day :) Thomas
Re: question regarding no space left on device message
Hi Thomas, Thank you for your email and recommendation. It seems that knoppix uses less ram. However I do not know how to install new programs in knoppix (still there is apt-get install as a command, but debian packages no longer seem to work, and I do not know which packages work with knoppix system, and I believe this is a forum on debian so I am not sure where to ask the knoppix questions.) I also can not adjust screen brightness, and I had to boot with secure boot disabled. Thomas Schmitt , 21 Ağu 2020 Cum, 14:56 tarihinde şunu yazdı: > Hi, > > Semih Ozlem wrote: > > I used "dd if=isofilename of=devicename" > > So the partition table afterwards is the one which came with the ISO. > MBR based, but accompanied by an invalid GPT. > > Further, this implies that your Live system is only running on RAM > and not using a writable system disk. > > -- > > You could add a data partition on the USB stick to store all extra > data there. But for that you would probably have to set up the partition > usage every time you start the system. (Mount partition, move data from > RAM disk to USB stick, install symbolic link from RAM disk to partition > ...) > > I would not strive for such a contraption, unless for the sake of art. > > > If i'd want to stay with a Live system, i'd use more RAM. > Else i would consider a normal installation, as mentioned by David > Christensen. > > A compromise might be Knoppix, which is prepared to expand its data > partition up to the end of the UBS stick when it gets bootet from that > stick for the first time. (Put the ISO onto the stick like you did > with Debian Live.) > > http://ftp.uni-kl.de/pub/linux/knoppix-dvd/KNOPPIX_V8.6.1-2019-10-14-EN.iso > > http://ftp.uni-kl.de/pub/linux/knoppix-dvd/KNOPPIX_V8.6.1-2019-10-14-EN.iso.sha256.asc > Knoppix might be prepared to put all additionally installed .deb packages > onto the data partition. You'll have to try. > > -- > > > Also if one creates a partition on some device, say /dev/sda becomes > > /dev/sda1 /dev/sda2 /dev/sda3 after partitioning (which can be done with > > gnome disk utility, or gparted, or from the command line, and I forget > the > > exact commands now probably "parted mkpart") then "dd if=isofilename.iso > > of=/dev/sda1" is an instance of placing iso file onto a device that I > use. > > That would be wrong, unless the stick is equipped with an own boot loader > which can chainload the ISO's boot loader from the partition. Something > like is described in > > https://www.pendrivelinux.com/boot-multiple-iso-from-usb-via-grub2-using-linux/#more-5352 > You don't get that from partition editors. > > > > I am not sure about the last option oflag=sync > > It causes the i/o system to take the data only as fast from dd as fast > as it can be written to the stick. No large buffering in RAM shall happen. > It's a good companion for status=progress in order to see steady and > realistic progress messages. > > > Have a nice day :) > > Thomas > >
Re: question regarding no space left on device message
Hi, Semih Ozlem wrote: > I used "dd if=isofilename of=devicename" So the partition table afterwards is the one which came with the ISO. MBR based, but accompanied by an invalid GPT. Further, this implies that your Live system is only running on RAM and not using a writable system disk. -- You could add a data partition on the USB stick to store all extra data there. But for that you would probably have to set up the partition usage every time you start the system. (Mount partition, move data from RAM disk to USB stick, install symbolic link from RAM disk to partition ...) I would not strive for such a contraption, unless for the sake of art. If i'd want to stay with a Live system, i'd use more RAM. Else i would consider a normal installation, as mentioned by David Christensen. A compromise might be Knoppix, which is prepared to expand its data partition up to the end of the UBS stick when it gets bootet from that stick for the first time. (Put the ISO onto the stick like you did with Debian Live.) http://ftp.uni-kl.de/pub/linux/knoppix-dvd/KNOPPIX_V8.6.1-2019-10-14-EN.iso http://ftp.uni-kl.de/pub/linux/knoppix-dvd/KNOPPIX_V8.6.1-2019-10-14-EN.iso.sha256.asc Knoppix might be prepared to put all additionally installed .deb packages onto the data partition. You'll have to try. -- > Also if one creates a partition on some device, say /dev/sda becomes > /dev/sda1 /dev/sda2 /dev/sda3 after partitioning (which can be done with > gnome disk utility, or gparted, or from the command line, and I forget the > exact commands now probably "parted mkpart") then "dd if=isofilename.iso > of=/dev/sda1" is an instance of placing iso file onto a device that I use. That would be wrong, unless the stick is equipped with an own boot loader which can chainload the ISO's boot loader from the partition. Something like is described in https://www.pendrivelinux.com/boot-multiple-iso-from-usb-via-grub2-using-linux/#more-5352 You don't get that from partition editors. > I am not sure about the last option oflag=sync It causes the i/o system to take the data only as fast from dd as fast as it can be written to the stick. No large buffering in RAM shall happen. It's a good companion for status=progress in order to see steady and realistic progress messages. Have a nice day :) Thomas
Re: question regarding no space left on device message
Also if one creates a partition on some device, say /dev/sda becomes /dev/sda1 /dev/sda2 /dev/sda3 after partitioning (which can be done with gnome disk utility, or gparted, or from the command line, and I forget the exact commands now probably "parted mkpart") then "dd if=isofilename.iso of=/dev/sda1" is an instance of placing iso file onto a device that I use. Someone one the list recommended additional options " dd if=isofilename of=devicename obs=4M status=progress oflag=sync" so that the writing process occurs at the right speed (obs option) and it displays progress status, and I am not sure about the last option oflag=sync. but even without these options the writing works. And if anyone has additional comments to this, please enlighten us. Semih Ozlem , 21 Ağu 2020 Cum, 14:23 tarihinde şunu yazdı: > I used "dd if=isofilename of=devicename" and when using this command I use > a blank usb or one with a partition, and device name gets filled with the > partition that will be overwritten if anything was previously on it. > > Thomas Schmitt , 21 Ağu 2020 Cum, 14:14 tarihinde şunu > yazdı: > >> Hi, >> >> Semih Ozlem wrote: >> > Hi Thomas, >> >> (You need to reply to the list, not to my mail address directly.) >> >> >> > the computer has 4gb RAM >> >> This should suffice for a RAM based session. >> But if you add large software packages, then 4 GB for everything will at >> some point not be enough. >> >> >> > >> https://cdimage.debian.org/mirror/cdimage/archive/10.3.0-live/amd64/iso-hybrid/ >> >> ... and which of the .iso images exactly ? >> >> >> > I burned the iso from a previous live usb >> >> "Burn" is not really a technical term in repect to USB sticks. >> >> So you did something to put the ISO onto the stick. What exactly ? >> >> >> > I did not change anything on the usb stick other than installing it >> (only >> > set up partitions before burning the iso so that a separate portion >> would >> > remain to save files) >> >> Well, some of the potential methods to put the ISO onto stick will as >> first overwrite any previous partitioning. If you partitioning survived >> unchenged, then your "burning" method probably unpacks to ISO in some way. >> >> But you should really give more tangible info which could help to >> reproduce your problems. Don't assume that we know what you do. >> >> >> Have a nice day :) >> >> Thomas >> >>
Re: question regarding no space left on device message
I used "dd if=isofilename of=devicename" and when using this command I use a blank usb or one with a partition, and device name gets filled with the partition that will be overwritten if anything was previously on it. Thomas Schmitt , 21 Ağu 2020 Cum, 14:14 tarihinde şunu yazdı: > Hi, > > Semih Ozlem wrote: > > Hi Thomas, > > (You need to reply to the list, not to my mail address directly.) > > > > the computer has 4gb RAM > > This should suffice for a RAM based session. > But if you add large software packages, then 4 GB for everything will at > some point not be enough. > > > > > https://cdimage.debian.org/mirror/cdimage/archive/10.3.0-live/amd64/iso-hybrid/ > > ... and which of the .iso images exactly ? > > > > I burned the iso from a previous live usb > > "Burn" is not really a technical term in repect to USB sticks. > > So you did something to put the ISO onto the stick. What exactly ? > > > > I did not change anything on the usb stick other than installing it (only > > set up partitions before burning the iso so that a separate portion would > > remain to save files) > > Well, some of the potential methods to put the ISO onto stick will as > first overwrite any previous partitioning. If you partitioning survived > unchenged, then your "burning" method probably unpacks to ISO in some way. > > But you should really give more tangible info which could help to > reproduce your problems. Don't assume that we know what you do. > > > Have a nice day :) > > Thomas > >
Re: question regarding no space left on device message
Hi, Semih Ozlem wrote: > Hi Thomas, (You need to reply to the list, not to my mail address directly.) > the computer has 4gb RAM This should suffice for a RAM based session. But if you add large software packages, then 4 GB for everything will at some point not be enough. > https://cdimage.debian.org/mirror/cdimage/archive/10.3.0-live/amd64/iso-hybrid/ ... and which of the .iso images exactly ? > I burned the iso from a previous live usb "Burn" is not really a technical term in repect to USB sticks. So you did something to put the ISO onto the stick. What exactly ? > I did not change anything on the usb stick other than installing it (only > set up partitions before burning the iso so that a separate portion would > remain to save files) Well, some of the potential methods to put the ISO onto stick will as first overwrite any previous partitioning. If you partitioning survived unchenged, then your "burning" method probably unpacks to ISO in some way. But you should really give more tangible info which could help to reproduce your problems. Don't assume that we know what you do. Have a nice day :) Thomas
Re: question regarding no space left on device message
On 2020-08-21 02:35, Semih Ozlem wrote: Hi, When I try installing some programs while running debian live from a usb, I get a message saying that there is no space left on device. I presume this means that the space allocated on the usb for debian is not enough to install the program in question. I am wondering if there is a way to attach another device so that this problem can be overcome. I am wondering how to do tell debian system that the externally attached memory device can be used to install programs. Thank you As others have mentioned, perhaps you want "persistence". This allows you to use the free space on the USB device to save data and/or enhance the live OS. That said, I prefer to do a full install onto a good USB 3.0 flash drive. This allows me to customize the stick exactly how I want. Graphical desktop use can be choppy, due to a lack of a RAM cache, NCQ, etc., and other SSD/HDD performance features. But, I find these very useful for portable maintenance and trouble-shooting. I have used USB flash drives as system drives 24x7 in low-end servers. They worked. I assume continuous frequent writes would rapidly consume the lifespan of a USB flash drive. Some people use high-endurance SD cards and an SD-to-USB adapter in such use-cases. Finally, there are very high-performance USB flash drives available with SSD controllers -- Corsair GTX, possibly others. However, I expect they are optimized for large sequential I/O rather than the small random I/O that system drives experience. David
Re: question regarding no space left on device message
Hi Brian, It helps partially, but I think (I have not yet tried it in a particular case) the problem is not in var/cache/apt/archives ... Even if the necessary packages are stored someplace else, if the system you are running is low on space, then the system won't be able to complete the installation, and give a no space left on device error. Brian , 21 Ağu 2020 Cum, 13:33 tarihinde şunu yazdı: > On Fri 21 Aug 2020 at 12:35:02 +0300, Semih Ozlem wrote: > > > Hi, > > > > When I try installing some programs while running debian live from a > usb, I > > get a message saying that there is no space left on device. > > I presume this means that the space allocated on the usb for debian is > not > > enough to install the program in question. > > I am wondering if there is a way to attach another device so that this > > problem can be overcome. I am wondering how to do tell debian system that > > the externally attached memory device can be used to install programs. > > I wonder whether Section 4.4.3 of the Release Notes helps? > > -- > Brian. > >
Re: question regarding no space left on device message
Hi, Semih Ozlem wrote: > When I try installing some programs while running debian live from a usb, I > get a message saying that there is no space left on device. > I presume this means that the space allocated on the usb for debian is not > enough to install the program in question. More people could join the presumption tournament if you'd give more tangible info: - How much RAM has your computer ? - URL of the ISO image ? - Size of the USB stick ? - How did the ISO get onto the USB stick ? - Did you do more sysadmin work on the USB stick before booting it ? In the most plain setting i would presume that Debian Live only uses a RAM disk but no partitions of the USB stick. In this case you'd probably get more wiggle room by using a computer with more RAM. Adding storage devices, like a partition on the USB stick which uses the remaining free space, might help too. This is the topic of "Live with Persistence". (When googling, beware of old descriptions.) Have a nice day :) Thomas
Re: question regarding no space left on device message
On Fri 21 Aug 2020 at 12:35:02 +0300, Semih Ozlem wrote: > Hi, > > When I try installing some programs while running debian live from a usb, I > get a message saying that there is no space left on device. > I presume this means that the space allocated on the usb for debian is not > enough to install the program in question. > I am wondering if there is a way to attach another device so that this > problem can be overcome. I am wondering how to do tell debian system that > the externally attached memory device can be used to install programs. I wonder whether Section 4.4.3 of the Release Notes helps? -- Brian.
question regarding no space left on device message
Hi, When I try installing some programs while running debian live from a usb, I get a message saying that there is no space left on device. I presume this means that the space allocated on the usb for debian is not enough to install the program in question. I am wondering if there is a way to attach another device so that this problem can be overcome. I am wondering how to do tell debian system that the externally attached memory device can be used to install programs. Thank you
Re: "No space left on device" error, but df shows plenty of space
On Thursday, 2 February 2017 10:05:58 PYST Andy Smith wrote: > Hi Kynn, > > On Wed, Feb 01, 2017 at 10:43:37AM -0500, Kynn Jones wrote: > > On Wed, Feb 1, 2017 at 7:24 AM, Andy Smith wrote: > > > On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > > > > Unfortunately, I'll never know what the problem was. > > > > > > Do you use btrfs? > > > > Not that I'm aware of. (FWIW, if I run `mount | grep -i btrfs` (as root), > > I get no output.) > > Okay, so not a btrfs issue. > > > > What does "df -i" report now, after your reboot when things are > > > working? > > > > > # df -i > > Filesystem Inodes IUsedIFree IUse% Mounted on > > /dev/sda5 24264704 1464023 228006817% / > > …and that doesn't show as being anywhere near full, so it most > likely wasn't that either. > > Well I suppose it could have been processes holding open deleted > files, though it would have to have been some really big files in > that case, as your filesystem didn't show as being anywhere near > full. > > Cheers, > Andy let me guess: facts: /var is on the same partition as / there is plenty of space and there are free i-nodes but anyway you got error apt-get resulted in "no space left on device" you rebooted and the error disappeared => / was mounted as r/o for some reason (unclean filesystem e.g.)
Re: "No space left on device" error, but df shows plenty of space
Hi Kynn, On Wed, Feb 01, 2017 at 10:43:37AM -0500, Kynn Jones wrote: > On Wed, Feb 1, 2017 at 7:24 AM, Andy Smith wrote: > > On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > > > Unfortunately, I'll never know what the problem was. > > > > Do you use btrfs? > > Not that I'm aware of. (FWIW, if I run `mount | grep -i btrfs` (as root), > I get no output.) Okay, so not a btrfs issue. > > What does "df -i" report now, after your reboot when things are > > working? > > # df -i > Filesystem Inodes IUsedIFree IUse% Mounted on > /dev/sda5 24264704 1464023 228006817% / …and that doesn't show as being anywhere near full, so it most likely wasn't that either. Well I suppose it could have been processes holding open deleted files, though it would have to have been some really big files in that case, as your filesystem didn't show as being anywhere near full. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: "No space left on device" error, but df shows plenty of space
On Wed, Feb 1, 2017 at 7:24 AM, Andy Smith wrote: > Hi Kynn, > > On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > > After the machine rebooted, I was able to run `dpkg-reconfigure ntp` > > without error. > > > > Unfortunately, I'll never know what the problem was. > > Do you use btrfs? > Not that I'm aware of. (FWIW, if I run `mount | grep -i btrfs` (as root), I get no output.) What does "df -i" report now, after your reboot when things are > working? > # df -i Filesystem Inodes IUsedIFree IUse% Mounted on /dev/sda5 24264704 1464023 228006817% / udev4115384 445 41149391% /dev tmpfs 4117499 735 41167641% /run tmpfs 4117499 14 41174851% /dev/shm tmpfs 4117499 5 41174941% /run/lock tmpfs 4117499 13 41174861% /sys/fs/cgroup tmpfs 4117499 10 41174891% /run/user/1000 Unfortunately, I don't have the output of `df -i` before I rebooted. Best, kj
Re: "No space left on device" error, but df shows plenty of space
Hi Kynn, On Tue, Jan 31, 2017 at 06:42:39PM -0500, Kynn Jones wrote: > After the machine rebooted, I was able to run `dpkg-reconfigure ntp` > without error. > > Unfortunately, I'll never know what the problem was. Do you use btrfs? What does "df -i" report now, after your reboot when things are working? Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: "No space left on device" error, but df shows plenty of space
Hi everyone! Thank you for your suggestions. They taught some new tricks. As it happened, I had to reboot the machine for an unrelated (?) reason (monitor would not wake from sleep). After the machine rebooted, I was able to run `dpkg-reconfigure ntp` without error. Unfortunately, I'll never know what the problem was. Thank you all for your help. kj On Tue, Jan 31, 2017 at 8:28 AM, Brad Rogers wrote: > On Tue, 31 Jan 2017 08:01:00 -0500 > Kynn Jones wrote: > > Hello Kynn, > > >When I tried to install `ntp`, there was a "No space left on device" at > >the end of `apt-get`'s output, but `df` shows no shortage of space: > > I've no idea whether this is relevant to your case, but it's possible to > be unable to use disk space if there are insufficient inodes left to > store the relevant directory/file info. AIUI, a "No space..." error is > the result. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > Just stop and take a second > U & Ur Hand - P!nk >
Re: "No space left on device" error, but df shows plenty of space
On Tue, 31 Jan 2017 08:01:00 -0500 Kynn Jones wrote: Hello Kynn, >When I tried to install `ntp`, there was a "No space left on device" at >the end of `apt-get`'s output, but `df` shows no shortage of space: I've no idea whether this is relevant to your case, but it's possible to be unable to use disk space if there are insufficient inodes left to store the relevant directory/file info. AIUI, a "No space..." error is the result. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Just stop and take a second U & Ur Hand - P!nk pgpsfbxcxn5Rs.pgp Description: OpenPGP digital signature
Re: "No space left on device" error, but df shows plenty of space
Hi Kynn, On Tue, Jan 31, 2017 at 08:01:00AM -0500, Kynn Jones wrote: > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/sda5 381993164 206410036 156155956 57% / […] > # dpkg-reconfigure ntp > Error: No space left on device > > How can I troubleshoot this problem further? Does /dev/sda5 have a btrfs filesystem on it? Type "mount" and look for the "type" part. If so, these problems are common with btrfs; see btrfs wiki and/or linux-btrfs mailing list: https://btrfs.wiki.kernel.org/index.php/FAQ#Help.21_Btrfs_claims_I.27m_out_of_space.2C_but_it_looks_like_I_should_have_lots_left.21 If not, could be things like deleted files that are still open (see "lsof" output, look for "(deleted)". Or maybe ran out of inodes. See "df -i" out to check that. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: "No space left on device" error, but df shows plenty of space
On 01/31/2017 08:03 AM, Eduardo M KALINOWSKI wrote: On Ter, 31 Jan 2017, Kynn Jones wrote: Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: Try 'df -i', you're probably out of inodes. I guess I should have read your reply before sending one suggesting the same precise thing. Sorry, Tony -- http://tonybaldwin.me all tony, all the time
Re: "No space left on device" error, but df shows plenty of space
On 01/31/2017 08:01 AM, Kynn Jones wrote: Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda5 381993164 206410036 156155956 57% / udev 10240 0 10240 0% /dev tmpfs6588000 9676 6578324 1% /run tmpfs 16469996 108 16469888 1% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 16469996 0 16469996 0% /sys/fs/cgroup tmpfs3294000 8 3293992 1% /run/user/1000 According to `df`, the maximum percent usage is 57%. So I tried `dpgk-reconfigure ntp` (as root), and got the same error: # dpkg-reconfigure ntp Error: No space left on device update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Error: No space left on device How can I troubleshoot this problem further? try doing $ df -i This shows inodes. I once had a problem where I could no longer write to a disk, because all of the inodes were occupied due to not properly rotating some log(s). Let us know if that reveals anything seemingly significant. Tony -- http://tonybaldwin.me all tony, all the time
Re: "No space left on device" error, but df shows plenty of space
On Ter, 31 Jan 2017, Kynn Jones wrote: Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: Try 'df -i', you're probably out of inodes. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
"No space left on device" error, but df shows plenty of space
Hi everyone! When I tried to install `ntp`, there was a "No space left on device" at the end of `apt-get`'s output, but `df` shows no shortage of space: # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda5 381993164 206410036 156155956 57% / udev 10240 0 10240 0% /dev tmpfs6588000 9676 6578324 1% /run tmpfs 16469996 108 16469888 1% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 16469996 0 16469996 0% /sys/fs/cgroup tmpfs3294000 8 3293992 1% /run/user/1000 According to `df`, the maximum percent usage is 57%. So I tried `dpgk-reconfigure ntp` (as root), and got the same error: # dpkg-reconfigure ntp Error: No space left on device update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Error: No space left on device How can I troubleshoot this problem further? # uname -ar Linux luna 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux Thanks in advance! kj
Re: dpkg "no space left on device" errors (lots of room left)
On 10/22/2014 07:10 PM, Michael Biebl wrote: The faulty package is system-config-printer which linterally creates millions of files in /tmp [1]. As as side-effect, you'll see that rebooting your system can take ages, when /tmp is being cleaned up [2] and you likely see output like this: "a start job is running for Create Volatile files and directories (xx minutes / no limit)" Ext4 is highly inefficient apparently when dealing with huge amount of files in on directory [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766092#62 Michael, Thanks - that is exactly what I am seeing although it only takes ~15 minutes to clean /tmp on reboot. I will watch for an update and be careful while printing! John -- --- John Bleichert-syb...@earthlink.net The heat from below can burn your eyes out! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/544907f6.5040...@earthlink.net
Re: dpkg "no space left on device" errors (lots of room left)
Am 22.10.2014 um 21:53 schrieb Andrei POPESCU: > On Mi, 22 oct 14, 15:45:58, John Bleichert wrote: >> >> This is the second time this has happened, so something is eating up inodes >> on /. I am going to run some aptitude tests and see what happens. >> >> Any idea what the OS is doing during boot to clean up temporary space? Is it >> something I can run manually from a terminal? > > There is some buggy software (cups?) creating a lot of symlinks in /tmp > or so. The faulty package is system-config-printer which linterally creates millions of files in /tmp [1]. As as side-effect, you'll see that rebooting your system can take ages, when /tmp is being cleaned up [2] and you likely see output like this: "a start job is running for Create Volatile files and directories (xx minutes / no limit)" Ext4 is highly inefficient apparently when dealing with huge amount of files in on directory [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766092#62 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: dpkg "no space left on device" errors (lots of room left)
On 10/22/2014 03:55 PM, Peter Palfrader wrote: On Wed, 22 Oct 2014, John Bleichert wrote: Try a df -i You may have run out of inodes Iain: Bingo - I was down to a single-digit number of inodes on / ... The box became unusable and had to be reset. Upon booting the OS "cleaned up temporary files" and now I'm back to an IUse% of 4% (which sounds about right, I don't store any non-OS data on / ). Maybe you want to make your /tmp a tmpfs? Edit /etc/default/tmpfs and set RAMTMP to yes, then reboot. Cheers, I will look into it - thanks for the suggestion! John -- --- John Bleichert-syb...@earthlink.net The heat from below can burn your eyes out! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54480c82.2070...@earthlink.net
Re: dpkg "no space left on device" errors (lots of room left)
On 10/22/2014 03:53 PM, Andrei POPESCU wrote: There is some buggy software (cups?) creating a lot of symlinks in /tmp or so. Kind regards, Andrei Interesting that you mention that - cups did kick the bucket this morning and become unusable. I will watch out for it in the future - thanks! John -- --- John Bleichert-syb...@earthlink.net The heat from below can burn your eyes out! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54480c66.6090...@earthlink.net
Re: dpkg "no space left on device" errors (lots of room left)
On Wed, 22 Oct 2014, John Bleichert wrote: > >Try a df -i You may have run out of inodes > > Iain: Bingo - I was down to a single-digit number of inodes on / ... > > The box became unusable and had to be reset. Upon booting the OS > "cleaned up temporary files" and now I'm back to an IUse% of 4% > (which sounds about right, I don't store any non-OS data on / ). Maybe you want to make your /tmp a tmpfs? Edit /etc/default/tmpfs and set RAMTMP to yes, then reboot. Cheers, -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141022195543.gf19...@anguilla.noreply.org
Re: dpkg "no space left on device" errors (lots of room left)
On Mi, 22 oct 14, 15:45:58, John Bleichert wrote: > > This is the second time this has happened, so something is eating up inodes > on /. I am going to run some aptitude tests and see what happens. > > Any idea what the OS is doing during boot to clean up temporary space? Is it > something I can run manually from a terminal? There is some buggy software (cups?) creating a lot of symlinks in /tmp or so. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: dpkg "no space left on device" errors (lots of room left)
On 10/22/2014 03:00 PM, Iain M Conochie wrote: Try a df -i You may have run out of inodes Cheers Iain Iain: Bingo - I was down to a single-digit number of inodes on / ... The box became unusable and had to be reset. Upon booting the OS "cleaned up temporary files" and now I'm back to an IUse% of 4% (which sounds about right, I don't store any non-OS data on / ). This is the second time this has happened, so something is eating up inodes on /. I am going to run some aptitude tests and see what happens. Any idea what the OS is doing during boot to clean up temporary space? Is it something I can run manually from a terminal? Thanks for the hint, John -- --- John Bleichert-syb...@earthlink.net The heat from below can burn your eyes out! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54480976.7080...@earthlink.net
Re: dpkg "no space left on device" errors (lots of room left)
Doug wrote: > On 10/22/2014 03:01 PM, Sven Hartge wrote: >> John Bleichert wrote: >> >>> As of a few days ago I keep getting errors similar to the following when >>> running aptitude upgrade: >> >>> >>> dpkg: error processing archive >>> /var/cache/apt/archives/cups-server-common_1.7.5-5_all.deb (--unpack): >>> unable to create >>> `/usr/share/cups/templates/ru/set-printer-options-header.tmpl.dpkg-new' >>> (while processing >>> `./usr/share/cups/templates/ru/set-printer-options-header.tmpl'): No >>> space left on device >>> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) >>> >> >> >>> Filesystem Size Used Avail Use% Mounted on >>> /dev/sda1 106G 31G 70G 31% / >> >> What is the output of "df -i"? >> >> I guess you ran out of inodes. > How many inodes are available? As many as "df -i" reports. > What remedy is available if you do run out of them? a) delete files or b) remake filesystem with better parameters or c) use a filesystem which has no fixed amount of inodes, like XFS Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ab3blcs42...@mids.svenhartge.de
Re: dpkg "no space left on device" errors (lots of room left)
On 10/22/2014 03:01 PM, Sven Hartge wrote: John Bleichert wrote: As of a few days ago I keep getting errors similar to the following when running aptitude upgrade: dpkg: error processing archive /var/cache/apt/archives/cups-server-common_1.7.5-5_all.deb (--unpack): unable to create `/usr/share/cups/templates/ru/set-printer-options-header.tmpl.dpkg-new' (while processing `./usr/share/cups/templates/ru/set-printer-options-header.tmpl'): No space left on device dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Filesystem Size Used Avail Use% Mounted on /dev/sda1 106G 31G 70G 31% / What is the output of "df -i"? I guess you ran out of inodes. S° How many inodes are available? What remedy is available if you do run out of them? --doug -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/544800de.2090...@optonline.net
Re: dpkg "no space left on device" errors (lots of room left)
On 22/10/14 19:49, John Bleichert wrote: Hello All, As of a few days ago I keep getting errors similar to the following when running aptitude upgrade: dpkg: error processing archive /var/cache/apt/archives/cups-server-common_1.7.5-5_all.deb (--unpack): unable to create `/usr/share/cups/templates/ru/set-printer-options-header.tmpl.dpkg-new' (while processing `./usr/share/cups/templates/ru/set-printer-options-header.tmpl'): No space left on device dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) I've gotten strange errors like this with /tmp too outside of upgrades. I've got arseloads of space available on all my mount points: Try a df -i You may have run out of inodes Cheers Iain And now, of course, there are dependency issues all over the place. Any suggestions on how how to sort this out? I can provide a great deal more info. jessie/sid Thanks, John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5447fee7.5010...@thargoid.co.uk
Re: dpkg "no space left on device" errors (lots of room left)
John Bleichert wrote: > As of a few days ago I keep getting errors similar to the following when > running aptitude upgrade: > > dpkg: error processing archive > /var/cache/apt/archives/cups-server-common_1.7.5-5_all.deb (--unpack): > unable to create > `/usr/share/cups/templates/ru/set-printer-options-header.tmpl.dpkg-new' > (while processing > `./usr/share/cups/templates/ru/set-printer-options-header.tmpl'): No > space left on device > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > > Filesystem Size Used Avail Use% Mounted on > /dev/sda1 106G 31G 70G 31% / What is the output of "df -i"? I guess you ran out of inodes. S° -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/9b3bjqb42...@mids.svenhartge.de
dpkg "no space left on device" errors (lots of room left)
Hello All, As of a few days ago I keep getting errors similar to the following when running aptitude upgrade: dpkg: error processing archive /var/cache/apt/archives/cups-server-common_1.7.5-5_all.deb (--unpack): unable to create `/usr/share/cups/templates/ru/set-printer-options-header.tmpl.dpkg-new' (while processing `./usr/share/cups/templates/ru/set-printer-options-header.tmpl'): No space left on device dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) I've gotten strange errors like this with /tmp too outside of upgrades. I've got arseloads of space available on all my mount points: Filesystem Size Used Avail Use% Mounted on /dev/sda1 106G 31G 70G 31% / udev 10M 0 10M 0% /dev tmpfs 1.6G 972K 1.6G 1% /run tmpfs 5.0M 8.0K 5.0M 1% /run/lock tmpfs 4.1G 34M 4.1G 1% /run/shm /dev/sdb1 459G 258G 178G 60% /data /dev/sdc1 962G 256G 658G 28% /localbu /dev/sdc2 436G 71M 414G 1% /remotebu /dev/sdc3 437G 116G 299G 28% /music cgroup 12K 0 12K 0% /sys/fs/cgroup tmpfs 1.6G 12K 1.6G 1% /run/user/1000 tmpfs 1.6G 0 1.6G 0% /run/user/0 And now, of course, there are dependency issues all over the place. Any suggestions on how how to sort this out? I can provide a great deal more info. jessie/sid Thanks, John -- --- John Bleichert-syb...@earthlink.net The heat from below can burn your eyes out! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5447fc27.9070...@earthlink.net
Re: No space left on device (28) but device is NOT full!
On Wed, Nov 6, 2013 at 4:43 PM, Neal Murphy wrote: > On Wednesday, November 06, 2013 07:44:18 AM Wawrzek Niewodniczanski wrote: >> >> This is a bit off main topic, but definitely 'on' for this list. Lets >> imagine a scenario there is nothing to delete on the troublesome >> partition, but there is another disk. What would be the best tool to >> move data to another partition having the same size, but higher number >> of inodes? > > Assuming the problem is /var/log is part of the root filesystem and is crammed > with millions of files. Assume other drive is /dev/sdb. The general process is > as follows. > > 1. Reboot to single-user > 2. Add partition #1 to /dev/sdb > 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes > 4. 'mount /dev/sdb1 /mnt' > 5. 'cd /var/log; find . -depth | cpio -pdv /mnt' > 6. 'if [ $? -eq 0 ]; then cd ..; mv log log-; rm -rf log-; fi&' > 7. 'mkdir log; chmod 755 log > 8. 'echo "/dev/sdb1 /var/log reiserfs defaults,notail 0 1" >> /etc/fstab' > 9. 'wait' > 10. 'umount /mnt; init 6' Recommending the use of reiserfs is wrong. The Debian installer's development version's kernel no longer supports reiserfs (see [1]) so it's safe to assume that reiserfs support'll be dropped from Debian at some point. You'd have to ask the Debian kernel maintainers whether it'll be dropped in Debian 8 or 9. [1] From the "linux (3.10.1-1)" changelog: * udeb: Remove obsolete and unsupported drivers and filesystems - Remove ppa from scsi-modules - Remove floppy-modules, irda-modules, parport-modules, plip-modules, qnx4-modules, reiserfs-modules, ufs-modules -- Ben Hutchings Tue, 16 Jul 2013 02:06:53 +0100 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sy+mdun-qr618ektyyomvpx16wrurvuaucs2aifs9r...@mail.gmail.com
Re: No space left on device (28) but device is NOT full!
On Wed, 6 Nov 2013 21:45:28 -0800 un...@physics.ubc.ca (unruh) wrote: > In linux.debian.user, you wrote: > > On Mon, 04 Nov 2013 21:51:26 -0600 > > Stan Hoeppner wrote: > > > > ... > > > >> Food for thought: your /dev/sda7 is an EXT filesystem of 26GB with 1.7M > >> inodes. XFS would give you ~23M inodes on a 26GB filesystem. > > > > An ext[2-4] filesystem can be created with any desired number inodes by > > invoking 'mkfs.ext[2-4] -N nnn'. > > Irrelevant in this case. It is almost certainly a misconfigured > logrotate (eg filename* as the file pattern) which exponentially grows > the number of inodes. No number would be enough.Each day the number of > files double. You cannot win against an exponential. Yes, it's irrelevant to this case - but your comment is irrelevant to my point, which was merely to counter the implication that XFS has some advantage over ext* in the matter of inodes. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131107083151.317a638f7acf1263b7ed8...@gmail.com
Re: No space left on device (28) but device is NOT full!
On Mon, 04 Nov 2013 21:51:26 -0600 Stan Hoeppner wrote: ... > Food for thought: your /dev/sda7 is an EXT filesystem of 26GB with 1.7M > inodes. XFS would give you ~23M inodes on a 26GB filesystem. An ext[2-4] filesystem can be created with any desired number inodes by invoking 'mkfs.ext[2-4] -N nnn'. Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131107002536.6e0351b50afcf65844329...@gmail.com
Re: No space left on device (28) but device is NOT full!
On Wednesday, November 06, 2013 12:11:33 PM Beco wrote: > On 6 November 2013 13:43, Neal Murphy wrote: > > Assuming the problem is /var/log is part of the root filesystem and is > > crammed with millions of files. Assume other drive is /dev/sdb. The > > general process is as follows. > > > > 1. Reboot to single-user > > 2. Add partition #1 to /dev/sdb > > 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes > > 4. 'mount /dev/sdb1 /mnt' > > 5. 'cd /var/log; find . -depth | cpio -pdv /mnt' > > 6. 'if [ $? -eq 0 ]; then cd ..; mv log log-; rm -rf log-; fi&' > > 7. 'mkdir log; chmod 755 log' > > 8. 'echo "/dev/sdb1 /var/log reiserfs defaults,notail 0 1" >> /etc/fstab' > > 9. 'wait' > > 10. 'umount /mnt; init 6' > > Hi Neal, > > I think I'm going to ask about the easier part: > > What is "9. wait" for? You want the background delete to complete before rebooting. If it already finished, wait returns immediately. N -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311061246.43209.neal.p.mur...@alum.wpi.edu
Re: No space left on device (28) but device is NOT full!
Neal Murphy wrote: > 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes Really? ReiserFS 3 is dead, IMHO and ReiserFS 4 was never included in any vanilla kernel. I'd suggest XFS or a properly configured ext4. Sure, ext4 has a fixed set of inodes, but properly configured and sized for the task, you should never run out of them. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4a6gjb6o0...@mids.svenhartge.de
Re: No space left on device (28) but device is NOT full!
On Wed, Nov 06, 2013 at 11:43:09AM -0500, Neal Murphy wrote: > 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes Before opting for ReiserFS (version 3), users would be advised to do some reading on the current level of support it attracts in the kernel, and possibly seek out some filesystem comparisons in order to make an informed filesystem choice. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131106171725.gb27...@bryant.redmars.org
Re: No space left on device (28) but device is NOT full!
On 6 November 2013 13:43, Neal Murphy wrote: > Assuming the problem is /var/log is part of the root filesystem and is crammed > with millions of files. Assume other drive is /dev/sdb. The general process is > as follows. > > 1. Reboot to single-user > 2. Add partition #1 to /dev/sdb > 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes > 4. 'mount /dev/sdb1 /mnt' > 5. 'cd /var/log; find . -depth | cpio -pdv /mnt' > 6. 'if [ $? -eq 0 ]; then cd ..; mv log log-; rm -rf log-; fi&' > 7. 'mkdir log; chmod 755 log > 8. 'echo "/dev/sdb1 /var/log reiserfs defaults,notail 0 1" >> /etc/fstab' > 9. 'wait' > 10. 'umount /mnt; init 6' > Hi Neal, I think I'm going to ask about the easier part: What is "9. wait" for? Thx, Beco. -- Dr Beco A.I. researcher "For the things we have to learn before we can do them, we learn by doing them" (Aristotle) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caluyw2x+vyf-h4i_yxgzdsnc2b7+iuxyeq4zqxdjgy7yyow...@mail.gmail.com
Re: No space left on device (28) but device is NOT full!
On Wednesday, November 06, 2013 07:44:18 AM Wawrzek Niewodniczanski wrote: > This is a bit off main topic, but definitely 'on' for this list. Lets > imagine a scenario there is nothing to delete on the troublesome > partition, but there is another disk. What would be the best tool to > move data to another partition having the same size, but higher number > of inodes? Assuming the problem is /var/log is part of the root filesystem and is crammed with millions of files. Assume other drive is /dev/sdb. The general process is as follows. 1. Reboot to single-user 2. Add partition #1 to /dev/sdb 3. 'mkreiserfs /dev/sdb1' # to avoid the whole issue of inodes 4. 'mount /dev/sdb1 /mnt' 5. 'cd /var/log; find . -depth | cpio -pdv /mnt' 6. 'if [ $? -eq 0 ]; then cd ..; mv log log-; rm -rf log-; fi&' 7. 'mkdir log; chmod 755 log 8. 'echo "/dev/sdb1 /var/log reiserfs defaults,notail 0 1" >> /etc/fstab' 9. 'wait' 10. 'umount /mnt; init 6' -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311061143.09913.neal.p.mur...@alum.wpi.edu
Re: No space left on device (28) but device is NOT full!
On 5 November 2013 02:30, Tazman Deville wrote: > On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: >>Hi, >> >>Did you check inodes usage? (df -i) >> >>I could be inodes availability rather than block availability. [...] > I have no idea what the significance of this is, but > df -i gives > $ df -i > FilesystemInodes IUsed IFree IUse% Mounted on > /dev/sda71729920 1729920 0 100% / > > So, yeah...inodes, but I'm ignorant of what that means, > or how to resolve that. [...] This is a bit off main topic, but definitely 'on' for this list. Lets imagine a scenario there is nothing to delete on the troublesome partition, but there is another disk. What would be the best tool to move data to another partition having the same size, but higher number of inodes? Thanks, Wawrzek -- Dr Wawrzyniec Niewodniczańskior Wawrzek for short PhD in Quantum Chemistry & MSc in Molecular Engineering WWW: http://wawrzek.name E-MAIL: j...@wawrzek.name Linux User #177124 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAC7-vpCHd3V0E235JXaZTbfYE5e4z9OeMXTbG9-Vh-b�u...@mail.gmail.com
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 5, 2013 at 11:29 AM, Tazman Deville wrote: > On Tue, Nov 05, 2013 at 08:34:37AM +0900, Joel Rees wrote: >> [...] >> The first thing that I check when I get disk full errors but the disks >> are not full is the permissions. And the second thing should be the inodes, but I wasn't thinking that direction yesterday. Glad someone else was. >>Sometimes, software just assumes that >> any time the system refuses to write it's that the disk is full. >> >> Then you should check whether you've set quotas up. In Java, there >> would be policies to check. And so forth. > > [...] > I'm unclear as to what java policies have to do with this, > but I know diddley about Java. Java has policies, which are kind of like the Java's runtime's implementation of file permissions (but not really). Anyway, if the current php has something similar (Last time I used php they seemed to be "thinking about adding that".), that might have been something to check. Line noise, as it turned out. I'd kind of want to figure out why the popularity contest started misbehaving. And report a bug anyway, if I had the time. There shouldn't be any sudden changes to the popcorn infrastructure for squeeze yet, should there. -- Joel Rees Be careful where you see conspiracy. Look first in your own heart. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caar43ipsanhf-acb7sunmq0fs+1a-ooo+rk6sirohrz6zej...@mail.gmail.com
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 04:54:19PM +, Jonathan Dowland wrote: > The binary size effects the initial load-up time which, for small > numbers of files/short execution times, may be the lions share of > the total execution time. However as you point out, for orders of > magnitute like 500,000; it's dwarfed by the algorithm. I agree with you. I assumed if OP needed to remove all that popcon logs - there would be large amount of those files. > I'm quite amazed how much faster your perl implementation was. I > can only imagine that nobody has ever been troubled by find's > performance enough to work on it. This points to find not taking > advantage of parallelism (and also to potential improvements in > speed even for your perl implementation). Well, the primary usage of find is to find files, not to delete them. And find shows reasonable speed if you need to delete medium amount of files. Besides, deleting that amount of files is a rare unusual task, so using custom tools to do it is only fitting. Half-million is a small amount. Once I had to purge ~200m files - now that was slow. > > Basically, the difference is in the fact that find uses fstatat64 > > syscall for each file, and this perl one-liner uses lstat64 and stat64 > > syscalls. Use strace to check it in your environment. On another OS > > results could be different. > > So you believe the discrepancy is entirely down to the difference > between fstat64 and lstat/stat64? I find that hard to believe. I > suspect find is just not very efficient. I never bothered to see find source to check how they do it. Or kernel source for the implementation of these syscalls. Still, the fact stands - both find and one-liner use unlink (find uses unlink64, but that should not be relevant), one-liner does double amount of stat syscalls compared to the find, yet it's faster. Probably C implementation would be even more faster, but I'm to lazy to do it. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105184625.GA28050@x101h
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 07:15:19PM +0400, Reco wrote: > On Tue, Nov 05, 2013 at 02:29:10PM +, Jonathan Dowland wrote: > > On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote: > > > find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f > > > > I idly wonder (don't know) to what extend find might parallelize the > > unlinks with -delete. A cursory scan of the semantics would suggest it > > could potentially do so: it's not clear that a single unlink failing > > should stop future unlinks (merely spew errors and consider the -delete > > operation as a whole to have failed) > > xargs parallelism is optional. The point is that you have one process > which finds files, and another one (or another group of) who are > deleting files. Helps utilizing multiple cpus. I know about xargs and parallelism. I was wondering whether find implemented parallelism internally, when it could, and afaics the semantics of -delete do not proclude it doing so. I did not investigate whether it does, but… > $ time find -type f -delete … > real4m27.799s …suggests it doesn't. (I'm appalled by that!) > It's not the binary size which matters, it's the algorithm: The binary size effects the initial load-up time which, for small numbers of files/short execution times, may be the lions share of the total execution time. However as you point out, for orders of magnitute like 500,000; it's dwarfed by the algorithm. I'm quite amazed how much faster your perl implementation was. I can only imagine that nobody has ever been troubled by find's performance enough to work on it. This points to find not taking advantage of parallelism (and also to potential improvements in speed even for your perl implementation). > Basically, the difference is in the fact that find uses fstatat64 > syscall for each file, and this perl one-liner uses lstat64 and stat64 > syscalls. Use strace to check it in your environment. On another OS > results could be different. So you believe the discrepancy is entirely down to the difference between fstat64 and lstat/stat64? I find that hard to believe. I suspect find is just not very efficient. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105165419.ga2...@bryant.redmars.org
Re: No space left on device (28) but device is NOT full!
On 11/05/2013 05:33 PM, Reco wrote:
> Hi.
>
> On Tue, Nov 05, 2013 at 04:25:13PM +0200, Lars Noodén wrote:
>>> On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote:
perl -e 'for(){((stat)[9]<(unlink))}'
>>
>> I have two questions. Why < before unlink and why stat[9] there?
>
> You have to pass unlink something to delete. Stat is called
> without an argument, hence $_ is used for stat too.
> '<' is used to give unlink something to work with. Try it like this:
>
> perl -e 'for(<*>){((stat)[9])>(printf)}'
Ok. It's just there and does not play any functional role.
perl -e 'for(<*>){((stat)[9]);printf}'
>> stat[9] is mtime.
>
> Files are sorted in directory inode by mtime. That saves you sorting
> all the file list in directory.
Interesting.
Thanks,
/Lars
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52791242.7050...@gmail.com
Re: No space left on device (28) but device is NOT full!
Hi.
On Tue, Nov 05, 2013 at 04:25:13PM +0200, Lars Noodén wrote:
> > On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote:
> >> perl -e 'for(){((stat)[9]<(unlink))}'
>
> I have two questions. Why < before unlink and why stat[9] there?
You have to pass unlink something to delete. Stat is called
without an argument, hence $_ is used for stat too.
'<' is used to give unlink something to work with. Try it like this:
perl -e 'for(<*>){((stat)[9])>(printf)}'
> stat[9] is mtime.
Files are sorted in directory inode by mtime. That saves you sorting
all the file list in directory.
Reco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131105153315.GB19598@x101h
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 02:29:10PM +, Jonathan Dowland wrote:
> On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote:
> > find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f
>
> I idly wonder (don't know) to what extend find might parallelize the
> unlinks with -delete. A cursory scan of the semantics would suggest it
> could potentially do so: it's not clear that a single unlink failing
> should stop future unlinks (merely spew errors and consider the -delete
> operation as a whole to have failed)
xargs parallelism is optional. The point is that you have one process
which finds files, and another one (or another group of) who are
deleting files. Helps utilizing multiple cpus.
> > Arguably the fastest way to delete all this mess should be
> >
> > perl -e 'for(){((stat)[9]<(unlink))}'
>
> Not sure why loading perl (>1.6M) should be faster than find (~300K)
> and I think '-delete' behaviour is essentially unlink under the hood.
It's not the binary size which matters, it's the algorithm:
$ for x in $(seq 1 50); do echo somefile > $x; done
$ time perl -e 'for(<*>){(stat)[9]>(unlink))}'
real0m24.047s
user0m4.785s
sys 0m16.926s
$ for x in $(seq 1 50); do echo somefile > $x; done
$ time find -type f -delete
real4m27.799s
user0m0.831s
sys 0m17.961s
Basically, the difference is in the fact that find uses fstatat64
syscall for each file, and this perl one-liner uses lstat64 and stat64
syscalls. Use strace to check it in your environment.
On another OS results could be different.
Reco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131105151518.GA19598@x101h
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote:
> find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f
I idly wonder (don't know) to what extend find might parallelize the
unlinks with -delete. A cursory scan of the semantics would suggest it
could potentially do so: it's not clear that a single unlink failing
should stop future unlinks (merely spew errors and consider the -delete
operation as a whole to have failed)
> Arguably the fastest way to delete all this mess should be
>
> perl -e 'for(){((stat)[9]<(unlink))}'
Not sure why loading perl (>1.6M) should be faster than find (~300K)
and I think '-delete' behaviour is essentially unlink under the hood.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131105142910.gd28...@bryant.redmars.org
Re: No space left on device (28) but device is NOT full!
> On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote:
>> perl -e 'for(){((stat)[9]<(unlink))}'
I have two questions. Why < before unlink and why stat[9] there?
stat[9] is mtime.
Regards,
/Lars
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5278ffc9.4000...@gmail.com
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 03:13:10PM +0400, Reco wrote:
> Hi.
>
> On Tue, Nov 05, 2013 at 09:41:58AM +, Jonathan Dowland wrote:
> > On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote:
> > > find . -name 'popularity-*' | xargs rm -rf
> >
> > Sorry, opportunity for a bit of golf. Find has a built-in for deleting
> > files:
> >
> > > find . -type f -name 'popularity-*' -delete
> >
> > I'd also be rather wary of invoking rm -rf with the results of find
> > output.
>
> If you're unsure (and you should!) if filenames contain spaces, that
> should more appopriate.
>
> find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f
>
>
> Arguably the fastest way to delete all this mess should be
>
> perl -e 'for(){((stat)[9]<(unlink))}'
>
>
> Reco
Learning perl has been on my todo list for about 8 years now...
./t
--
http://tazmandevil.info
taz hungry
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131105141304.gc30...@myownsite.me
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 09:41:58AM +, Jonathan Dowland wrote: > On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote: > > find . -name 'popularity-*' | xargs rm -rf > > Sorry, opportunity for a bit of golf. Find has a built-in for deleting > files: > > > find . -type f -name 'popularity-*' -delete > > I'd also be rather wary of invoking rm -rf with the results of find > output. > This occurred to me, but I figured, since I was in /var/log, and I was careful to use the name "popuarlity", it couldn't really hose anything important. Just log files. ./t -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105141210.gb30...@myownsite.me
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 02:52:52AM -0600, Stan Hoeppner wrote: > On 11/5/2013 1:21 AM, Richard Hector wrote: > > On 05/11/13 16:51, Stan Hoeppner wrote: > >> Second, you have a serious problem here because it is your root > >> filesystem that has run out of inodes. You need to ask yourself why you > >> have 1.7M files in your rootfs. That's very dumb. > > > > Or perhaps "That's not generally advisable." or similar. > > > > Richard > > Or perhaps you should remove your politically correct inspired, > sensitivity trainer ground, colored lenses so you can correctly read and > comprehend what I typed. > Personally, I would have used "that's really f--king stupid", for my part. (Mind, I clarified that I didn't use up those inodes. Some glitch with popularity-contest, and I'm wondering if I should file a bug. Something that drastic, I would surprised if it wasn't already caught, but then, I haven't seen anybody else on here discussing the same problem. I did NOT manipulate its logrotate stuff, or anything that should have caused it to do that.) ./t -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105141042.ga30...@myownsite.me
Re: No space left on device (28) but device is NOT full!
Hi.
On Tue, Nov 05, 2013 at 09:41:58AM +, Jonathan Dowland wrote:
> On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote:
> > find . -name 'popularity-*' | xargs rm -rf
>
> Sorry, opportunity for a bit of golf. Find has a built-in for deleting
> files:
>
> > find . -type f -name 'popularity-*' -delete
>
> I'd also be rather wary of invoking rm -rf with the results of find
> output.
If you're unsure (and you should!) if filenames contain spaces, that
should more appopriate.
find . -type f -name 'popularity-*' -print0 | xargs -0rn 20 rm -f
Arguably the fastest way to delete all this mess should be
perl -e 'for(){((stat)[9]<(unlink))}'
Reco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131105111310.GA11995@x101h
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 05:28:16AM +0100, Tazman Deville wrote: > find . -name 'popularity-*' | xargs rm -rf Sorry, opportunity for a bit of golf. Find has a built-in for deleting files: > find . -type f -name 'popularity-*' -delete I'd also be rather wary of invoking rm -rf with the results of find output. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105094158.ga28...@bryant.redmars.org
Re: No space left on device (28) but device is NOT full!
On 11/5/2013 1:21 AM, Richard Hector wrote: > On 05/11/13 16:51, Stan Hoeppner wrote: >> Second, you have a serious problem here because it is your root >> filesystem that has run out of inodes. You need to ask yourself why you >> have 1.7M files in your rootfs. That's very dumb. > > Or perhaps "That's not generally advisable." or similar. > > Richard Or perhaps you should remove your politically correct inspired, sensitivity trainer ground, colored lenses so you can correctly read and comprehend what I typed. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5278b1e4.4070...@hardwarefreak.com
Re: No space left on device (28) but device is NOT full!
On 11/4/2013 10:28 PM, Tazman Deville wrote: ... > Got it! > find . -name 'popularity-*' | xargs rm -rf > (passes the files to rm one at a time). Glad you got it squared away Anthony. Normally I'd suggest filing a bug report against the problem application, but since the system is Squeeze it's probably already been addressed. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5278a96e.7040...@hardwarefreak.com
Re: No space left on device (28) but device is NOT full!
On Tuesday, November 05, 2013 02:21:36 AM Richard Hector wrote: > On 05/11/13 16:51, Stan Hoeppner wrote: > > Second, you have a serious problem here because it is your root > > filesystem that has run out of inodes. You need to ask yourself why you > > have 1.7M files in your rootfs. That's very dumb. > > Or perhaps "That's not generally advisable." or similar. 'Contra-indicated' is a suitable military term. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201311050247.36507.neal.p.mur...@alum.wpi.edu
Re: No space left on device (28) but device is NOT full!
On 05/11/13 16:51, Stan Hoeppner wrote: > Second, you have a serious problem here because it is your root > filesystem that has run out of inodes. You need to ask yourself why you > have 1.7M files in your rootfs. That's very dumb. Or perhaps "That's not generally advisable." or similar. Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52789c80.9090...@walnut.gen.nz
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 05:14:34AM +0100, Tazman Deville wrote: > On Mon, Nov 04, 2013 at 09:51:26PM -0600, Stan Hoeppner wrote: > > On 11/4/2013 8:30 PM, Tazman Deville wrote: > > > On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: > > >>Hi, > > >> > > >>Did you check inodes usage? (df -i) > > >> > > >>I could be inodes availability rather than block availability. > > > > > > > > > AHA! > > > > > > df -i gives > > > $ df -i > > > FilesystemInodes IUsed IFree IUse% Mounted on > > > /dev/sda71729920 1729920 0 100% / > > > > > > > First it means you're using a filesystem with a small fixed number of > > inodes, obviously EXT. > > > > Second, you have a serious problem here because it is your root > > filesystem that has run out of inodes. You need to ask yourself why you > > have 1.7M files in your rootfs. That's very dumb. That's what /home > > and /data and other places are to be used for. > > I'm not the dummy that filled up my / > Before this, it was barely more than hafl full (well, df -h > shows I'm only using 9.6gb of the 16gb there). > Also, that hdd is old. > I ran fedora core 4 on it.That's how old it is. > Then I tried Ubuntu Dapper Duck on it, and some old PCLinuxOS, > and eventually, when it was already about 3 years old, > installed Lenny on it, my first Debian (and I'm still here!). > But I formatted it as ext3 when I installed lenny, > and from there just upgraded to squeeze with apt, so > haven't changed the fs. Haven't had any reason to change it. > > > So, anyway, after some digging around, I find there are some billions > of log files in /var/log/ for popularity-contest. > > Like, this is 0.005% of the output of > sudo find . -xdev -type f | cut -d "/" -f 2 | sort | uniq -c | sort -n > > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.2.gz > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.2.gz.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.2.gz > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1.1.1 > 1 > popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.2.gz > > I've aptitude purged popularity-contest, now. > I checked the logrotate file, and it has a maxage of 7, meaning these > are all a week old or younger, too. > Very, very strange. > Now I have to figure out how to get rid of them. > Even trying to rm -rf a small subset, like *.1.2.gz.1.2.gz.1* > gives me > Argument list too long. > Got it! find . -name 'popularity-*' | xargs rm -rf (passes the files to rm one at a time). The machine in question, btw, now simply sits quietly in a corner of my office, serving up the scuttle, a little dokuwiki for my personal use, and a couple of other useful things, sometimes serves as a sandbox for trying stuff out before use on a production server. It's a trooper, and, until today, has never given me any real problems. My main box (one I'm typing on) runs Wheezy, with 4x2.8ghz AMD APU, and 16gb ram, 2Tb storage, etc. ./taz -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105042816.gc14...@myownsite.me
Re: No space left on device (28) but device is NOT full!
On Mon, Nov 04, 2013 at 09:51:26PM -0600, Stan Hoeppner wrote: > On 11/4/2013 8:30 PM, Tazman Deville wrote: > > On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: > >>Hi, > >> > >>Did you check inodes usage? (df -i) > >> > >>I could be inodes availability rather than block availability. > > > > > > AHA! > > > > I have no idea what the significance of this is, but > > df -i gives > > $ df -i > > FilesystemInodes IUsed IFree IUse% Mounted on > > /dev/sda71729920 1729920 0 100% / > > > > So, yeah...inodes, but I'm ignorant of what that means, > > or how to resolve that. > > First it means you're using a filesystem with a small fixed number of > inodes, obviously EXT. > > Second, you have a serious problem here because it is your root > filesystem that has run out of inodes. You need to ask yourself why you > have 1.7M files in your rootfs. That's very dumb. That's what /home > and /data and other places are to be used for. I'm not the dummy that filled up my / Before this, it was barely more than hafl full (well, df -h shows I'm only using 9.6gb of the 16gb there). Also, that hdd is old. I ran fedora core 4 on it.That's how old it is. Then I tried Ubuntu Dapper Duck on it, and some old PCLinuxOS, and eventually, when it was already about 3 years old, installed Lenny on it, my first Debian (and I'm still here!). But I formatted it as ext3 when I installed lenny, and from there just upgraded to squeeze with apt, so haven't changed the fs. Haven't had any reason to change it. So, anyway, after some digging around, I find there are some billions of log files in /var/log/ for popularity-contest. Like, this is 0.005% of the output of sudo find . -xdev -type f | cut -d "/" -f 2 | sort | uniq -c | sort -n 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.2.gz 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.1.2.gz.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.1.2.gz 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.1.2.gz.1.1.1 1 popularity-contest.1.1.2.gz.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.gz.1.2.gz.1.1.2.gz I've aptitude purged popularity-contest, now. I checked the logrotate file, and it has a maxage of 7, meaning these are all a week old or younger, too. Very, very strange. Now I have to figure out how to get rid of them. Even trying to rm -rf a small subset, like *.1.2.gz.1.2.gz.1* gives me Argument list too long. Never seen anything like it... ./taz > > To remedy this you will need to copy files off of the rootfs to another > filesystem, then delete them from your rootfs to free some of these inodes. > > Food for thought: your /dev/sda7 is an EXT filesystem of 26GB with 1.7M > inodes. XFS would give you ~23M inodes on a 26GB filesystem. > > -- > Stan > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/52786b3e.6020...@hardwarefreak.com > -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105041434.gb14...@myownsite.me
Re: No space left on device (28) but device is NOT full!
On 11/4/2013 8:30 PM, Tazman Deville wrote: > On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: >>Hi, >> >>Did you check inodes usage? (df -i) >> >>I could be inodes availability rather than block availability. > > > AHA! > > I have no idea what the significance of this is, but > df -i gives > $ df -i > FilesystemInodes IUsed IFree IUse% Mounted on > /dev/sda71729920 1729920 0 100% / > > So, yeah...inodes, but I'm ignorant of what that means, > or how to resolve that. First it means you're using a filesystem with a small fixed number of inodes, obviously EXT. Second, you have a serious problem here because it is your root filesystem that has run out of inodes. You need to ask yourself why you have 1.7M files in your rootfs. That's very dumb. That's what /home and /data and other places are to be used for. To remedy this you will need to copy files off of the rootfs to another filesystem, then delete them from your rootfs to free some of these inodes. Food for thought: your /dev/sda7 is an EXT filesystem of 26GB with 1.7M inodes. XFS would give you ~23M inodes on a 26GB filesystem. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52786b3e.6020...@hardwarefreak.com
Re: No space left on device (28) but device is NOT full!
Hi, inodes are basically metadata (http://www.linfo.org/inode.html). It looks like you have a lot of files in the root directory (most probably small files), and your system has used all available inodes. You cannot add more inodes without re-creating the file system (mkfs), this is because the inode number is fixed during file system creation. In this case, if the system requires several small files, then the file system should be created using a smaller byte-per-inode ratio. You could use another directory, in a different device/partition for your application data, but if this application requires all those files (let's assume that those files are not temp files), then I really recommend to plan again the installation of this system using another partition, only for this data. Best regards, HC On Mon, Nov 4, 2013 at 9:30 PM, Tazman Deville wrote: > On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: > >Hi, > > > >Did you check inodes usage? (df -i) > > > >I could be inodes availability rather than block availability. > > > AHA! > > I have no idea what the significance of this is, but > df -i gives > $ df -i > FilesystemInodes IUsed IFree IUse% Mounted on > /dev/sda71729920 1729920 0 100% / > > So, yeah...inodes, but I'm ignorant of what that means, > or how to resolve that. > > Taz > > > >Best regards, > > > >HC > > > >On Mon, Nov 4, 2013 at 6:16 PM, Tazman Deville <[1] > tazmande...@gmx.com> > >wrote: > > > > Just since yesterday, I'm seeing this PHP error > > on the scuttle installation on a little server here > > I have. > > Scuttle is installed from the debian repos. > > The server is running Squeeze still (I know.. > > I should upgrade it, but I'll spend a day ironing > > out dovecot and postfix when I do, so haven't gotten > > around to it). > > > > Now, the device is far from full. > > df -h shows: > > Filesystem � � � � � �Size �Used Avail Use% Mounted on > > /dev/sda7 � � � � � � �26G �9.7G � 15G �40% / > > tmpfs � � � � � � � � 949M � � 0 �949M � 0% /lib/init/rw > > udev � � � � � � � � �944M �200K �944M � 1% /dev > > tmpfs � � � � � � � � 949M � � 0 �949M � 0% /dev/shm > > /dev/sda1 � � � � � � 2.8G � 85M �2.6G � 4% /boot > > /dev/sda5 � � � � � � 154G � 52G � 95G �36% /home > > > > Googling (or dukgoing, or ixquicking) > > just shows a lot of stuff about "duh, your disk is full", > > but it isn't. > > Somewhere, I think on LinuxQuestions.org, I'd > > found something about the aptitude package cache, > > yesterday when this happened, so I did > > aptitude autoclean > > and that seemed to resolve the problem. > > Today, however, it is not working. > > > > What could be causing this, and how may I resolve it? > > The machine is a 3.2ghz celeron with 1.5gb ram. > > You can see the storage parameters from df -h, of course. > > > > Any assistance or guidance would be appreciated. > > > > Thanks, > > Taz > > -- > > [2]http://tazmandevil.info > > taz hungry > > > > -- > > To UNSUBSCRIBE, email to [3]debian-user-requ...@lists.debian.org > > with a subject of "unsubscribe". Trouble? Contact > > [4]listmas...@lists.debian.org > > Archive: [5] > http://lists.debian.org/20131104231629.ga28...@myownsite.me > > > > References > > > >Visible links > >1. mailto:tazmande...@gmx.com > >2. http://tazmandevil.info/ > >3. mailto:debian-user-requ...@lists.debian.org > >4. mailto:listmas...@lists.debian.org > >5. http://lists.debian.org/20131104231629.ga28...@myownsite.me > > -- > http://tazmandevil.info > taz hungry > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/20131105023026.gb3...@myownsite.me > >
Re: No space left on device (28) but device is NOT full!
On Mon, Nov 04, 2013 at 06:43:45PM -0500, Hecber Cordova wrote: >Hi, > >Did you check inodes usage? (df -i) > >I could be inodes availability rather than block availability. AHA! I have no idea what the significance of this is, but df -i gives $ df -i FilesystemInodes IUsed IFree IUse% Mounted on /dev/sda71729920 1729920 0 100% / So, yeah...inodes, but I'm ignorant of what that means, or how to resolve that. Taz > >Best regards, > >HC > >On Mon, Nov 4, 2013 at 6:16 PM, Tazman Deville <[1]tazmande...@gmx.com> >wrote: > > Just since yesterday, I'm seeing this PHP error > on the scuttle installation on a little server here > I have. > Scuttle is installed from the debian repos. > The server is running Squeeze still (I know.. > I should upgrade it, but I'll spend a day ironing > out dovecot and postfix when I do, so haven't gotten > around to it). > > Now, the device is far from full. > df -h shows: > Filesystem � � � � � �Size �Used Avail Use% Mounted on > /dev/sda7 � � � � � � �26G �9.7G � 15G �40% / > tmpfs � � � � � � � � 949M � � 0 �949M � 0% /lib/init/rw > udev � � � � � � � � �944M �200K �944M � 1% /dev > tmpfs � � � � � � � � 949M � � 0 �949M � 0% /dev/shm > /dev/sda1 � � � � � � 2.8G � 85M �2.6G � 4% /boot > /dev/sda5 � � � � � � 154G � 52G � 95G �36% /home > > Googling (or dukgoing, or ixquicking) > just shows a lot of stuff about "duh, your disk is full", > but it isn't. > Somewhere, I think on LinuxQuestions.org, I'd > found something about the aptitude package cache, > yesterday when this happened, so I did > aptitude autoclean > and that seemed to resolve the problem. > Today, however, it is not working. > > What could be causing this, and how may I resolve it? > The machine is a 3.2ghz celeron with 1.5gb ram. > You can see the storage parameters from df -h, of course. > > Any assistance or guidance would be appreciated. > > Thanks, > Taz > -- > [2]http://tazmandevil.info > taz hungry > > -- > To UNSUBSCRIBE, email to [3]debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > [4]listmas...@lists.debian.org > Archive: [5]http://lists.debian.org/20131104231629.ga28...@myownsite.me > > References > >Visible links >1. mailto:tazmande...@gmx.com >2. http://tazmandevil.info/ >3. mailto:debian-user-requ...@lists.debian.org >4. mailto:listmas...@lists.debian.org >5. http://lists.debian.org/20131104231629.ga28...@myownsite.me -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105023026.gb3...@myownsite.me
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 05, 2013 at 08:34:37AM +0900, Joel Rees wrote: > On Tue, Nov 5, 2013 at 8:16 AM, Tazman Deville wrote: > > Just since yesterday, I'm seeing this PHP error > > meaning the "No space left on device (28)" you mention in the subject, > I suppose. > > > on the scuttle installation on a little server here > > I have. > > Scuttle is installed from the debian repos. > > The server is running Squeeze still (I know.. > > I should upgrade it, but I'll spend a day ironing > > out dovecot and postfix when I do, so haven't gotten > > around to it). > > > > Now, the device is far from full. > > df -h shows: > > FilesystemSize Used Avail Use% Mounted on > > /dev/sda7 26G 9.7G 15G 40% / > > tmpfs 949M 0 949M 0% /lib/init/rw > > udev 944M 200K 944M 1% /dev > > tmpfs 949M 0 949M 0% /dev/shm > > /dev/sda1 2.8G 85M 2.6G 4% /boot > > /dev/sda5 154G 52G 95G 36% /home > > > > Googling (or dukgoing, or ixquicking) > > just shows a lot of stuff about "duh, your disk is full", > > but it isn't. > > Somewhere, I think on LinuxQuestions.org, I'd > > found something about the aptitude package cache, > > yesterday when this happened, so I did > > aptitude autoclean > > and that seemed to resolve the problem. > > Today, however, it is not working. > > > > The first thing that I check when I get disk full errors but the disks > are not full is the permissions. Sometimes, software just assumes that > any time the system refuses to write it's that the disk is full. > > Then you should check whether you've set quotas up. In Java, there > would be policies to check. And so forth. I haven't made any user quotas. I checked /tmp, and there's almost nothing in there of any consequence (an empty log file). To look deeper, the full error was Warning: session_start(): open(/tmp/sess_9gct9d1b866iek1p3kmo5oe0f2, O_RDWR) failed: No space left on device (28) in /usr/share/scuttle/www/header.inc.php on line 8 line 8 of the file in question is a "session_start();" I looked at /etc/php5/apache2/php.ini to see where php is storing sessions. The relevant line, session.save_path = "/tmp" was commented out, so I do not know where it WAS storing them. I uncommented the line and restarted apache, however, it seems to have made no difference. Now, that scuttle installation has been on this server for about two years without ever having had such an issue. I can't think of anything that would have changed any permissions related to its sessions, or preventing it to write to /tmp, but since /tmp definitely isn't full, I suppose that seems like something to look at. The scuttle runs as user www-data, as far as I understand, which should have permissions to write to /tmp, no? I'm unclear as to what java policies have to do with this, but I know diddley about Java. TazD -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131105022901.ga3...@myownsite.me
Re: No space left on device (28) but device is NOT full!
Hi, Did you check inodes usage? (df -i) I could be inodes availability rather than block availability. Best regards, HC On Mon, Nov 4, 2013 at 6:16 PM, Tazman Deville wrote: > Just since yesterday, I'm seeing this PHP error > on the scuttle installation on a little server here > I have. > Scuttle is installed from the debian repos. > The server is running Squeeze still (I know.. > I should upgrade it, but I'll spend a day ironing > out dovecot and postfix when I do, so haven't gotten > around to it). > > Now, the device is far from full. > df -h shows: > FilesystemSize Used Avail Use% Mounted on > /dev/sda7 26G 9.7G 15G 40% / > tmpfs 949M 0 949M 0% /lib/init/rw > udev 944M 200K 944M 1% /dev > tmpfs 949M 0 949M 0% /dev/shm > /dev/sda1 2.8G 85M 2.6G 4% /boot > /dev/sda5 154G 52G 95G 36% /home > > Googling (or dukgoing, or ixquicking) > just shows a lot of stuff about "duh, your disk is full", > but it isn't. > Somewhere, I think on LinuxQuestions.org, I'd > found something about the aptitude package cache, > yesterday when this happened, so I did > aptitude autoclean > and that seemed to resolve the problem. > Today, however, it is not working. > > What could be causing this, and how may I resolve it? > The machine is a 3.2ghz celeron with 1.5gb ram. > You can see the storage parameters from df -h, of course. > > Any assistance or guidance would be appreciated. > > Thanks, > Taz > -- > http://tazmandevil.info > taz hungry > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/20131104231629.ga28...@myownsite.me > >
Re: No space left on device (28) but device is NOT full!
On Tue, Nov 5, 2013 at 8:16 AM, Tazman Deville wrote: > Just since yesterday, I'm seeing this PHP error meaning the "No space left on device (28)" you mention in the subject, I suppose. > on the scuttle installation on a little server here > I have. > Scuttle is installed from the debian repos. > The server is running Squeeze still (I know.. > I should upgrade it, but I'll spend a day ironing > out dovecot and postfix when I do, so haven't gotten > around to it). > > Now, the device is far from full. > df -h shows: > FilesystemSize Used Avail Use% Mounted on > /dev/sda7 26G 9.7G 15G 40% / > tmpfs 949M 0 949M 0% /lib/init/rw > udev 944M 200K 944M 1% /dev > tmpfs 949M 0 949M 0% /dev/shm > /dev/sda1 2.8G 85M 2.6G 4% /boot > /dev/sda5 154G 52G 95G 36% /home > > Googling (or dukgoing, or ixquicking) > just shows a lot of stuff about "duh, your disk is full", > but it isn't. > Somewhere, I think on LinuxQuestions.org, I'd > found something about the aptitude package cache, > yesterday when this happened, so I did > aptitude autoclean > and that seemed to resolve the problem. > Today, however, it is not working. > > What could be causing this, and how may I resolve it? > The machine is a 3.2ghz celeron with 1.5gb ram. > You can see the storage parameters from df -h, of course. > > Any assistance or guidance would be appreciated. > > Thanks, > Taz > -- > http://tazmandevil.info > taz hungry > The first thing that I check when I get disk full errors but the disks are not full is the permissions. Sometimes, software just assumes that any time the system refuses to write it's that the disk is full. Then you should check whether you've set quotas up. In Java, there would be policies to check. And so forth. -- Joel Rees Be careful where you see conspiracy. Look first in your own heart. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAr43iOvdpMmtgTw1WuObN_sZa++4=n_Nga72mcJQHBq855J=w...@mail.gmail.com
No space left on device (28) but device is NOT full!
Just since yesterday, I'm seeing this PHP error on the scuttle installation on a little server here I have. Scuttle is installed from the debian repos. The server is running Squeeze still (I know.. I should upgrade it, but I'll spend a day ironing out dovecot and postfix when I do, so haven't gotten around to it). Now, the device is far from full. df -h shows: FilesystemSize Used Avail Use% Mounted on /dev/sda7 26G 9.7G 15G 40% / tmpfs 949M 0 949M 0% /lib/init/rw udev 944M 200K 944M 1% /dev tmpfs 949M 0 949M 0% /dev/shm /dev/sda1 2.8G 85M 2.6G 4% /boot /dev/sda5 154G 52G 95G 36% /home Googling (or dukgoing, or ixquicking) just shows a lot of stuff about "duh, your disk is full", but it isn't. Somewhere, I think on LinuxQuestions.org, I'd found something about the aptitude package cache, yesterday when this happened, so I did aptitude autoclean and that seemed to resolve the problem. Today, however, it is not working. What could be causing this, and how may I resolve it? The machine is a 3.2ghz celeron with 1.5gb ram. You can see the storage parameters from df -h, of course. Any assistance or guidance would be appreciated. Thanks, Taz -- http://tazmandevil.info taz hungry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131104231629.ga28...@myownsite.me
Re: /tmp Cannot write: No space left on device
Kai Hendry wrote: frodo$ mount /dev/hda1 on / type ext3 (rw,errors=remount-ro) This is the one you're interested in /dev/hda6 on /home type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) tmpfs on /dev type tmpfs (rw,size=10M,mode=0755) frodo$ df -h FilesystemSize Used Avail Use% Mounted on /dev/hda1 6.5G 6.1G 0 100% / /dev/hda6 21G 12G 7.8G 60% /home tmpfs 252M 0 252M 0% /dev/shm tmpfs 10M 72K 10M 1% /dev frodo$ cat /etc/fstab | grep tmp frodo$ I'm not sure how my /tmp directory works. But I've noticed a couple of times I run out of space on it. Why is my mount reporting it's 10M? That's tiny. I'm sure I didn't purposefully set that whilst installing Debian. Why does df -h give two entries for tmpfs, where both don't seem to be fully used! You don't have a partition specifically for /tmp, so /tmp will be stored on the root partition, /, which df shows is full The two tmpfs filesystems are mounted on /dev and /dev/shm and are unrelated to /tmp HTH -ol -- I will live forever, or die trying. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /tmp Cannot write: No space left on device
On Thu, Oct 27, 2005 at 10:08:38AM +1000, Kai Hendry wrote: > I'm not sure how my /tmp directory works. But I've noticed a couple of times I > run out of space on it. If temp isn't on its own partition, it's just mounted under '/' which is full. I'd start by checking /var/log and /tmp and removing extraneous logs and cruft. Also, apt-get clean will help if you've never done it. -- asg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /tmp Cannot write: No space left on device
Björn Lindström wrote: >Kai Hendry <[EMAIL PROTECTED]> writes: > > > >>FilesystemSize Used Avail Use% Mounted on >>/dev/hda1 6.5G 6.1G 0 100% / >>/dev/hda6 21G 12G 7.8G 60% /home >>tmpfs 252M 0 252M 0% /dev/shm >>tmpfs 10M 72K 10M 1% /dev >> >>I'm not sure how my /tmp directory works. But I've noticed a couple >>of times I run out of space on it. >> >> > >/tmp is just a directory on your root partition. 6.1 GB on your root >partition seems like a lot to me. Maybe you can clean something out. > > > "du -h /tmp" should give you an idea of how much space /tmp is taking. If it's significant, you can manually clean it out (you might want to switch to single-user mode first) or reboot, which will clean it out automagically. This is one of the reasons I use more than one partition; I tend to have separate partitions for /, /tmp, /usr, /usr/local, /var, and /home. In your case, I'd consider moving the /var or /usr or /usr/local to your /home partition, and then symlinking it back to the original location. Say, for example, your /var directory typically runs around 800MB in size; you could move it, which would free 800MB off the / partition: mv /var /home ln -s /home/var /var -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /tmp Cannot write: No space left on device
Kai Hendry <[EMAIL PROTECTED]> writes: > FilesystemSize Used Avail Use% Mounted on > /dev/hda1 6.5G 6.1G 0 100% / > /dev/hda6 21G 12G 7.8G 60% /home > tmpfs 252M 0 252M 0% /dev/shm > tmpfs 10M 72K 10M 1% /dev > > I'm not sure how my /tmp directory works. But I've noticed a couple > of times I run out of space on it. /tmp is just a directory on your root partition. 6.1 GB on your root partition seems like a lot to me. Maybe you can clean something out. > Why is my mount reporting it's 10M? That's tiny. I'm sure I didn't > purposefully set that whilst installing Debian. > > Why does df -h give two entries for tmpfs, where both don't seem to be fully > used! Those are tmpfs filesystems, but they have nothing to do with /tmp (as you can see under "Mounted on"). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
/tmp Cannot write: No space left on device
tar: oracle/instantclient-sqlplus-linux32-10.2.0.1-20050713.zip: Cannot write: No space left on device tar: Skipping to next header tar: Error exit delayed from previous errors frodo$ mount /dev/hda1 on / type ext3 (rw,errors=remount-ro) /dev/hda6 on /home type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) tmpfs on /dev type tmpfs (rw,size=10M,mode=0755) frodo$ df -h FilesystemSize Used Avail Use% Mounted on /dev/hda1 6.5G 6.1G 0 100% / /dev/hda6 21G 12G 7.8G 60% /home tmpfs 252M 0 252M 0% /dev/shm tmpfs 10M 72K 10M 1% /dev frodo$ cat /etc/fstab | grep tmp frodo$ I'm not sure how my /tmp directory works. But I've noticed a couple of times I run out of space on it. Why is my mount reporting it's 10M? That's tiny. I'm sure I didn't purposefully set that whilst installing Debian. Why does df -h give two entries for tmpfs, where both don't seem to be fully used! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CUPS No Space left on device
CUPS stops with showing an error "No space left on device". The printer is on /dev/lp0, parallel port, and the kernel version is 2.6.5. This message is shown when the printer runs out of paper and it is impossible to continue to print the file. The kernel and bios enables EPP+ECP mode, by-directional. Another printer on USB port does not occur the problem and kernel 2.4.x has never got the problem. Could anyone advise me ? Tomoo -- ** Nomura Technical Management Office Ltd. * Tomoo Nomura [EMAIL PROTECTED] http://www.tmo.co.jp/ Phone: +81-78-797-0240 Fax: +81-78-797-0241 @nifty:GBH12257 Worldwide Airline Timetable 'Flight Planner' European Electronic Timetable 'HAFAS' ValueFax Support -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No space left on device - Solved!
Hi again! I finally fixed the problem by creating two new partitions, one for /home (~26.5 Gb) and one for /var (~512 Mb). Here are the steps I followed (suggested by David Bree): 0. Reboot the computer using parted boot floppy. 1. Invoke parted and resize hda5 by shrinking it down to 10 Gbs: (parted) resize 5 15868.925 26367.424 2. Make two new partitions: (parted) mkpartfs logical ext2 26367.424 53503.424 (parted) mkpartfs logical ext2 53503.424 54015.456 Note: the new partitions are called hda7 and hda8. You can always hit 'p' and check that in parted. 3. Reboot the computer normally and copy /home and /var into hda7 and hda8 respectively. Change to root and: # mount -t ext2 /dev/hda7 /mnt # cd /home # tar cf - . | tar --same-owner -C /mnt -xf - # diff -r /home /mnt # umount /mnt # mount -t ext2 /dev/hda8 /mnt # cd /var # tar cf - . | tar --same-owner -C /mnt -xf - # diff -r /var /mnt # umount /mnt # rm -rf /home # mkdir /home # rm -rf /var # mkdir /var 4. Edit /etc/fstab, add the 2 new lines: "/dev/hda7 /home ext2defaults0 2" "/dev/hda8 /varext2defaults0 2" 5. All done (almost)! Reboot normally. Problems: When I rebooted after step 5, the Xserver would not start. The error on the screen said "gdm already running. Aborting!" Morever, I could not bring up Xserver by typing 'startx' because of "xauth: timeout in locking authority file /home/user/.Xauthority". So here's what I had to do: # chown /home/ (for all users on the system) # rm /var/log/gdm.pid This finally allowed me to start gdm as root but kde would complain: "Could not read netowrk connection list. ... Please check that dcopserver program is running". Here's what I did: # rm ~/.DCOP* Now kde runs fine, and I'm really done! See for yourself: # df -h FilesystemSize Used Avail Use% Mounted on /dev/hda3 463M 101M 338M 23% / /dev/hda5 10G 2.8G 6.7G 30% /usr /dev/hda7 26G 257M 24G 2% /home /dev/hda8 478M 68M 385M 15% /var Thank you everyone for your useful suggestions! ... salman On Sun, 20 Jul 2003, David wrote: > On Sat, Jul 19, 2003 at 09:10:14PM -0400, Salman Haq wrote: > > > > > > #df -h > > > > FilesystemSize Used Avail Use% Mounted on > > > > /dev/hda3 463M 440M 1.0k 100% / > > > > /dev/hda5 37G 2.5G 32G 8% /usr > > > > > > > > # df -ih > > > > FilesystemInodes IUsed IFree IUse% Mounted on > > > > /dev/hda3 120k 20k100k 17% / > > > > /dev/hda5 4.7M149k4.5M4% /usr > > > > > > > > Now, I realize that this a very bad partition scheme but I'm just a > > > > newbie. When I was installing debian a few months ago, I didn't intend to > > > > have this scheme. I wanted root to be mounted as '/' and everything else > > > > under '/usr' since thats the bigger partition. Unfortunately, most of > > > > everything is mounted under '/'. I wonder where I went wrong... > > > > > > > > Can I change this situation, without re-formatting/re-partitioning? Or, > > > > atleast for now, which files can I safely delete to free-up some space? > > > Thanks everybody for your helpful responses. To make some temporary room > > I cleaned up some logs and unnecessary directories in a few of the home > > directories of some of the users. > > > > Then I resolved to fix the problem once and for all by using parted to > > resize the partitions. When I finally got around to doing it this past > > weekend, things didn't go as smoothly as I thought they would. > > > > This is the information that parted shows about my partitions: > > > > Disk geometry for /dev/hda: 0.000-57220.458 megabytes > > Disk lable type: msdos > > Minor Start End TypeFilesystem Flags > > 1 0.031 31.376 primary fat 16 > > 2 31.37715390.395 primary ntfsboot > > 3 15390.39615868.894 primary ext2 > > 4 15868.89454493.923 extended > > 5 15868.92554015.424 logical ext2 > > 6 54015.45654390.396 logical linux-swap > > > > Since my original problem requires me to shrink hda5 down to ~10 gigs and > > expand hda3 to ~30 gigs I set about to do the following: > > > > (parted) resize 5 40869.024 54015.424 > > > > and saw this: > > > > attempt to access ... of device > > 03:00: rw-=0, ... limit=58593750 <-(same error msg as before) > > Warning: You requested to resize the partition to 40869.024-54015.424Mb. > > The closest Parted can manage is 15868.925-54015.424. > > > > So parted doesn't want to resize the partition that way. > > I believe that Florian Ernst answered this problem... > > > Then I quit > > parted and restarted it as "parted /dev/hda5" and typed: > > > > (parted) resize 1 0.000 13146.4 > > > > That actually resized something...
Re: No space left on device
On Sat, Jul 19, 2003 at 09:10:14PM -0400, Salman Haq wrote: > > > > #df -h > > > FilesystemSize Used Avail Use% Mounted on > > > /dev/hda3 463M 440M 1.0k 100% / > > > /dev/hda5 37G 2.5G 32G 8% /usr > > > > > > # df -ih > > > FilesystemInodes IUsed IFree IUse% Mounted on > > > /dev/hda3 120k 20k100k 17% / > > > /dev/hda5 4.7M149k4.5M4% /usr > > > > > > Now, I realize that this a very bad partition scheme but I'm just a > > > newbie. When I was installing debian a few months ago, I didn't intend to > > > have this scheme. I wanted root to be mounted as '/' and everything else > > > under '/usr' since thats the bigger partition. Unfortunately, most of > > > everything is mounted under '/'. I wonder where I went wrong... > > > > > > Can I change this situation, without re-formatting/re-partitioning? Or, > > > atleast for now, which files can I safely delete to free-up some space? > Thanks everybody for your helpful responses. To make some temporary room > I cleaned up some logs and unnecessary directories in a few of the home > directories of some of the users. > > Then I resolved to fix the problem once and for all by using parted to > resize the partitions. When I finally got around to doing it this past > weekend, things didn't go as smoothly as I thought they would. > > This is the information that parted shows about my partitions: > > Disk geometry for /dev/hda: 0.000-57220.458 megabytes > Disk lable type: msdos > Minor Start End TypeFilesystem Flags > 1 0.031 31.376 primary fat 16 > 2 31.377 15390.395 primary ntfsboot > 3 15390.39615868.894 primary ext2 > 4 15868.89454493.923 extended > 5 15868.92554015.424 logical ext2 > 6 54015.45654390.396 logical linux-swap > > Since my original problem requires me to shrink hda5 down to ~10 gigs and > expand hda3 to ~30 gigs I set about to do the following: > > (parted) resize 5 40869.024 54015.424 > > and saw this: > > attempt to access ... of device > 03:00: rw-=0, ... limit=58593750 <-(same error msg as before) > Warning: You requested to resize the partition to 40869.024-54015.424Mb. > The closest Parted can manage is 15868.925-54015.424. > > So parted doesn't want to resize the partition that way. I believe that Florian Ernst answered this problem... > Then I quit > parted and restarted it as "parted /dev/hda5" and typed: > > (parted) resize 1 0.000 13146.4 > > That actually resized something... when I restarted my computer normally, > /dev/hda5 mounted to /usr and "df" showed its size as 12 gigs (as opposed > to the old 37 gigs). However, parted continues to show the original > numbers. Morever, I still haven't solved my original problem, which is > expanding /dev/hda3. When I try: > > (parted) resize 3 15390.393 4.000 > it says "The closest parted can manage is 15390.393 15868.894" > > I also tried "parted /dev/hda4" but that just says "can't partition > outside of disk" even if I simply try to print info. > > What do I have to do to get rid of that disk access error and > shrink hda5 (or hda4,5,6) and expand hda3? > > In the meanwhile, I have 'resized' hda5 back to its original size > so that 'df' show its size as 37 gigs. I hope this makes sense. There are a couple of ways to go about this.. 1) Keep everything you currently have on "/" and expand it. 2) Create additional partitions and move some directories out of "/" In either case, the first thing you are going to have to do is shrink hda5.. Someone suggested that you'd never need more than 5-10G on /usr, so.. assuming you want 10 G, after issuing the command "parted /dev/hda" 1) if you want to keep only the two partitions and not add more.. (parted) resize 5 15868.925 44015 ( leaving about a 10-G space above hda5 (parted) mkpartfs ext2 54390.396 - see below.. (parted) del( should still be hda5) I'm not sure now what hda4 will look like - I've never tried this.. if it's now moved to the begin of the new hda5, you are sitting fine.. just resize hda3 up to the bottom of hda5... 2) -- probably easier.. create new partition(s) and move director(ies) out of "/".. "/home" should give you a bunch of space.. also /etc takes up quite a bit.. "du -ch" of the /home and /etc dirs should give you an idea of what you might need.. (parted) resize 5 15868.925 25868.925 (adjust to taste).. then create new partition(s) in the new free space and copy the director(ies) into the new partition(s) (see below).. delete (or empty) these directories from within hda3 - if you delete them, you need to make new empty dirs in hda3 for mounting purposes.. Then edit /etc/fstab to the new setup and remount.. Note on copying dirs: parted has a copy facility for copying one partition to another, but I'm not sure if it works on differently-sized partitions.. the simplest way is
Re: No space left on device
Hello Salman! At Sunday 20 July 2003 03:20 Salman Haq wrote: > Thanks everybody for your helpful responses. To make some temporary > room > I cleaned up some logs and unnecessary directories in a few of the > home directories of some of the users. > > Then I resolved to fix the problem once and for all by using parted > to > resize the partitions. When I finally got around to doing it this > past weekend, things didn't go as smoothly as I thought they would. > > When I boot the system using the parted boot disk and started > parted I > saw the following warning message: > > Using /dev/hda > attempt to access beyond end of device > 03:00: rw=0, want=58593752, limit=58593750 > Information: The operating system thinks the geometry on /dev/hda is > 7294/255/63. Therefore, cylinder 1024 ends at 8032.499M > > This is the information that parted shows about my partitions: > > Disk geometry for /dev/hda: 0.000-57220.458 megabytes > Disk lable type: msdos > Minor Start End TypeFilesystem Flags > 1 0.031 31.376 primary fat 16 > 2 31.377 15390.395 primary ntfsboot > 3 15390.39615868.894 primary ext2 > 4 15868.89454493.923 extended > 5 15868.92554015.424 logical ext2 > 6 54015.45654390.396 logical linux-swap > > Since my original problem requires me to shrink hda5 down to ~10 > gigs and expand hda3 to ~30 gigs I set about to do the following: > > (parted) resize 5 40869.024 54015.424 > > and saw this: > > attempt to access ... of device > 03:00: rw-=0, ... limit=58593750 <-(same error msg as before) > Warning: You requested to resize the partition to > 40869.024-54015.424Mb. The closest Parted can manage is > 15868.925-54015.424. Ok/Cancel? c A short quote from the GNU parted manual[1]: /--- | (parted) resize partition_number new start new end | | new start must be the same as the old start for ext2 partitions | (unfortunately) \--- So shrinking the partition this way is not possible using parted. > So parted doesn't want to resize the partition that way. Then I quit > parted and restarted it as "parted /dev/hda5" and typed: > > (parted) resize 1 0.000 13146.4 > > That actually resized something... when I restarted my computer > normally, > /dev/hda5 mounted to /usr and "df" showed its size as 12 gigs (as > opposed to the old 37 gigs). However, parted continues to show the > original numbers. Morever, I still haven't solved my original > problem, which is expanding /dev/hda3. When I try: > > (parted) resize 3 15390.393 4.000 > it says "The closest parted can manage is 15390.393 15868.894" The partition has to be in one contigeous block, that's why your attempt didn't work out. > I also tried "parted /dev/hda4" but that just says "can't partition > outside of disk" even if I simply try to print info. > > What do I have to do to get rid of that disk access error and > shrink hda5 (or hda4,5,6) and expand hda3? > > In the meanwhile, I have 'resized' hda5 back to its original size > so that 'df' show its size as 37 gigs. I hope this makes sense. There is an example repartitioning scheme in the GNU parted manual[1]. It doesn't completely apply to you, but it might be of some help; I guess you can work out the needed additions. Referring to your type of problem they say: /--- | So this process is going to be rather complicated. It is possible, | though. \--- Don't give up... ;) HTH, Flo [1] http://www.gnu.org/manual/parted-1.6.1/html_chapter/parted_2.html#SEC31 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No space left on device
On Mon, 14 Jul 2003, Bijan Soleymani wrote: > On Mon, Jul 14, 2003 at 12:51:55PM -0400, Salman Haq wrote: > > > > Hi, > > > > When trying to compile some code, I got the following error: > > > > cpp0: /tmp/ccFJJwQN.ii: No space left on device > > > > I then realized that /tmp is mounted on my root partition, which was > > full: > > > > #df -h > > FilesystemSize Used Avail Use% Mounted on > > /dev/hda3 463M 440M 1.0k 100% / > > /dev/hda5 37G 2.5G 32G 8% /usr > > > > # df -ih > > FilesystemInodes IUsed IFree IUse% Mounted on > > /dev/hda3 120k 20k100k 17% / > > /dev/hda5 4.7M149k4.5M4% /usr > > > > Now, I realize that this a very bad partition scheme but I'm just a > > newbie. When I was installing debian a few months ago, I didn't intend to > > have this scheme. I wanted root to be mounted as '/' and everything else > > under '/usr' since thats the bigger partition. Unfortunately, most of > > everything is mounted under '/'. I wonder where I went wrong... > > > > Can I change this situation, without re-formatting/re-partitioning? Or, > > atleast for now, which files can I safely delete to free-up some space? > > I recommend you use one huge / partition. This way you won't run into > this type of problem. You can delete logs in /var/log to get some free > space, then I suggest you install parted which will allow you to change > the size of your partitions. I suggest you shrink your /usr partition > down to 5-10 gigs (I doubt you will install more software than this) and > increase / to use up the extra space. > > The /usr partition is usually used to install software. The / partition > holds everything that doesn't have its own partition, like /home, /var, > /etc, etc. > > Bijan Thanks everybody for your helpful responses. To make some temporary room I cleaned up some logs and unnecessary directories in a few of the home directories of some of the users. Then I resolved to fix the problem once and for all by using parted to resize the partitions. When I finally got around to doing it this past weekend, things didn't go as smoothly as I thought they would. When I boot the system using the parted boot disk and started parted I saw the following warning message: Using /dev/hda attempt to access beyond end of device 03:00: rw=0, want=58593752, limit=58593750 Information: The operating system thinks the geometry on /dev/hda is 7294/255/63. Therefore, cylinder 1024 ends at 8032.499M This is the information that parted shows about my partitions: Disk geometry for /dev/hda: 0.000-57220.458 megabytes Disk lable type: msdos Minor Start End TypeFilesystem Flags 1 0.031 31.376 primary fat 16 2 31.37715390.395 primary ntfsboot 3 15390.39615868.894 primary ext2 4 15868.89454493.923 extended 5 15868.92554015.424 logical ext2 6 54015.45654390.396 logical linux-swap Since my original problem requires me to shrink hda5 down to ~10 gigs and expand hda3 to ~30 gigs I set about to do the following: (parted) resize 5 40869.024 54015.424 and saw this: attempt to access ... of device 03:00: rw-=0, ... limit=58593750 <-(same error msg as before) Warning: You requested to resize the partition to 40869.024-54015.424Mb. The closest Parted can manage is 15868.925-54015.424. Ok/Cancel? c So parted doesn't want to resize the partition that way. Then I quit parted and restarted it as "parted /dev/hda5" and typed: (parted) resize 1 0.000 13146.4 That actually resized something... when I restarted my computer normally, /dev/hda5 mounted to /usr and "df" showed its size as 12 gigs (as opposed to the old 37 gigs). However, parted continues to show the original numbers. Morever, I still haven't solved my original problem, which is expanding /dev/hda3. When I try: (parted) resize 3 15390.393 4.000 it says "The closest parted can manage is 15390.393 15868.894" I also tried "parted /dev/hda4" but that just says "can't partition outside of disk" even if I simply try to print info. What do I have to do to get rid of that disk access error and shrink hda5 (or hda4,5,6) and expand hda3? In the meanwhile, I have 'resized' hda5 back to its original size so that 'df' show its size as 37 gigs. I hope this makes sense. thanks ... salman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No space left on device
* Salman Haq <[EMAIL PROTECTED]> [14-07-2003 18:56]: > Now, I realize that this a very bad partition scheme but I'm just a > newbie. When I was installing debian a few months ago, I didn't intend to > have this scheme. I wanted root to be mounted as '/' and everything else > under '/usr' since thats the bigger partition. Unfortunately, most of > everything is mounted under '/'. I wonder where I went wrong... Either I misread what you are saying or your understanding of filesystems and mount points is wrong. You can't mount _everything else_ under /usr. You could mount another filesystem on say /usr/local but i.e. /tmp is either on the / filesystem or has its own filesystem that is mounted on /tmp, but it's never on the filesystem that is mounted on /usr (not directly annyway, you could use symlinks). I hope this makes sense. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No space left on device
>>>>> "BS" == Bijan Soleymani <[EMAIL PROTECTED]> writes:
BS> On Mon, Jul 14, 2003 at 12:51:55PM -0400, Salman Haq wrote:
>> Hi,
>>
>> When trying to compile some code, I got the following error:
>>
>> cpp0: /tmp/ccFJJwQN.ii: No space left on device
>>
>> I then realized that /tmp is mounted on my root partition,
>> which was full:
>>
>> #df -h Filesystem Size Used Avail Use% Mounted on /dev/hda3
>> 463M 440M 1.0k 100% / /dev/hda5 37G 2.5G 32G 8% /usr
>>
>> # df -ih Filesystem Inodes IUsed IFree IUse% Mounted on
>> /dev/hda3 120k 20k 100k 17% / /dev/hda5 4.7M 149k 4.5M 4% /usr
>>
>> Now, I realize that this a very bad partition scheme but I'm
>> just a newbie. When I was installing debian a few months ago, I
>> didn't intend to have this scheme. I wanted root to be mounted
>> as '/' and everything else under '/usr' since thats the bigger
>> partition. Unfortunately, most of everything is mounted under
>> '/'. I wonder where I went wrong...
>>
>> Can I change this situation, without
>> re-formatting/re-partitioning? Or, atleast for now, which files
>> can I safely delete to free-up some space?
You can run "apt-get clean" to delete the apt cache.
You could probably move some things around, too -- move /home to
/usr/home, and symlink it to /home.
Finally, you could use GNU parted to rearrange the partitions.
--Joe
--
Joseph Barillari -- http://barillari.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No space left on device
Hello Salman Haq wrote: > When trying to compile some code, I got the following error: > > cpp0: /tmp/ccFJJwQN.ii: No space left on device > > I then realized that /tmp is mounted on my root partition, which was > full: > > #df -h > FilesystemSize Used Avail Use% Mounted on > /dev/hda3 463M 440M 1.0k 100% / > /dev/hda5 37G 2.5G 32G 8% /usr > > # df -ih > FilesystemInodes IUsed IFree IUse% Mounted on > /dev/hda3 120k 20k100k 17% / > /dev/hda5 4.7M149k4.5M4% /usr > > Now, I realize that this a very bad partition scheme but I'm just a > newbie. When I was installing debian a few months ago, I didn't intend > to have this scheme. I wanted root to be mounted as '/' and everything > else under '/usr' since thats the bigger partition. Unfortunately, most > of everything is mounted under '/'. I wonder where I went wrong... A good place to look for files to delete is probably /var/cache/apt/archives where apt saves downloaded packages. If you installed a lot of security updates all these packages will be in that directory. You can safeley delete them from hard disk (although saving them on cdrom or moving them somewhere else might be a good idea so you don't have to download them again in case you want to reinstall). If you have plenty of RAM, you can also use tmpfs to mount the tmp directory in your RAM. You could maybe also try to reduce the size of your /dev/hda5 partition, make a new partition behind /dev/hda5 and mount that as /var. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
