Yast trying to install in a external hdd ?

Hi
I’ve someone asking this in the forum, but I can’t find in the search.
This was happening in 13.2 too.
Every time, I have a external hdd plug, yast warns me ( upon some package installation), about running out of space in that hdd.
Not sure why, Yast wants to install it on that hdd.
This doesn’t happen with zypper. Just Yast or the ( software installer ? )

Not sure if there is a fix to this, and not sure what happens, if I would click to proceed.

Thanks

Post specifics about what you’re seeing.
Take pictures if necessary, post somewhere and link in your post.

And, of course you need to identify the app you’re trying to install.

Posting your disk layout would be useful, too…
Post the result of the following command after your external drive is connected.

df -u

TSU

Thanks for the reply
Curiously enough, I’ve reinstall opensuse, and I made some installations through Yast with my external hdd plugged, and it did not happen…
But it was happening, in 13.2, and when I posted .
If it happens again, I’ll try to paste a screenshot, and that info.

Does not make sense unless you booted from that external/ RPM installs all go to root partition unless you have added additional partition in an odd way

Yast will give this warning if there’s a blank space in the volume name. See here: https://forums.opensuse.org/showthread.php/506145-YAST-warning-of-low-disk-space-in-unrelated-mounted-partition-with-more-than-800-GB-free?p=2701717#post2701717

Well, yesterday didn’t happen, today, has happen again. The external drive, has been connected from the start.

Here is a screenshot :

I was not able to do df -u , so here’s a df- a :


daniel@myopensuse:~/DevApp/libsass/libsass> df -ah
Filesystem      Size  Used Avail Use% Mounted on
sysfs              0     0     0    - /sys
proc               0     0     0    - /proc
devtmpfs        2,7G     0  2,7G   0% /dev
securityfs         0     0     0    - /sys/kernel/security
tmpfs           2,8G  424K  2,8G   1% /dev/shm
devpts             0     0     0    - /dev/pts
tmpfs           2,8G  2,2M  2,8G   1% /run
tmpfs           2,8G     0  2,8G   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/blkio
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/perf_event
cgroup             0     0     0    - /sys/fs/cgroup/hugetlb
/dev/sda6        36G  9,7G   26G  28% /
systemd-1          0     0     0    - /proc/sys/fs/binfmt_misc
debugfs            0     0     0    - /sys/kernel/debug
hugetlbfs          0     0     0    - /dev/hugepages
mqueue             0     0     0    - /dev/mqueue
/dev/sda6        36G  9,7G   26G  28% /.snapshots
/dev/sda6        36G  9,7G   26G  28% /var/spool
/dev/sda6        36G  9,7G   26G  28% /var/tmp
/dev/sda6        36G  9,7G   26G  28% /var/opt
/dev/sda6        36G  9,7G   26G  28% /var/log
/dev/sda6        36G  9,7G   26G  28% /var/lib/pgsql
/dev/sda6        36G  9,7G   26G  28% /var/lib/named
/dev/sda6        36G  9,7G   26G  28% /var/lib/mysql
/dev/sda6        36G  9,7G   26G  28% /var/lib/mariadb
/dev/sda6        36G  9,7G   26G  28% /var/crash
/dev/sda6        36G  9,7G   26G  28% /var/lib/mailman
/dev/sda6        36G  9,7G   26G  28% /var/lib/libvirt/images
/dev/sda6        36G  9,7G   26G  28% /usr/local
/dev/sda6        36G  9,7G   26G  28% /tmp
/dev/sda6        36G  9,7G   26G  28% /srv
/dev/sda6        36G  9,7G   26G  28% /opt
/dev/sda6        36G  9,7G   26G  28% /boot/grub2/x86_64-efi
/dev/sda6        36G  9,7G   26G  28% /boot/grub2/i386-pc
/dev/sda7        68G  6,7G   62G  10% /home
gvfsd-fuse         0     0     0    - /run/user/1000/gvfs
tracefs            -     -     -    - /sys/kernel/debug/tracing
/dev/sdb1       466G  274G  193G  59% /run/media/daniel/Apollo M100 USB3




http://paste.opensuse.org/images/1244365.png

It is a strangle problem, but as brunomcl has already mentioned, it’s been reported previously with openSUSE 13.2 and still lingering it would seem…

https://bugzilla.opensuse.org/show_bug.cgi?id=928639
https://forums.opensuse.org/showthread.php/502498-Yast-2-annoying-and-erroneous-complaint-about-not-having-space-when-installing-packages

Change the disk label so that white space characters are removed and you should be ok eg ‘Apollo_M100_USB3’

Thanks
hum…never done that in linux. Is it possible to do that without formatting ?

Which file system is in use on that device?

Doh…don’t how I managed that… or course I meant strange lol!

Refer ‘man e2label’ for ext2/ext3/ext4 file systems
Refer ‘man mlabel’ for MSDOS volume labels

It’s a ntfs external drive …

That does seem to be an odd message, but based on the file name it might have something to do with mounting the external USB3 device and not actually trying to install a file at that location (but I can’t know for sure since I’m not sure what libsass is doing with the external device). Also, You might notice that the that the filename itself contains a backslash not followed by a character to be escaped, which I’m not sure what would be the consequence.

What might happen if you try to delete possibly corrupt file (or reboot since /run in mounted as tempfs)

For example, in a root console

rm -r /run/media/daniel/*

Reading up a bit on what libsass is, it appears that originally it was written in Ruby, but people thought so much of it that it was ported to C/C++ as “libsass” so that it could be wrapped for use in other languages.

This suggests that although you’d probably still need to compile on your own for latest features and functionality (as of today, latest git contrib was 2 mths ago), you’d likely be able to get a “wrapped” libsass ready to go for the specific language you are developing in. If openSUSE isn’t providing latest, there is a pretty good likelihood it’s already available in the official repos for whatever language you are using (ie python = pip, ruby = gem, node = npm, etc). If you want to explore the official repos for your language, I’ve done some writeups how to setup for Ruby and Nodejs at the following wiki pages. A similar approach should be implemented for python using virtualenv.

https://en.opensuse.org/User:Tsu2/Install_Ruby
https://en.opensuse.org/User:Tsu2/nodejs

HTH,
TSU

Thanks
I don’t think this is related to the libsass. It already happen in 13.2
I’ll be changing the name for something with no spaces, but no sure if the mlabel formats or not the drive, and I have a lot of stuff that I can’t loose, so I’ll be cautious, hum…maybe doing it in windows ?rotfl!

But , what’s strange, it’s that only happens sometimes.
I’ll be changing the name, and then post the results.

Thanks

For NTFS, you can use ‘ntfslabel’.

Then general form is

sudo ntfslabel <device> <label>

Unmount the device first, then assuming ‘fdisk -l’ shows the device as /dev/sdb1, you’d use

sudo ntfslabel /dev/sdb1 Apollo_M100_USB3

Refer ‘man ntfslabel’ for more info.

Yes, but use the ‘ntfslabel’ utility if using Linux, or rename via a Windows machine instead.

only to confirm, in my
PC=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 @ 1.60GHz, OS=opensuse 13.2 KDE= 4.14.9
happen the same error, if I answer yes it continue without (it seems) problems
my disk is without spaces in
/run/media/user/backup4/
and it is ext3 filesystem
manythanks ciao pier