Hi,
I’m new to OpenSuse. Maybe it’s specific feature, but it does not seem right that within ~30 m to 1h 3gb of disk space on /home are gone due to I can’t tell what exactly. Usually it happens while listening to music via vlc or browsing www (chrome and firefox). I got 3gigs of ram (95% in use under such conditions), and 1,5gb of swap that is not used at all by the system. Its a KDE.
Where is the problem? Please help
are you saying that when you close vlc, chrome or firefox that that
space remains used?
i ask because it is normal when streaming in video/audio for the
stream to be buffered in an on disk cache…so, you should expect
available space to decrease anytime you are consuming a media stream…
but, depending on how you have set up those devices they should
release the space (delete the cache)…
you might check the size of ~/.vlc/cache and etc before and after that
30 minutes to an hour of playing…and, then again after shutting down
the application(s) to see which is the user not releasing its cache
space…and, then adjust some settings, somewhere…
sorry, i don’t how to set the space release timing for any of those
programs…but, i bet someone here does…
–
palladium
du -smc /home/yourname/*
tells you how much disk space is being used in the subdirectories of your home directory. You may need to also try
du -smc /home/yourname/.*
to catch the hidden files. Spend some time drilling down until you find the culprit. Then we might be able to offer appropriate help. Certainly do a before and after measurement to be sure about roughly where you are losing such a large amount of disk space.
Is it possible that the user is browsing over a local network using a protocol such as fish:// in KDE, which (IIRC) makes a temporary copy of e.g. a media file?
3 Gbyte is about 1.5 hours of hi-res video. I’d expect to see the copy in /tmp rather thann /home though.
Is nepomuk enabled? This might generate a database and might account for some space loss on /home.
Check under Configure Desktop - Advanced - Desktop Search (I think…)
You can also try running the following to give you an idea of what is so big.
Run the following command in a terminal:
du -ah /home
Hope that works…
I suspect it may be .xsession-errors (a hidden file in your home dir) filling up quickly. I’ve seen such reports about it exploding in size. If it really is, best is to make a symlink to /dev/null using a script you place in .kde4/Autostart
#!/bin/bash
ln -sf /dev/null $HOME/.xsession-errors
Make sure to make the file executable 
That’s what I like about this forum, one learns stuff. I thought I knew how to use du, but the -a option seems to have passed me by.
It happens after I run vlc playing music from my hard drive. Xorg seems to be very busy (25% of CPU power) and it takes nearly 115MB of memory. from the pint when all free space on /home and ram is gone, xorg calms down, but still engages all that memory.
then i cleared trash freeing some 200mb and xorg started working again until all remaining disk space was gone. I did not find any enormously big files, yet.
very bad practice to allow the disk to run out of space…all Unix and
variants really don’t like no space…can lead to corrupted files and
whole system…
you say you are running out of space on /home, but are you sure it is
not somewhere on root /?
how did you lay out your system?
can you do these in a terminal and copy paste back to here:
df --print-type
df -h
cat /etc/fstab/
and, i see someone else asked you for
du -ah /home
and another directed a link to direct some log reports to /dev/nul
but apparently you didn’t do either, or respond to those…
i guess my question is: do you want help, or not?
–
palladium
I dont know honestly
how did you lay out your system?
can you do these in a terminal and copy paste back to here:
df --print-type
df -h
cat /etc/fstab/
/dev/sda6 ext4 8927840 6261564 2212716 74% /
udev tmpfs 1544800 488 1544312 1% /dev
/dev/sda7 ext4 4659096 4422352 8 100% /home
/dev/sda1 fuseblk 102396 24924 77472 25% /windows/C
/dev/sda2 fuseblk 66281660 51656020 14625640 78% /windows/D
/dev/sda3 fuseblk 74533884 71941916 2591968 97% /windows/E
tomek@linux-9ll1:~> df -h
System plików rozm. użyte dost. %uż. zamont. na
/dev/sda6 8,6G 6,0G 2,2G 74% /
udev 1,5G 488K 1,5G 1% /dev
/dev/sda7 4,5G 4,3G 8,0K 100% /home
/dev/sda1 100M 25M 76M 25% /windows/C
/dev/sda2 64G 50G 14G 78% /windows/D
/dev/sda3 72G 69G 2,5G 97% /windows/E
when i use cat /etc/fstab/ , system says that /etc/fstab/ is not a directory
and, i see someone else asked you for
du -ah /home
and another directed a link to direct some log reports to /dev/nul
but apparently you didn’t do either, or respond to those…
yes, I didnt respond
command du gave me information on my files, directories, yet I did not find anything strange
I used the ln command, and made the file .xsession-errors executable. although i’m not sure how to take advantage of it yet. when i try to access dev/null it says null is neither a file or directory. same with .xsession-errors, but i can see it is there
i guess my question is: do you want help, or not?
–
palladium
of course. I really apreciate your help. what can i do next?
Please post output of this ( a bit more of ‘du-enjoy’ ):
du -h /home/YOURUSERNAMEHERE --max-depth=1
This shows the size of the folders in your /home/YOURUSERNAME
IMHO these days 4.5 GB is small for a /home.
I hardly dare to ask: Did you empty the Trash lately?
tomekbin wrote:
> palladium;2116915 Wrote:
>> very bad practice to allow the disk to run out of space…all Unix and
>> variants really don’t like no space…can lead to corrupted files and
>> whole system…
>>
>> you say you are running out of space on /home, but are you sure it is
>> not somewhere on root /?
>>
> I dont know honestly
>> how did you lay out your system?
>>
>> can you do these in a terminal and copy paste back to here:
>>
>> df --print-type
>> df -h
>> cat /etc/fstab/
>>
>
> Code:
> --------------------
>
> /dev/sda6 ext4 8927840 6261564 2212716 74% /
> udev tmpfs 1544800 488 1544312 1% /dev
> /dev/sda7 ext4 4659096 4422352 8 100% /home
> /dev/sda1 fuseblk 102396 24924 77472 25% /windows/C
> /dev/sda2 fuseblk 66281660 51656020 14625640 78% /windows/D
> /dev/sda3 fuseblk 74533884 71941916 2591968 97% /windows/E
>
> --------------------
>
>
>
> Code:
> --------------------
>
> tomek@linux-9ll1:~> df -h
> System plik�w rozm. użyte dost. %uż. zamont. na
> /dev/sda6 8,6G 6,0G 2,2G 74% /
> udev 1,5G 488K 1,5G 1% /dev
> /dev/sda7 4,5G 4,3G 8,0K 100% /home
> /dev/sda1 100M 25M 76M 25% /windows/C
> /dev/sda2 64G 50G 14G 78% /windows/D
> /dev/sda3 72G 69G 2,5G 97% /windows/E
>
> --------------------
>
>
> when i use cat /etc/fstab/ , system says that /etc/fstab/ is not a
> directory
>
>> and, i see someone else asked you for
>>
>> du -ah /home
>>
>> and another directed a link to direct some log reports to /dev/nul
>>
>> but apparently you didn’t do either, or respond to those…
>>
> yes, I didnt respond
> command du gave me information on my files, directories, yet I did not
> find anything strange
> I used the ln command, and made the file .xsession-errors executable.
> although i’m not sure how to take advantage of it yet. when i try to
> access dev/null it says null is neither a file or directory. same with
> .xsession-errors, but i can see it is there
>
>>
>>
>> i guess my question is: do you want help, or not?
>>
>> –
>> palladium
>
> of course. I really apreciate your help. what can i do next?
>
>
to me it looks like you just make one of a very few choices:
-buy a new larger hard drive and move all your stuff to it
-add secondary drive and move some of the stuff you have on the
original to the secondary
-move some static stuff that you can live with somewhere else (pics,
songs, movies etc) to DVDs or CDs
bottom line is you just don’t have enough space for the stuff you
have…on the other hand your C drive is not nearly fully used but,
then again it might be ‘boxed in’ and probably doesn’t have enough to
help a lot…
yes, if you listen to music you are gonna build temp files…what you
might do is set your vlc or whatever to use a directory in the C drive
for temp files…but, i don’t really know if that would work (because
Redmond file systems don’t all have the ability to carry permissions
and etc…and, i have NO idea what a fuseblock file system is??
sorry, but someone else is gonna have to pick up your problem if you
wanna continue to try to avoid the BEST solutions: more drive space
oh, and sorry about
cat /etc/fstab
will work, because fstab is indeed not a directory, but a file
good luck
–
palladium