path / mount folder confusion trying to install Spotify

-First of all, if I find software or a 1 click install in this location (https://software.opensuse.org/package/) can assume it is safe / vetted? https://software.opensuse.org/package/spotify-easyrpm

-Midway through the install / download, I get interrupted with “disk space on partition /run/media/dcnblues/apple\040500 is nearly exhausted.” I canceled the install. Does this mean a bunch of useless data is still on that partition file? I certainly hope not (it doesn’t appear so).

-Opensuse is on a roomy new SSD. Why wouldn’t the installer try to put the app there?

-I have a couple of external drives in the PC. One is named ‘apple 500.’ Does Linux identify that as apple\040500?

-Granted, I have music files on that drive. Is it possible the installer somehow decided that was where to dump a repository?

-How do I fix this?

Well how big is your root partition?? if too small you can get filled up with snapshots if you use BTRFS (the default) on root partition.

Need to see your drives/partitions to do anything but make wild guesses

show fdisk -l
paste using code block to stop the forum editor fro reformatting (# in tool bar)

There is no “forum editor”, and the Forums Team is not going to reformat posts :=). But, you’re right, people should use CODE blocks

disk space on partition /run/media/dcnblues/apple\040500 is nearly exhausted

That is only a warning that you have less than 10% (or so) of free disk space on that device and has nothing to do with the Installation of any Package.
That is maybe your Apple device, see inside with dolphin.

Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AB6F2783-A2B0-4DB3-8910-8DBFC0B50447

Device        Start        End   Sectors   Size Type
/dev/sda1      2048     321535    319488   156M EFI System
/dev/sda2    321536    4530175   4208640     2G Microsoft basic data
/dev/sda3   4530176   88422399  83892224    40G Microsoft basic data
/dev/sda4  88422400 1000214527 911792128 434.8G Microsoft basic data


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9B804B44-52DE-43B3-9A60-3EA57953714C

Device      Start       End   Sectors   Size Type
/dev/sdb1      40    409639    409600   200M EFI System
/dev/sdb2  409640 976510983 976101344 465.5G Microsoft basic data


Disk /dev/sdc: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8868F9C4-D7A6-4364-AF0E-0ACB37EE80A3

Device       Start        End   Sectors   Size Type
/dev/sdc1     2048     923647    921600   450M Windows recovery environment
/dev/sdc2   923648    1128447    204800   100M EFI System
/dev/sdc3  1128448    1161215     32768    16M Microsoft reserved
/dev/sdc4  1161216 1000214527 999053312 476.4G Microsoft basic data


Disk /dev/sdd: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb275bdcd

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdd1  *        2 1465149167 1465149166 698.7G  7 HPFS/NTFS/exFAT



I still don’t know if this is a Linux naming conversion. The question in my original post: I have a couple of external drives in the PC. One is named ‘apple 500.’ Does Linux identify that as apple\040500?

And I still don’t understand why it would try to download a repository to that device. Don’t they go into a standard location?

And I still don’t understand why it would try to download a repository to that device. Don’t they go into a standard location?

Where does zypper/Yast say this???

Once more:
The “Error” is no Error, only a warning by the System, not the Package Manager (zypper/Yast).
So zypper/Yast will not install anything to that location.

Most probably yes. As octal 040 is the code for a blank space in ASCII, apparently \040 is used to avoid having blank spaces in that directory name.

Apparently ‘apple 500’ is the label of a file system on (a partition of) a mass storage device. The file system is mounted by the desktop session running for user dcnblues on the directory /run/media/dcnblues/apple\040500.

The message is a bit confusing because it talks about the space “on partition” instead of “on file system”. But that confusion is widespread because often (as in this case) the file system is on a partition and many see them as one and the same (which is NOT true).

And I, like the others, doubt very, very much that any installation from an openSUSE repository will ever try to store data in the directory tree starting at /run/media/dcnblues/apple\040500. So there is no connection between your installation action and the message.

When you install an application the software gets installed in various place off the root directory. The location of the root directory is set by where linux was initially installed to so chances are that it may be installed to the partition with limited space. If you open a console and enter this command it should along with the fdisk output help determine where linux was installed.


df /

On my system the command produces this


df /
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2       40185204 14420244  23700580  38% /

Output in a file manager can be a little confusing in some ways. For instance I decided to install /home to a totally separate partition on a different disk. The file manager doesn’t show this. The df command does though


 df /home
Filesystem     1K-blocks      Used Available Use% Mounted on
/dev/md0       961301640 116288476 844020020  13% /home

Perhaps you chose a default install in terms of the partitioning - which disks to use but you are free to set that up according to your needs when you install. If you don’t set this up yourself the install will make a choice for you. That will usually be fine but there is a need to look at the proposed partitioning and use the custom option if it’s not as desired. As I have several disks I find that adding disk labels to each helps me identify which one is which.

John

df is not exactly working on btrfs Filesystems.

btrfs fi df <path>