Davi C. Rodrigues said the following on 10/16/2013 02:36 PM:

I see that the folder usr occupies 16.3 GB

What is in /tmp and /usr/tmp? What is in /lost+found? oh, and have you run fsck to see what state the file system is in and do some clean up. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Davi C. Rodrigues said the following on 10/16/2013 03:02 PM:

...

What is in /tmp and /usr/tmp?

3.4 MB files and 4 KB files

You should see about leaning /tmp then. There are many reasons why having /tmp on a separate FS (including some security ones that claim to have been overcome, but I'm a bit paranoid there) is a good idea. Of course if you have a lot of memory then /tmp (or some part of it) can be a tmpfs

...

What is in /lost+found?

Nothing.

GOOD! There are also some file cleanup tools such as * bleachbit including cleaning out unused languages - that's a LOT! * sweeper * fslint and of course judicious use of 'find' :-) -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward wrote:

...

...

What is in /tmp and /usr/tmp? 3.4 MB files and 4 KB files

You should see about leaning /tmp then.

There are many reasons why having /tmp on a separate FS (including some security ones that claim to have been overcome, but I'm a bit paranoid there) is a good idea. Of course if you have a lot of memory then /tmp (or some part of it) can be a tmpfs

It's possible to have /tmp cleared out automagically at boot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I am not an expert on such matters, but I cannot understand what the temp files have to do with my problem. They only occupy a very small fraction of the root, a few MB in 20 GB. Also, the logs seem not to be the source of trouble. sudo du -h /var/log root's password: 88K /var/log/ConsoleKit 4.0K /var/log/krb5 54M /var/log/journal/41ef233e76e7528b304b79b700000697 54M /var/log/journal 4.0K /var/log/samba 4.0K /var/log/hp 15M /var/log/YaST2 1.4M /var/log/zypp 4.0K /var/log/news 1.6M /var/log/cups 102M /var/log It seems that the safest thing to do is to uninstall the older version of Mathematica. If I do this, I will recover 3 GB. That helps, but unfortunately, that is not much, and I would like to preserve the old version... Probably the best thing to do would be to set a larger partition for root when I installed opensuse. Is there a safe and easy way to enlarge the root partition? Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Oct 16, 2013 at 4:42 PM, John Andersen wrote:

It seems to me that there was some noise on this list with systemD making this more complicated than it was in the past (it was never drop dead easy, unless, as mentioned you are sitting on a bunch of unallocated space).

If you have a initrd (which is default and almost everyone has), then /usr is mounted via logic in initrd prior to the systemd even starting from what I understand. Thus systemD neither makes it easier nor harder since /usr is mounted prior to it starting. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* John Andersen [10-16-13 16:45]: [...]

...

It seems that the safest thing to do is to uninstall the older version of Mathematica. If I do this, I will recover 3 GB. That helps, but unfortunately, that is not much, and I would like to preserve the old version... Probably the best thing to do would be to set a larger partition for root when I installed opensuse. Is there a safe and easy way to enlarge the root partition?

You can only resize a partition if you have spare space on the drive, or if you can shrink some other partition. Gpartd can do this.

But in your case you may find it simpler to move /usr to its own partition.

It seems to me that there was some noise on this list with systemD making this more complicated than it was in the past (it was never drop dead easy, unless, as mentioned you are sitting on a bunch of unallocated space).

there is aways LVM, and changing partitioning is not necessary. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 10/16/2013 2:18 PM, Greg Freemyer wrote:

On Wed, Oct 16, 2013 at 4:42 PM, John Andersen wrote:

...

It seems to me that there was some noise on this list with systemD making this more complicated than it was in the past (it was never drop dead easy, unless, as mentioned you are sitting on a bunch of unallocated space).

Yes... it does.

If you have a initrd (which is default and almost everyone** has), then /usr is mounted via logic in initrd prior to the systemd even starting from what I understand.

--- **"everyone"=those who don't care as much about speed. The systemd reference pages suggest *NOT* using initrd for faster boot. Who knows, maybe suse will support faster boots in the future. Right now, they are still trying to cope with all the reqs and changes of systemd to get to secure EFI booting to produce appliance systems. I threw in a few crutches for the rest of the boot process in: /etc/rc.d/boot.d: S01boot.sysctl@ S01boot.usr-mount@ S02boot.udev@ S05boot.clock@ S06boot.device-mapper@ S06boot.loadmodules@ S06boot.localnet@ S07boot.assign_netif_names@ S07boot.cgroup@ S10boot.lvm@ S11boot.localfs@ <-- this is about 14secs from kernel unpacking. S13boot.klog@ S13boot.lvm_monitor@ S13boot.swap@ <--- and at ~16 secs... [ 10.200027] bio: create slab <bio-1> at 1 [ 10.843408] bio: create slab <bio-2> at 2 [ 14.414724] XFS (sdc3): Mounting Filesystem [ 14.485300] XFS (sdc3): Ending clean mount [ 14.492799] XFS (dm-3): Mounting Filesystem [ 14.676810] XFS (dm-3): Ending clean mount ... [ 16.374981] Adding 8393924k swap on /dev/sdc5. Priority:-1 extents:1 across:8393924k FS Kernel logging (ksyslog) stopped. --- Before that it's all HW startup... ~20-25 seconds later and all services are up. Basically I use the "boot" phase to setup the system to handle system services ... with systemd starting after the initial "boot" phase (or initrd phase)... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org