Is there a way to find out? I ask because I recently was trying to install a program and Yast told me I was low on space and specified some drive I’m sure isn’t the main directory. As I checked that and have well over 600 gigabytes of storage to spare. I’m so confused. All app content including repositories and such I thought went to the main directory by default.
As this is clearly about installing software and not about hardware, this will be moved to Install/Boot/Login and is CLOSED for the moment.
Moved from Hardware and open again.
I think there are two questions here, one about where files belonging to an installed package are stored in the directory tree of a system and the other about a particular case where YaST reports that there is no space enough.
The general question.
Packages coming from most repositories (certainly the OSS, non-OSS and Packman repos, but many others), have files that are stored in what are loosely called “system directories”. The idea is to have e.g. a application’s executables in /us/bin, it’s configuration files in /etc, it’s libraries in /lib, etc. There is a recommendation about this in the Filesystem Hierarchy Standard: Filesystem Hierarchy Standard - Wikipedia. Those directories are in most cases (certainly in home systems) part of the root file system (mounted on /), to be sure that they are always available even if some other partitions can not be mounted.
The specific case.
As you do provide about nil information about your case, not much help is possible. You could at least tell things like:
- the package you try to install and the repo it should come from;
- the exact messages YaST and/or zypper shows you;
- when the message is about “not enough space” the output of
df-h
;
- any other information you think can be relevant to the problem.
We re not clairvoyant.
hi,
select -yast --Software Management
if the Repositories tab cannot be seen, press
-View tab then --Repositories
in the left panel select
in the right upper panel select the package of interest
from the tabs below select
-File List
in the right bottom panel all files and destinations are shown
hth
Or simply use the Search field from the first/main View you get when starting YaST > Software > Software Management.
But you then get information about the files of an installed package. The OP seems to have problems wen he tries to install a package, thus the package is still not installed, thus this information is not available for that package.
perhaps the root partition is full and he is looking at the home partition space. If so it may be that snapper is taking up too much space. Need to see df -a output
Also we don’t know how some programs may be installed ie any compiled programs? Else you can see where any given program is installed in Yast as mentioned above
On 2015-08-25 10:46, hcvv wrote:
> The specific case.
> As you do provide about nil information about your case, not much help
> is possible. You could at least tell things like:
Yep.
A possibility with YaST is that it can warn about lack of space in
“other” partitions, if they exist.
There is a little hidden feature of the yast package manager (QT
flavour). At the bottom of the left panel you can click and drag open a
little panel that displays the size of all mounted partitions, a
coloured bar graph, showing in red those partitions with 90% full (I
think). Thus in mine /home shows in red, even though that means 12GB free.
I think, I have not seen it in a long time, that beyond a certain limit,
it can also warn before an installation.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
David@linux-gu7v:~> df -aFilesystem 1K-blocks Used Available Use% Mounted on
rootfs - - - - /
sysfs 0 0 0 - /sys
proc 0 0 0 - /proc
devtmpfs 3011080 0 3011080 0% /dev
securityfs 0 0 0 - /sys/kernel/security
tmpfs 3017868 56116 2961752 2% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 3017868 2212 3015656 1% /run
tmpfs 3017868 0 3017868 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/cpuset
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/memory
cgroup 0 0 0 - /sys/fs/cgroup/devices
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/net_cls,net_prio
cgroup 0 0 0 - /sys/fs/cgroup/blkio
cgroup 0 0 0 - /sys/fs/cgroup/perf_event
cgroup 0 0 0 - /sys/fs/cgroup/hugetlb
/dev/sda3 41946112 9296208 31534448 23% /
efivarfs 0 0 0 - /sys/firmware/efi/efivars
systemd-1 0 0 0 - /proc/sys/fs/binfmt_misc
mqueue 0 0 0 - /dev/mqueue
debugfs 0 0 0 - /sys/kernel/debug
hugetlbfs 0 0 0 - /dev/hugepages
/dev/sda3 41946112 9296208 31534448 23% /.snapshots
/dev/sda3 41946112 9296208 31534448 23% /var/tmp
/dev/sda3 41946112 9296208 31534448 23% /var/spool
/dev/sda3 41946112 9296208 31534448 23% /var/log
/dev/sda3 41946112 9296208 31534448 23% /var/opt
/dev/sda3 41946112 9296208 31534448 23% /var/lib/pgsql
/dev/sda3 41946112 9296208 31534448 23% /var/lib/named
/dev/sda3 41946112 9296208 31534448 23% /var/lib/mailman
/dev/sda3 41946112 9296208 31534448 23% /var/crash
/dev/sda3 41946112 9296208 31534448 23% /usr/local
/dev/sda3 41946112 9296208 31534448 23% /tmp
/dev/sda3 41946112 9296208 31534448 23% /srv
/dev/sda3 41946112 9296208 31534448 23% /opt
/dev/sda3 41946112 9296208 31534448 23% /boot/grub2/x86_64-efi
/dev/sda3 41946112 9296208 31534448 23% /boot/grub2/i386-pc
/dev/sda1 159564 4916 154648 4% /boot/efi
/dev/sda4 688026384 862412 687163972 1% /home
fusectl 0 0 0 - /sys/fs/fuse/connections
gvfsd-fuse 0 0 0 - /run/user/1000/gvfs
That’s what I got.
Ok so you have used only about 23% of available space for files on root. Are you actually getting out of space errors? if so then you need to reduce the amount and frequency of snapshots. Snapper is set pretty aggressive you can see the command line usage with **man snapper **or there is a yast module that lets you set options.