Re: Disk too full?
On 2016-04-05 22:07 -0400, Stefan Monnier wrote: >>> Filesystem Size Used Avail Use% Mounted on >>> rootfs 323M 189M 117M 62% / >> This is the problem. The root filesystem is too small, so you will not >> be able to install or upgrade a Debian kernel. This is a bug[1] in the >> automatic partitioner that only got fixed in Jessie. >> There's no easy way out here, my choice would probably be to make a >> backup and repartition the disk. > > Can't he just create a suitably sized /boot partition to relieve the / > partition of badly needed space for the /lib/modules subdirectory? This might free just enough space for the time being, but in the long run it is not going to suffice because of the ever growing size of the kernel. A possible long term solution is to move the kernel modules to /usr/lib/modules and make /lib/modules a symlink to /usr/lib/modules. This requires that /usr is mounted by the initramfs. Cheers, Sven
Re: Disk too full?
On Tue, 5 Apr 2016 06:36:39 -0500 Charles Blairwrote: >I think I'm running out of space on my > laptop. The last time I got an "updates > available" message, I got a further warning, > during the update, that I was low on space. > The update did seem to complete, though. > >However, when I tried to use the calculator > program dc afterwards, the computer just sat > there. > >Below is the output from the df command. Try running df -i. The output of df can be somewhat misleading; you can have plenty of disk space free, but not enough inodes. pgpQjPNgm1lIx.pgp Description: OpenPGP digital signature
Re: Disk too full?
On Wed, 6 Apr 2016 at 09:56, arianwrote: > > > The Debian Wiki, circa 2009 when I last built a Debian system from > scratch, used to advise this kind of setup for performance and backup > convenience. I have almost the same partition structure (although my disks, > note disks plural) are a lot bigger so I don't have space problems. > > and then SSDs happened :) > How would this give you backup convenience? > > First apologies for not clipping above -- Google inbox client on an iPhone seems to be trying to manoeuvre me into top-posting, and won't let me edit the quoted text... I didn't see where the OP mentioned he is using SSDs, apologies if I missed something there. If HDDs, the advice would still be relevant. As to backup convenience, some backup techniques eg the dump command, work with disk device names and as such things can be better controlled with finer grained partition structure (although perhaps lvm offers a better solution nowadays, I am not sure) Mark
Re: Disk too full?
>> Filesystem Size Used Avail Use% Mounted on >> rootfs 323M 189M 117M 62% / > This is the problem. The root filesystem is too small, so you will not > be able to install or upgrade a Debian kernel. This is a bug[1] in the > automatic partitioner that only got fixed in Jessie. > There's no easy way out here, my choice would probably be to make a > backup and repartition the disk. Can't he just create a suitably sized /boot partition to relieve the / partition of badly needed space for the /lib/modules subdirectory? Stefan
Re: Disk too full?
> The Debian Wiki, circa 2009 when I last built a Debian system from scratch, > used to advise this kind of setup for performance and backup convenience. I > have almost the same partition structure (although my disks, note disks > plural) are a lot bigger so I don't have space problems. and then SSDs happened :) How would this give you backup convenience? signature.asc Description: OpenPGP digital signature
Re: Disk too full?
On Wed, 6 Apr 2016 at 07:11, arianwrote: > Hi Charles, > > why is your system spread across this many partitions? Having / + /home ( > and where appropriate /boot or /boot/efi ) is far less cumbersome as you > only need to maintain 2-3 partitions, for instance a reasonable amount of > free space on them. On btrfs, zfs you can even go to 1-2 partitions, as you > put /home on a subvolume. > > If you don't have requirements for this kind of setup, I side with Sven: > repartition. > > regards, Arian > > The Debian Wiki, circa 2009 when I last built a Debian system from scratch, used to advise this kind of setup for performance and backup convenience. I have almost the same partition structure (although my disks, note disks plural) are a lot bigger so I don't have space problems. I did originally have a root partition that was too small, thanks to the same bad advice in the wiki, and had to repartition some years ago to fix it. Mark
Re: Disk too full?
On Tue 05 Apr 2016 at 22:46:10 (+0100), Lisi Reisz wrote: > On Tuesday 05 April 2016 19:13:23 David Wright wrote: > > On Tue 05 Apr 2016 at 16:46:36 (+0100), Lisi Reisz wrote: > > > May the OP have run out of inodes in / ? > > > > Here's my prediction :) > > > > 1010% / > > 120 1% /home > > 10 1% /tmp > > 6050% /usr > > 2010% /var > > > > Cheers, > > David. > > On Tuesday 05 April 2016 21:29:00 Charles Blair wrote: > >Output from df -ih > > > > Filesystem Inodes IUsed IFree IUse% Mounted on > > rootfs 84K 7.6K 76K 10% / > > udev 488K 462 488K1% /dev > > tmpfs 490K 459 489K1% /run > > /dev/disk/by-uuid/09...8e 84K 7.6K 76K 10% / > > tmpfs 490K 1 490K1% /run/lock > > tmpfs 490K 8 490K1% /run/shm > > /dev/sda10 11M 9.0K 11M1% /home > > /dev/sda9 96K42 96K1% /tmp > > /dev/sda6 537K 245K 293K 46% /usr > > /dev/sda7 179K 11K 169K6% /var > > > All right. Don't smirk. ;-) If I were good at Ascii art you would get a > star, albeit not a gold one. :-) I cheated; I remembered that he posted them last year. I think it's possible that you, Charles, are still running wheezy, which is probably why you're getting away with such a small root partition. If booting into single user mode allows you to umount /usr, then it would be possible to migrate your root to /dev/sda6, but you don't give me the impression that you'd be confident enough to do that. If you're running a 3.2 kernel, just don't try to upgrade to 3.16; the .deb file is 50% bigger. I don't know what you've got in the partitions we don't see, but judging by your use of /home, you've got room to repartition with two at-least-32GB root partitions so that you can in future install/ upgrade a new Debian in one without touching the old one in the other. Cheers, David.
Re: Disk too full?
Hi Charles, why is your system spread across this many partitions? Having / + /home ( and where appropriate /boot or /boot/efi ) is far less cumbersome as you only need to maintain 2-3 partitions, for instance a reasonable amount of free space on them. On btrfs, zfs you can even go to 1-2 partitions, as you put /home on a subvolume. If you don't have requirements for this kind of setup, I side with Sven: repartition. regards, Arian signature.asc Description: OpenPGP digital signature
Re: Disk too full?
On Tuesday 05 April 2016 19:13:23 David Wright wrote: > On Tue 05 Apr 2016 at 16:46:36 (+0100), Lisi Reisz wrote: > > May the OP have run out of inodes in / ? > > Here's my prediction :) > > 1010% / > 120 1% /home > 10 1% /tmp > 6050% /usr > 2010% /var > > Cheers, > David. On Tuesday 05 April 2016 21:29:00 Charles Blair wrote: >Output from df -ih > > Filesystem Inodes IUsed IFree IUse% Mounted on > rootfs 84K 7.6K 76K 10% / > udev 488K 462 488K1% /dev > tmpfs 490K 459 489K1% /run > /dev/disk/by-uuid/09...8e 84K 7.6K 76K 10% / > tmpfs 490K 1 490K1% /run/lock > tmpfs 490K 8 490K1% /run/shm > /dev/sda10 11M 9.0K 11M1% /home > /dev/sda9 96K42 96K1% /tmp > /dev/sda6 537K 245K 293K 46% /usr > /dev/sda7 179K 11K 169K6% /var All right. Don't smirk. ;-) If I were good at Ascii art you would get a star, albeit not a gold one. :-) Lisi
Re: Disk too full?
On Tue, 5 Apr 2016 15:29:00 -0500 Charles Blairwrote: >Many thanks for all the assistance! > >My apologies for hitting the panic button over > dc waiting for me to type in some numbers, which is, > of course, what it is supposed to do. > >There were several other questions from my > would-be helpers, but for now: > >Output from df -h > > Filesystem Size Used Avail Use% Mounted on > rootfs 323M 189M 117M 62% / > udev 10M 0 10M 0% /dev > tmpfs392M 704K 391M 1% /run > /dev/disk/by-uuid/09...8e323M 189M 117M 62% / > tmpfs5.0M 0 5.0M 0% /run/lock > tmpfs2.4G 152K 2.4G 1% /run/shm > /dev/sda10 169G 1.9G 159G 2% /home > /dev/sda9368M 11M 339M 3% /tmp > /dev/sda68.3G 5.8G 2.1G 74% /usr > /dev/sda72.8G 1.8G 859M 68% /var > >Output from df -ih > > Filesystem Inodes IUsed IFree IUse% Mounted on > rootfs 84K 7.6K 76K 10% / > udev 488K 462 488K1% /dev > tmpfs 490K 459 489K1% /run > /dev/disk/by-uuid/09...8e 84K 7.6K 76K 10% / > tmpfs 490K 1 490K1% /run/lock > tmpfs 490K 8 490K1% /run/shm > /dev/sda10 11M 9.0K 11M1% /home > /dev/sda9 96K42 96K1% /tmp > /dev/sda6 537K 245K 293K 46% /usr > /dev/sda7 179K 11K 169K6% /var > Sorry, I hadn't been paying enough attention. If you are awaiting a kernel upgrade, you don't have enough space in /. My current two kernel modules directories are each around 175MB, with /lib totalling 445MB. You can't run /lib anywhere but inside /, so I don't think you have too much choice but to plan for a bigger /. Until quite recently, 'a few hundred megs' was enough for /, now it isn't. Not only have the kernel modules mushroomed, but we are now strongly advised to merge /usr into /. The boot process is getting cleverer, and starting to want /usr stuff mounted during boot. There are ways to arrange to mount a separate /usr, but that's another thing to go wrong/get forgotten, it's easier to merge it in. -- Joe
Re: Disk too full?
On 2016-04-05 15:29 -0500, Charles Blair wrote: >Many thanks for all the assistance! > >My apologies for hitting the panic button over > dc waiting for me to type in some numbers, which is, > of course, what it is supposed to do. > >There were several other questions from my > would-be helpers, but for now: > >Output from df -h > > Filesystem Size Used Avail Use% Mounted on > rootfs 323M 189M 117M 62% / This is the problem. The root filesystem is too small, so you will not be able to install or upgrade a Debian kernel. This is a bug[1] in the automatic partitioner that only got fixed in Jessie. There's no easy way out here, my choice would probably be to make a backup and repartition the disk. Cheers, Sven 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693107
Re: Re: Disk too full?
Many thanks for all the assistance! My apologies for hitting the panic button over dc waiting for me to type in some numbers, which is, of course, what it is supposed to do. There were several other questions from my would-be helpers, but for now: Output from df -h Filesystem Size Used Avail Use% Mounted on rootfs 323M 189M 117M 62% / udev 10M 0 10M 0% /dev tmpfs392M 704K 391M 1% /run /dev/disk/by-uuid/09...8e323M 189M 117M 62% / tmpfs5.0M 0 5.0M 0% /run/lock tmpfs2.4G 152K 2.4G 1% /run/shm /dev/sda10 169G 1.9G 159G 2% /home /dev/sda9368M 11M 339M 3% /tmp /dev/sda68.3G 5.8G 2.1G 74% /usr /dev/sda72.8G 1.8G 859M 68% /var Output from df -ih Filesystem Inodes IUsed IFree IUse% Mounted on rootfs 84K 7.6K 76K 10% / udev 488K 462 488K1% /dev tmpfs 490K 459 489K1% /run /dev/disk/by-uuid/09...8e 84K 7.6K 76K 10% / tmpfs 490K 1 490K1% /run/lock tmpfs 490K 8 490K1% /run/shm /dev/sda10 11M 9.0K 11M1% /home /dev/sda9 96K42 96K1% /tmp /dev/sda6 537K 245K 293K 46% /usr /dev/sda7 179K 11K 169K6% /var
Re: Disk too full?
On Tue 05 Apr 2016 at 16:46:36 (+0100), Lisi Reisz wrote: > May the OP have run out of inodes in / ? Here's my prediction :) 1010% / 120 1% /home 10 1% /tmp 6050% /usr 2010% /var Cheers, David.
Re: Disk too full?
On Tue 05 Apr 2016 at 18:00:30 (+0100), Lisi Reisz wrote: > On Tuesday 05 April 2016 17:46:24 David Wright wrote: > > On Tue 05 Apr 2016 at 16:46:36 (+0100), Lisi Reisz wrote: > > > On Tuesday 05 April 2016 15:34:37 David Wright wrote: > > > > On Tue 05 Apr 2016 at 06:36:39 (-0500), Charles Blair wrote: > > > > >I think I'm running out of space on my > > > > > laptop. The last time I got an "updates > > > > > available" message, I got a further warning, > > > > > during the update, that I was low on space. > > > > > The update did seem to complete, though. > > > > [...] > > > > > > The only other thing I can suggest at present is running df while > > > > those warnings are being generated. > > > > > > May the OP have run out of inodes in / ? > > > > It's always possible, though the error message (wherever that's coming > > from) could be better. Posting the result of > > > > df -i > > > > would be far more use than df -h (and doesn't require root access). > > Or > df -ih > and have the best of both worlds! It's mean, though, isn't it. It takes away the space% when it adds the inode%. Cheers, David.
Re: Disk too full?
On Tue 05 Apr 2016 at 17:15:18 (+), Curt wrote: > On 2016-04-05, David Wrightwrote: > > > > It's always possible, though the error message (wherever that's coming > > from) could be better. Posting the result of > > > > df -i > > > > would be far more use than df -h (and doesn't require root access). > > df -h requires root access? No. To understand that line, you have to have read the thread, specifically: https://lists.debian.org/debian-user/2016/04/msg00271.html Cheers, David.
Re: Disk too full?
On 2016-04-05, David Wrightwrote: > > It's always possible, though the error message (wherever that's coming > from) could be better. Posting the result of > > df -i > > would be far more use than df -h (and doesn't require root access). df -h requires root access? > Cheers, > David. > > -- Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and so entirely in harmony with the demagogic appeals to cultural democracy that accompany (and distract one’s attention from) the ever-tightening grip of plutocratic capitalism. - Susan Sontag
Re: Disk too full?
On Tuesday 05 April 2016 17:46:24 David Wright wrote: > On Tue 05 Apr 2016 at 16:46:36 (+0100), Lisi Reisz wrote: > > On Tuesday 05 April 2016 15:34:37 David Wright wrote: > > > On Tue 05 Apr 2016 at 06:36:39 (-0500), Charles Blair wrote: > > > >I think I'm running out of space on my > > > > laptop. The last time I got an "updates > > > > available" message, I got a further warning, > > > > during the update, that I was low on space. > > > > The update did seem to complete, though. > > [...] > > > > The only other thing I can suggest at present is running df while > > > those warnings are being generated. > > > > May the OP have run out of inodes in / ? > > It's always possible, though the error message (wherever that's coming > from) could be better. Posting the result of > > df -i > > would be far more use than df -h (and doesn't require root access). Or df -ih and have the best of both worlds! Lisi
Re: Disk too full?
On Tue 05 Apr 2016 at 16:46:36 (+0100), Lisi Reisz wrote: > On Tuesday 05 April 2016 15:34:37 David Wright wrote: > > On Tue 05 Apr 2016 at 06:36:39 (-0500), Charles Blair wrote: > > >I think I'm running out of space on my > > > laptop. The last time I got an "updates > > > available" message, I got a further warning, > > > during the update, that I was low on space. > > > The update did seem to complete, though. [...] > > The only other thing I can suggest at present is running df while > > those warnings are being generated. > > May the OP have run out of inodes in / ? It's always possible, though the error message (wherever that's coming from) could be better. Posting the result of df -i would be far more use than df -h (and doesn't require root access). Cheers, David.
Re: Disk too full?
On Tuesday 05 April 2016 15:34:37 David Wright wrote: > On Tue 05 Apr 2016 at 06:36:39 (-0500), Charles Blair wrote: > >I think I'm running out of space on my > > laptop. The last time I got an "updates > > available" message, I got a further warning, > > during the update, that I was low on space. > > The update did seem to complete, though. > > > >However, when I tried to use the calculator > > program dc afterwards, the computer just sat > > there. > > > >Below is the output from the df command. > > Thanks very much for any help! > > > > Filesystem1K-blocksUsed Available Use% > > Mounted on rootfs 330215 193394119772 > > 62% / udev 10240 0 10240 0% > > /dev tmpfs400736 708400028 1% > > /run /dev/disk/by-uuid/0923...36f4ab8e330215 193394119772 62% / > > tmpfs 5120 0 5120 0% > > /run/lock tmpfs 2457480 84 2457396 > > 1% /run/shm /dev/sda10176581224 2269620 165341776 > > 2% /home /dev/sda9376807 10272347079 > > 3% /tmp /dev/sda6 8649992 6057732 2152864 > > 74% /usr /dev/sda7 2882592 1857652878508 > > 68% /var > > Well, you've survived over a year so you aren't doing so badly. The > main difference I can see is that your /var has increased from 19% > to 68%. Have you run that duse command on it recently? Here's my > wheezy /var but bear in mind that my /var/cache contains apt-cacher-ng > which is holding all the .deb files for both wheezy and jessie (and > backport and bits of sid). > >9087M /var/ > 11M /var/backups/ >8646M /var/cache/ > 376M /var/lib/ > 1M /var/local/ > 0M /var/lock/ > 53M /var/log/ > 1M /var/mail/ > 1M /var/opt/ > 1M /var/run/ > 1M /var/spool/ > 2M /var/tmp/ > > So apart from that cache, I've got 447MB and you've got 1.8GB. > How's your /var/tmp? I think you're responsible for any cleaning > done there, unlike /tmp. > > The only other thing I can suggest at present is running df while > those warnings are being generated. May the OP have run out of inodes in / ? Lisi
Re: Disk too full?
On Tue 05 Apr 2016 at 06:36:39 (-0500), Charles Blair wrote: >I think I'm running out of space on my > laptop. The last time I got an "updates > available" message, I got a further warning, > during the update, that I was low on space. > The update did seem to complete, though. > >However, when I tried to use the calculator > program dc afterwards, the computer just sat > there. > >Below is the output from the df command. > Thanks very much for any help! > > Filesystem1K-blocksUsed Available Use% Mounted on > rootfs 330215 193394119772 62% / > udev 10240 0 10240 0% /dev > tmpfs400736 708400028 1% /run > /dev/disk/by-uuid/0923...36f4ab8e330215 193394119772 62% / > tmpfs 5120 0 5120 0% /run/lock > tmpfs 2457480 84 2457396 1% /run/shm > /dev/sda10176581224 2269620 165341776 2% /home > /dev/sda9376807 10272347079 3% /tmp > /dev/sda6 8649992 6057732 2152864 74% /usr > /dev/sda7 2882592 1857652878508 68% /var Well, you've survived over a year so you aren't doing so badly. The main difference I can see is that your /var has increased from 19% to 68%. Have you run that duse command on it recently? Here's my wheezy /var but bear in mind that my /var/cache contains apt-cacher-ng which is holding all the .deb files for both wheezy and jessie (and backport and bits of sid). 9087M /var/ 11M /var/backups/ 8646M /var/cache/ 376M /var/lib/ 1M /var/local/ 0M /var/lock/ 53M /var/log/ 1M /var/mail/ 1M /var/opt/ 1M /var/run/ 1M /var/spool/ 2M /var/tmp/ So apart from that cache, I've got 447MB and you've got 1.8GB. How's your /var/tmp? I think you're responsible for any cleaning done there, unlike /tmp. The only other thing I can suggest at present is running df while those warnings are being generated. Cheers, David.
Re: Disk too full?
>Below is the output from the df command. > Thanks very much for any help! for everyone's convenience, please post # df -h 's output. regards, arian signature.asc Description: OpenPGP digital signature
Re: Disk too full?
>However, when I tried to use the calculator program dc afterwards, > the computer just sat there. What else did you expect from `dc`? Stefan
Disk too full?
I think I'm running out of space on my laptop. The last time I got an "updates available" message, I got a further warning, during the update, that I was low on space. The update did seem to complete, though. However, when I tried to use the calculator program dc afterwards, the computer just sat there. Below is the output from the df command. Thanks very much for any help! Filesystem1K-blocksUsed Available Use% Mounted on rootfs 330215 193394119772 62% / udev 10240 0 10240 0% /dev tmpfs400736 708400028 1% /run /dev/disk/by-uuid/0923...36f4ab8e330215 193394119772 62% / tmpfs 5120 0 5120 0% /run/lock tmpfs 2457480 84 2457396 1% /run/shm /dev/sda10176581224 2269620 165341776 2% /home /dev/sda9376807 10272347079 3% /tmp /dev/sda6 8649992 6057732 2152864 74% /usr /dev/sda7 2882592 1857652878508 68% /var