Seems to me that yast2 have some wrong setting somewhere because: after I had mounted my external HDD, suddenly yast2 started to complain about lack of space on this external HDD !!!
To be more specific, i get this warning when trying to install some new package from the repositorie(s) list:
“The diskspace in partition /run/media/cornel/ADATA \040CH94 is nearly exhausted.
Continue with installation ? (Yes/No)”
The external HDD is mounted into the path /run/media/cornel/ADATA CH94 (OK, the disk;s label has a space in it’s name … but this didn’t had any issues back in previous installment of OpenSUSE 13.1, and the previous versions, like 12.3, 12.2 a.s.o)
More, disk space is far from being exhausted on that disk (it has some 750 GB, out of which is has about 300 GB free !)
Yast2 compains with the same message even after I unmount that external disk !!! (which is even more frustrating).
OK, if I chose YES, installation goes OK, and on the PC’s HDD, of course.
But the message is mind boggling, and (for me) without any logical reason.
Can anyone give a hand into figuring out why this is happening ?
Something new about the issue:
after restarting PC, when using yast2 without the external HDD being mounted, it does work OK.
But as soon as I mount it, yast2 starts again to complain about lack of space on that HDD ! (of course, despite the warning, it installs OK the packages into the PC’s harddisk, without any problem but this strange warning).
On 11/17/2014 08:46 AM, Ace wrote:
>
> Same problem here. It is warning about low space on ext4 device mounted
> by hand and not by fstab even with +40 GiB space on it.
>
>
Just curious, what is the % space available? Could the warning be
triggered by “%” instead of “space”?
I checked it again, there are 82.2 GB free from 984.4 GB. But why is yast complaining, the partition has nothing to do with installations or anything. Its just a HDD for data which some times is mounted, there aren’t any system relevant files on it.
On 11/17/2014 09:26 AM, Ace wrote:
>
> I checked it again, there are 82.2 GB free from 984.4 GB. But why is
> yast complaining, the partition has nothing to do with installations or
> anything. Its just a HDD for data which some times is mounted, there
> aren’t any system relevant files on it.
>
>
Well, space available < 10% which could be the trigger. Doesn’t matter
that the available space > 80GB. If you had a 3TB drive with 250GB left
it is still less then 10%. Do you follow me on the theory?
Well, I think the issue with less than 10% free space on the disk would be appropriate if that disk would be the / partition, right ?
But since the complain is about an external disk, which happen to be mounted at the time of installing with yast2, this is very strange.
Even more strange is that if that external disk is formatted with Windows partition (NTFS for instance) this does not happen anymore !!
The external disk which caused me this problem was, indeed, formatted as EXT4.
And, as far as my case is concerned, I had way more than the minimum 10 % free on the external disk anyway (my external HDD with EXT4 partition has around 35% free space, while the other one, with NTFS has around 45% free space).
And besides, despite this warning, yast2 still installs the package(s) on the correct partition
> And, as far as my case is concerned, I had way more than the minimum
> 10 % free on the external disk anyway (my external HDD with EXT4
> partition has around 35% free space, while the other one, with NTFS
> has around 45% free space).
This problem was cropping up with the development 13.2 iso’s but I
hadn’t noticed it with the final release on the 64-bit DVD.
I had been getting this warning for my /home partition, amongst others,
which had 95% space remaining - about 1.8TiB!
–
Graham Davis [Retired Fortran programmer - now a mere computer user]
openSUSE Tumbleweed (64-bit); KDE 4.14.2; AMD Phenom II X2 550
Processor; Kernel: 3.17.2; Video: nVidia GeForce 210 (using nVidia
driver); Sound: ATI SBx00 Azalia (Intel HDA)
Well, I tried to see if there’s anything about that label of the external disk which gives me the problem described in the first post.
So, using gparted, I changed the label of the external disk (that one with EXT4 partition).
I chose only a single word (not spaces, not even numbers in it), and now it’s simply labeled ADATA.
And, it seems that now there’s no problem anymore
Just tried 3 times installing different new packages from yast2, an there were no more warnings about that strange lack of space !
I suppose that’s why I had no issue with the other external disk I’ve tried (which really did has a label without spaces).
So, I think this will be the final resolution for the issue: after changing the label (so that it does not contain spaces in it) it doesn’t occur.
I can’t find anything related to the text of the warning (what has got to do the label with spaces in the name with lack of space on the disk involved), but at least there’s no more warnings.
On 2014-12-03 23:56, cuchumino wrote:
>
> I had a similar issue with an external hard drive. I had the annoying
> complaint.
>
> As soon as I added the entry to fstab, the problem was solved. Thanks!
All of you should report your findings in Bugzilla.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I have the same problem with an FSS shared directory called “Server Storage”.
Here’s a new wrinkle to this mystery: I actually have two shared directories with white space in their names (“Server Storage” and “Server Storage 2”), but YAST only complains about the first one.:?
Unfortunately for me these directory names are referenced all over my laptop via sym-links, so I think I’ll put up with this minor inconvenience until a fix comes along.
