My root disk is full.(opensuse 13.1) I only found out while doing updates and it kept telling me the operation was aborted by user. I have less than 100mb free after I deleted a whole bunch of tmp files and logs.
The system error-ed on shutdown before I figured out what was wrong, so I am afraid to use it until I can fix the space issue.
I have one disk spit: with about 50gb root disk and /home/kilbert about 250 gb
I would like to split another 50gb off the /home/kilbert and add it to the / partition.
I have /home backed up elsewhere. So no worries there.
I have other drives mounted for data.
What’s the safest way to expand the root partition and keep my system running without reinstalling?
What are you running on / to use up that space? Maybe some very large databases???
Generally you need no more then 20-30 gig for the root partition. If you are not running a process that is using the space then you may have a serious error somewhere causing extreme error files.
First step in resizing is to back up everything.
Next from a live DVD/CD adjust the size of the partition.
Next extend the File System on the partition you increased
details depend on the file system used
But if the problem is from error logs then you need to find and fix the real problem since no amount of space will be enough
> I have one disk spit: with about 50gb root disk and /home/kilbert about
> 250 gb
> I would like to split another 50gb off the /home/kilbert and add it to
> the / partition.
Wait, 50 GB should be ample enough. Is your root of type btrfs? You get
automatic snapshots made with snapper, and they take space that
accumulates. You have to remove some of them.
So first verify that.
If it is not btrfs, then you have to do a size verification of each
directory, and find out which is fullest. I use ‘mc’ in a terminal, if
it is installed. If not, you can not install anything at this stage, so
us “du” instead. I don’t remember offhand which options will be more
appropriate, so you will have to read the man page and try… I think
you need -c, -h, -s, and -x
su -
du -chsx /*
If then you find you still can not delete anything more, create a
directory in home for “/home/usr_share”, copy there (not move yet)
everything from “/usr/share”, then rename it to “/usr/share.old”, and
finally symlink “/home/usr_share” to “/usr/share”.
If machine continues working, remove “/usr/share.old”.
My system is unstable now crashed a few times typing this so I am shortening it drastically.
I managed to get 500mb free, and found the culprit: plexmediaserver is using 25+gb (it keep crashing while calculating in both dolphin and terminal du -chsx /* while in the /var directory- the same directory the plexmediaserver is)
While I try to fix that issue, how can I extend the root dir. of my system in the interim while I try to figure out why the plex is killing my system? can I use the suselive cd? I am afraid I cannot grab anything else right now.
I tried rescue- it gave me a command prompt, I tried install, and it did not recognise my installation.
fdisk-l
cut out other junk not needed.
Disk /dev/sde: 320.1 GB, 320072933376 bytes, 625142448 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
Disk label type: dos
Disk identifier: 0x08000000
Device Boot Start End Blocks Id System
/dev/sde1 * 2048 105048063 52523008 83 Linux
/dev/sde2 105048064 113434623 4193280 82 Linux swap / Solaris
/dev/sde3 113434624 625141759 255853568 83 Linux
On 2014-05-21 01:46, kilbert wrote:
>
> Thanks guys.
>
> My system is unstable now crashed a few times typing this so I am
> shortening it drastically.
>
> I managed to get 500mb free, and found the culprit: plexmediaserver is
> using 25+gb (it keep crashing while calculating in both dolphin and
> terminal du -chsx /* while in the /var directory- the same directory the
> plexmediaserver is)
>
> While I try to fix that issue, how can I extend the root dir.
Don’t.
Just delete that plex thing directories, and rename that program so that
it can not run. Then boot your system and uninstall it.
Then, if you really want to use that plex thing again, dedicate a disk
to it - not the Linux root filesystem.
> of my
> system in the interim while I try to figure out why the plex is killing
> my system? can I use the suselive cd?
Yes, you can.
> I tried rescue- it gave me a command prompt,
That’s right, that’s what it does. You type commands on it
> I tried install, and it did
> not recognise my installation.
Install? That would destroy your current installation.
This does seem the best option. I will delete the directory and uninstall the program.
Thanks
How would I go about installing the plex program on a different drive (its in a repository).
On Wed, 21 May 2014 00:26:02 +0000, kilbert wrote:
> This does seem the best option. I will delete the directory and
> uninstall the program.
> Thanks How would I go about installing the plex program on a different
> drive (its in a repository).
It’ll probably be a configuration option in the program - the software
itself isn’t 25 GB, but the data it’s generating is, so you need to look
at the configuration options and see if you can point it somewhere else.
On 2014-05-21 02:26, kilbert wrote:
>
> This does seem the best option. I will delete the directory and
> uninstall the program.
> Thanks
> How would I go about installing the plex program on a different drive
> (its in a repository).
For that you need to ask someone that knows that program reasonably
well. I just learnt about it in the wikipedia enough to answer you…
(If whatever is on that directory is important to you, then
don’t delete it, but move somewhere else)
I know that it is somekind of multimedia server/client thing. Probably
it stores thousands of movie streams somewhere, or songs, or whatever.
Such a thing needs dedicated space, hundreds of gigabytes for it alone,
not a section of a 50 GB root partition.
I suggest asking in the multimedia forum here, with a subject tittle
about “plex”. But I guess you either configure it so that it writes to a
directory of your choice, and if that is not possible because the
destination storage is hard coded, then you mount a partition/disk in
that directory and be done with.
And reading the above, it looks as if that program behaves very strange. It even looks as if it is run “as root”. When run as a normal user, it would not (be able to) store so much data in the wrong place. It would store it in that users home directory, or (as others suggest) in a place configurable by the user.
Turns out this is normal for a media program, some users state their database has grown to 200+gb
PLex devs suggest 100gb for /, 50gb for /opt and 700gb for /var as Plex resides there with all it’s metadata.
Looks like this is all by design.
My puny 320 gb drive is woefully undersized for this application.
For anyone reading this with this issue, plex .bif indexing files are the culprit. 30 gb of these files were what was filling up my drive. plex total was about 38gb.
Bad design if you can not specify where you want the files to go. As stated if you really feel you need the program add another disk with one large partition on it. Mount that partition at the directory where he program stores the data and be sure that the mount is in /etc/fstab. Then instead of writing a bunch of stuff to root it will go to the new drive and that can be as large as yo can afford to add.
>
>Turns out this is normal for a media program, some users state their
>database has grown to 200+gb
>PLex devs suggest 100gb for /, 50gb for /opt and 700gb for /var as Plex
>resides there with all it’s metadata.
>Looks like this is all by design.
>My puny 320 gb drive is woefully undersized for this application.
>
>For anyone reading this with this issue, plex .bif indexing files are
>the culprit. 30 gb of these files were what was filling up my drive.
>plex total was about 38gb.
Spewing that kind of GB in those directories??? Evil by design.
On 2014-05-27 08:17, josephkk wrote:
> On Wed, 21 May 2014 10:46:01 GMT, kilbert <> wrote:
>> For anyone reading this with this issue, plex .bif indexing files are
>> the culprit. 30 gb of these files were what was filling up my drive.
>> plex total was about 38gb.
>
> Spewing that kind of GB in those directories??? Evil by design.
>
> ?-)
Nope.
For instance, mysql stores databases under “/var/lib/mysql/”, so what
plex does in “/var” is absolutely normal. It is a database.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
That is why I have told (configured if you want) MySQL to put it elsewhere (it does so by using symlinks btw).
But this product seems not to be configurable in this subject and that it what people loath here.
On 2014-05-27 14:06, hcvv wrote:
>
> robin_listas;2645714 Wrote:
>>
>>
>> For instance, mysql stores databases under “/var/lib/mysql/”, so what
>> plex does in “/var” is absolutely normal. It is a database.
> That is why I have told (configured if you want) MySQL to put it
> elsewhere (it does so by using symlinks btw).
> But this product seems not to be configurable in this subject and that
> it what people loath here.
I assume that you can use symlinks or bind mounts as with any other
application in Linux. I don’t have the intention to install it in order
to check it, but I don’t see a reason why its data directories can not
be redirected.
The only objection is that you can not do it by configuration of the
application, apparently, but that’s the case with many applications.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
>On 2014-05-27 08:17, josephkk wrote:
>> On Wed, 21 May 2014 10:46:01 GMT, kilbert <> wrote:
>
>>> For anyone reading this with this issue, plex .bif indexing files are
>>> the culprit. 30 gb of these files were what was filling up my drive.
>>> plex total was about 38gb.
>>
>> Spewing that kind of GB in those directories??? Evil by design.
>>
>> ?-)
>
>Nope.
>
>For instance, mysql stores databases under “/var/lib/mysql/”, so what
>plex does in “/var” is absolutely normal. It is a database.
Evil, but not anything a smart admin can’t handle with some links to more
appropriate places (other mounted volumes).
I’m having a similar problem - the 30G system partition is filling up - but I’m getting odd numbers. If I go to the properties of each folder in the home directory (hidden & non-hidden) I can count up about 1.5G worth of files. But folder properties & du both report over 3G so I’m not finding something. du is also having trouble accessing some directories.
du: cannot access ‘/proc/3482/task/3482/ns/net’: No such file or directory
du: cannot access ‘/proc/3482/task/3482/ns/uts’: No such file or directory
du: cannot access ‘/proc/3482/task/3482/ns/ipc’: No such file or directory
du: cannot access ‘/proc/3482/ns/net’: No such file or directory
du: cannot access ‘/proc/3482/ns/uts’: No such file or directory
du: cannot access ‘/proc/3482/ns/ipc’: No such file or directory
du: cannot access ‘/proc/4601/task/4601/fd/4’: No such file or directory
du: cannot access ‘/proc/4601/task/4601/fdinfo/4’: No such file or directory
du: cannot access ‘/proc/4601/fd/4’: No such file or directory
du: cannot access ‘/proc/4601/fdinfo/4’: No such file or directory
0 /proc
6.0M /root
du: cannot access ‘/run/user/1000/gvfs’: Permission denied
I’m running OpenSuse 12.3 Linux 3.7.10-1.32-desktop with KDE 4.10.5. Is there some other utility I should run instead?
Some directories like /proc are virtual ie do not live on the disk so should not be considered in calculating disk usage. In Linux like Unix eveything is a file so /proc is a window into all the process. /dev is a window into attached hardware /sys is a window into the system process
Check your logs unless you are running some program that may have huge databases then it is probably over large log files and that means that there is a problem somewhere that is repeatedly getting logged.
You probably should start a new thread since your problems is unlikely the same as the original poster
