Re: solution to / full

2023-03-06 Thread Jonathan Dowland
On Mon, Mar 06, 2023 at 10:41:22AM +, Jonathan Dowland wrote: Quite. I habitually alias ls to 'ls -lhrt', (and cdls() { cd "$@" && ls -lhrt; }; alias cd=cdls) so I'm very used to only looking at the bottom of a long list of size-sorted-ascending. Err, of course, that's

Re: solution to / full

2023-03-06 Thread Jonathan Dowland
On Sat, Mar 04, 2023 at 11:10:48AM -0600, David Wright wrote: But then when there's a drove, the biggest go AWOL off the top of screen. Quite. I habitually alias ls to 'ls -lhrt', (and cdls() { cd "$@" && ls -lhrt; }; alias cd=cdls) so I'm very used to only looking at the bottom of a long

Re: solution to / full

2023-03-04 Thread David Wright
On Fri 03 Mar 2023 at 15:42:37 (-), Curt wrote: > On 2023-03-02, Jonathan Dowland wrote: > > On Thu, Mar 02, 2023 at 07:25:58AM -0500, Greg Wooledge wrote: > >>I don't understand why you used sort -r, but then reversed it again with > >>tac at the end. You could drop both of the reversals,

Re: solution to / full

2023-03-03 Thread davidson
On Fri, 3 Mar 2023 Curt wrote: On 2023-03-02, Jonathan Dowland wrote: On Thu, Mar 02, 2023 at 07:25:58AM -0500, Greg Wooledge wrote: I don't understand why you used sort -r, but then reversed it again with tac at the end. You could drop both of the reversals, and just change head to tail.

Re: solution to / full

2023-03-03 Thread Curt
On 2023-03-02, Jonathan Dowland wrote: > On Thu, Mar 02, 2023 at 07:25:58AM -0500, Greg Wooledge wrote: >>I don't understand why you used sort -r, but then reversed it again with >>tac at the end. You could drop both of the reversals, and just change >>head to tail. > > The short answer is

Re: solution to / full

2023-03-02 Thread Richard Hector
On 2/03/23 06:00, Andy Smith wrote: Hi, On Wed, Mar 01, 2023 at 02:35:17PM +0100, lina wrote: My / is almost full. # df -h Filesystem Size Used Avail Use% Mounted on udev126G 0 126G 0% /dev tmpfs26G 2.3M 26G 1% /run /dev/nvme0n1p2 23G 21G 966M

Re: solution to / full

2023-03-02 Thread David Wright
On Thu 02 Mar 2023 at 18:09:06 (-0500), songbird wrote: > Joe wrote: > ... > > On unstable, I have a /var/cache/apt/archives directory, from which apt > > autoclean, which I do occasionally, recently removed about 5G of > > packages (obviously too occasionally). There's still quite a bit there > >

Re: solution to / full

2023-03-02 Thread songbird
Andy Smith wrote: > Hello, > > On Wed, Mar 01, 2023 at 07:53:19PM +0100, Nicolas George wrote: >> Andy Smith (12023-03-01): >> > > /dev/nvme0n1p2 23G 21G 966M 96% / >> > > /dev/nvme0n1p6 267M 83M 166M 34% /boot >> > > /dev/nvme0n1p1 511M 5.8M 506M 2% /boot/efi >> > > /dev/nvme0n1p3

Re: solution to / full

2023-03-02 Thread songbird
Joe wrote: ... > On unstable, I have a /var/cache/apt/archives directory, from which apt > autoclean, which I do occasionally, recently removed about 5G of > packages (obviously too occasionally). There's still quite a bit there > as it was only autoclean and I prefer to keep downloads around for

Re: solution to / full

2023-03-02 Thread David Christensen
On 3/2/23 15:19, Felix Miata wrote: David Christensen composed on 2023-03-02 14:41 (UTC-0800): How do I make the settings live (other than rebooting, which might hang if there is a syntax error)? I think this is one of those things that systemctl daemon-reload does. [quote] So, it's a

Re: solution to / full

2023-03-02 Thread Felix Miata
David Christensen composed on 2023-03-02 14:41 (UTC-0800): > How do I make the settings live (other than rebooting, which might hang > if there is a syntax error)? I think this is one of those things that systemctl daemon-reload does. [quote] So, it's a "soft" reload, essentially; taking

Re: solution to / full

2023-03-02 Thread David Christensen
On 3/2/23 14:41, David Christensen wrote: On 3/2/23 00:53, lina wrote: > :/usr/lib$ du -sh * | sort -nr | grep -v K  | head > 981M R > 591M rstudio > 591M jvm > 554M mega > 538M llvm-11 > 343M modules > 313M libreoffice So, your computer has 3911M of apps in /usr/share. Corrections:

Re: solution to / full

2023-03-02 Thread David Christensen
On 3/1/23 05:35, lina wrote: > My / is almost full. > > # df -h > Filesystem Size Used Avail Use% Mounted on > udev126G 0 126G 0% /dev > tmpfs26G 2.3M 26G 1% /run > /dev/nvme0n1p2 23G 21G 966M 96% / On 3/1/23 15:03, Felix Miata wrote: > I limit

Re: solution to / full

2023-03-02 Thread Jonathan Dowland
On Thu, Mar 02, 2023 at 07:25:58AM -0500, Greg Wooledge wrote: I don't understand why you used sort -r, but then reversed it again with tac at the end. You could drop both of the reversals, and just change head to tail. The short answer is because I wrote all but the last "tac" several years

Re: solution to / full

2023-03-02 Thread Greg Wooledge
On Thu, Mar 02, 2023 at 09:45:38AM +, Jonathan Dowland wrote: > --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂ --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂-- > > STATUS_FILE=/var/lib/dpkg/status > dpigs() > { > TL=${1-10} > awk -v RS='' '/Status:.*installed\n/' "$STATUS_FILE" \ > | grep -E

Re: solution to / full

2023-03-02 Thread Jonathan Dowland
On Wed, Mar 01, 2023 at 03:15:07PM +0100, Jochen Spieker wrote: The program dpigs from the package debian-goodies can help you find the biggest debian packages you have installed. Of course you need to check yourself whether you need them. It's a shame that this requires installing

Re: solution to / full

2023-03-02 Thread Jonathan Dowland
On Wed, Mar 01, 2023 at 02:27:58PM -0700, Charles Curley wrote: You can find the large directory culprits quickly enough with cd / du -h | sort -h OP demonstrated that they know how to use ncdu, which is a far superior way of achieving the same result. Personally I like duc for this job (and

Re: solution to / full

2023-03-02 Thread tomas
On Thu, Mar 02, 2023 at 09:53:29AM +0100, lina wrote: > :/usr/lib$ du -sh * | sort -nr | grep -v K | head > 981M R > 591M rstudio > 591M jvm > 554M mega > 538M llvm-11 > 343M modules > 313M libreoffice Insightful, thanks :) Cheers -- t signature.asc Description: PGP signature

Re: solution to / full

2023-03-02 Thread lina
:/usr/lib$ du -sh * | sort -nr | grep -v K | head 981M R 591M rstudio 591M jvm 554M mega 538M llvm-11 343M modules 313M libreoffice On Thu, Mar 2, 2023 at 9:48 AM lina wrote: > Hi all, > > Thanks for your suggestions, > > I take the least risk way, just move the things from /opt away, > > I

Re: solution to / full

2023-03-02 Thread lina
Hi all, Thanks for your suggestions, I take the least risk way, just move the things from /opt away, I hope I can make it in the next few months, the biggest problem was created by the R associated package. /dev/nvme0n1p2 23G 18G 4.5G 80% / Thanks again, lina On Thu, Mar 2, 2023 at

Re: solution to / full

2023-03-01 Thread tomas
On Wed, Mar 01, 2023 at 06:12:05PM -0500, Greg Wooledge wrote: > On Wed, Mar 01, 2023 at 05:53:18PM -0500, Jeffrey Walton wrote: > > On Wed, Mar 1, 2023 at 8:35 AM lina wrote: > > > > > > My / is almost full. [...] > > > /dev/nvme0n1p2 23G 21G 966M 96% / [...] > > > /dev/nvme0n1p3 9.1G

Re: solution to / full

2023-03-01 Thread David Wright
On Wed 01 Mar 2023 at 19:53:09 (+), Andy Smith wrote: > On Wed, Mar 01, 2023 at 07:53:19PM +0100, Nicolas George wrote: > I was talking about them going to the effort of separating /home and > /var and ending up with completely inappropriate sizings. They would > have been much better off just

Re: solution to / full

2023-03-01 Thread Greg Wooledge
On Wed, Mar 01, 2023 at 05:53:18PM -0500, Jeffrey Walton wrote: > On Wed, Mar 1, 2023 at 8:35 AM lina wrote: > > > > My / is almost full. > > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > > udev126G 0 126G 0% /dev > > tmpfs26G 2.3M 26G 1%

Re: solution to / full

2023-03-01 Thread Felix Miata
Jeffrey Walton composed on 2023-03-01 17:53 (UTC-0500): > You can probably reclaim a couple of GB by trimming systemd logs. It > should get you some room to work. Something like: >journalctl --vacuum-time=14d I limit journal size this way: # cat /etc/systemd/journald.conf.d/local.conf

Re: solution to / full

2023-03-01 Thread Jeffrey Walton
On Wed, Mar 1, 2023 at 8:35 AM lina wrote: > > My / is almost full. > > # df -h > Filesystem Size Used Avail Use% Mounted on > udev126G 0 126G 0% /dev > tmpfs26G 2.3M 26G 1% /run > /dev/nvme0n1p2 23G 21G 966M 96% / > tmpfs 126G 15M 126G

Re: solution to / full

2023-03-01 Thread Charles Curley
On Wed, 1 Mar 2023 14:35:17 +0100 lina wrote: > My / is almost full. > > # df -h > Filesystem Size Used Avail Use% Mounted on > udev126G 0 126G 0% /dev > tmpfs26G 2.3M 26G 1% /run > /dev/nvme0n1p2 23G 21G 966M 96% / You can find the large

Re: solution to / full

2023-03-01 Thread David Christensen
On 3/1/23 05:35, lina wrote: Hi, My / is almost full. # df -h Filesystem Size Used Avail Use% Mounted on udev126G 0 126G 0% /dev tmpfs26G 2.3M 26G 1% /run /dev/nvme0n1p2 23G 21G 966M 96% / tmpfs 126G 15M 126G 1% /dev/shm tmpfs

Re: solution to / full

2023-03-01 Thread Brian
On Wed 01 Mar 2023 at 19:37:10 +0100, to...@tuxteam.de wrote: > On Wed, Mar 01, 2023 at 06:12:09PM +, Brian wrote: > > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > > > [...] > > > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > > package cache,

Re: solution to / full

2023-03-01 Thread Brian
On Wed 01 Mar 2023 at 13:33:32 -0500, Greg Wooledge wrote: > On Wed, Mar 01, 2023 at 06:12:09PM +, Brian wrote: > > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > > > [...] > > > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > > package cache, which

Re: solution to / full

2023-03-01 Thread Brian
On Wed 01 Mar 2023 at 19:48:59 +, Joe wrote: > On Wed, 1 Mar 2023 18:12:09 + > Brian wrote: > > > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > > > [...] > > > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > > package cache, which lives in

Re: solution to / full

2023-03-01 Thread Greg Wooledge
On Wed, Mar 01, 2023 at 07:53:34PM +, Joe wrote: > On Wed, 1 Mar 2023 13:33:32 -0500 > Greg Wooledge wrote: > > By default, "apt" removes the .deb files > > from /var/cache/apt/archives/ after installing them, but "apt-get" > > does not. For other programs, who knows. > > I've just asked

Re: solution to / full

2023-03-01 Thread Joe
On Wed, 1 Mar 2023 13:33:32 -0500 Greg Wooledge wrote: > On Wed, Mar 01, 2023 at 06:12:09PM +, Brian wrote: > > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > > > [...] > > > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > > package cache, which

Re: solution to / full

2023-03-01 Thread Andy Smith
Hello, On Wed, Mar 01, 2023 at 07:53:19PM +0100, Nicolas George wrote: > Andy Smith (12023-03-01): > > > /dev/nvme0n1p2 23G 21G 966M 96% / > > > /dev/nvme0n1p6 267M 83M 166M 34% /boot > > > /dev/nvme0n1p1 511M 5.8M 506M 2% /boot/efi > > > /dev/nvme0n1p3 9.1G 3.2G 5.5G 37% /var

Re: solution to / full

2023-03-01 Thread Joe
On Wed, 1 Mar 2023 18:12:09 + Brian wrote: > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > [...] > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > package cache, which lives in /var. You didn't show us /var, > > which might be interesting too

Re: solution to / full

2023-03-01 Thread Nicolas George
Andy Smith (12023-03-01): > > /dev/nvme0n1p2 23G 21G 966M 96% / > > /dev/nvme0n1p6 267M 83M 166M 34% /boot > > /dev/nvme0n1p1 511M 5.8M 506M 2% /boot/efi > > /dev/nvme0n1p3 9.1G 3.2G 5.5G 37% /var > > /dev/nvme0n1p5 1.8G 14M 1.7G 1% /tmp > > /dev/nvme0n1p7 630G 116G

Re: solution to / full

2023-03-01 Thread tomas
On Wed, Mar 01, 2023 at 06:12:09PM +, Brian wrote: > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > [...] > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > package cache, which lives in /var. You didn't show us /var, > > which might be interesting

Re: solution to / full

2023-03-01 Thread Greg Wooledge
On Wed, Mar 01, 2023 at 06:12:09PM +, Brian wrote: > On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: > > [...] > > > In a pinch, you can "sudo apt-get clean", which purges the APT > > package cache, which lives in /var. You didn't show us /var, > > which might be interesting

Re: solution to / full

2023-03-01 Thread Brian
On Wed 01 Mar 2023 at 17:43:41 +0100, to...@tuxteam.de wrote: [...] > In a pinch, you can "sudo apt-get clean", which purges the APT > package cache, which lives in /var. You didn't show us /var, > which might be interesting too (/var/log, in case some logs > aren't rotated properly?) There

Re: solution to / full

2023-03-01 Thread Andy Smith
Hi, On Wed, Mar 01, 2023 at 02:35:17PM +0100, lina wrote: > My / is almost full. > > # df -h > Filesystem Size Used Avail Use% Mounted on > udev126G 0 126G 0% /dev > tmpfs26G 2.3M 26G 1% /run > /dev/nvme0n1p2 23G 21G 966M 96% / > tmpfs

Re: solution to / full

2023-03-01 Thread The Wanderer
On 2023-03-01 at 09:15, Jochen Spieker wrote: > lina: > >> My / is almost full. >> >> # df -h >> Filesystem Size Used Avail Use% Mounted on >> udev126G 0 126G 0% /dev >> tmpfs26G 2.3M 26G 1% /run >> /dev/nvme0n1p2 23G 21G 966M 96% / >> tmpfs

Re: solution to / full

2023-03-01 Thread tomas
On Wed, Mar 01, 2023 at 02:35:17PM +0100, lina wrote: > Hi, > > My / is almost full. > > # df -h > Filesystem Size Used Avail Use% Mounted on > udev126G 0 126G 0% /dev > tmpfs26G 2.3M 26G 1% /run > /dev/nvme0n1p2 23G 21G 966M 96% / > tmpfs

Re: solution to / full

2023-03-01 Thread Klaus Singvogel
lina wrote: > Filesystem Size Used Avail Use% Mounted on [...] > /dev/nvme0n1p2 23G 21G 966M 96% / > /dev/nvme0n1p3 9.1G 3.2G 5.5G 37% /var > /dev/nvme0n1p5 1.8G 14M 1.7G 1% /tmp > /dev/nvme0n1p7 630G 116G 482G 20% /home [...] > I have done some purging already. > :/usr#

Re: solution to / full

2023-03-01 Thread Jochen Spieker
lina: > > My / is almost full. > > # df -h > Filesystem Size Used Avail Use% Mounted on > udev126G 0 126G 0% /dev > tmpfs26G 2.3M 26G 1% /run > /dev/nvme0n1p2 23G 21G 966M 96% / > tmpfs 126G 15M 126G 1% /dev/shm > tmpfs

solution to / full

2023-03-01 Thread lina
Hi, My / is almost full. # df -h Filesystem Size Used Avail Use% Mounted on udev126G 0 126G 0% /dev tmpfs26G 2.3M 26G 1% /run /dev/nvme0n1p2 23G 21G 966M 96% / tmpfs 126G 15M 126G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1%