Compiled Linux-Kernel, crach, 40GB disk full, temp folder?












1















As i was compilenig a Linux-Kernel on KDE neon GNU/Linux (upgrade to ubuntu 18.04/Linux-Kernel 4.20.5) the computer crashed and now my Linux pratition (40GB) is full.
Where is the directory where the gcc compiler stores files while its compiling?
I already cleand the partition with BleachBit but still 30GB data on the disk, it sould be around 9GB.



With a greeting





Thanks for the quick response.
I fetched the k4dirstat an tryd to install...



CMake Error at /usr/share/cmake-



3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find Gettext (missing: GETTEXT_MSGMERGE_EXECUTABLE
GETTEXT_MSGFMT_EXECUTABLE)


README:




Overview



See the
wiki.



Building



First install Qt 5 and KDE Framework
5 headers. On Debian and its derivatives it can
be done with:



libkf5coreaddons-dev   libkf5i18n-dev libkf5xmlgui-dev
libkf5doctools-dev libkf5kio-dev ```

Then run [cmake](http://www.cmake.org):

cmake -DCMAKE_INSTALL_PREFIX=/path/where/to/install
make install











share|improve this question

























  • You can easily find out what’s occupying space using ncdu or a similar tool. Since you have KDE, perhaps KDirStat.

    – Daniel B
    Jan 28 at 17:44











  • OK, i got it.Its the: /usr/src/linux-4.20.5 directory, got 16.xxGB date in it.

    – Bandoler
    Jan 28 at 18:47











  • If you have another suitable drive/partition elsewhere, you can do all your building there and just transfer the finished result to your root partition. It might take a few tweaks to tell the build apparatus to use another location, but it will prevent you from running out of space on your root partition.

    – Joe
    Feb 4 at 18:41











  • fixed with the command: make clean

    – Bandoler
    Feb 6 at 10:21
















1















As i was compilenig a Linux-Kernel on KDE neon GNU/Linux (upgrade to ubuntu 18.04/Linux-Kernel 4.20.5) the computer crashed and now my Linux pratition (40GB) is full.
Where is the directory where the gcc compiler stores files while its compiling?
I already cleand the partition with BleachBit but still 30GB data on the disk, it sould be around 9GB.



With a greeting





Thanks for the quick response.
I fetched the k4dirstat an tryd to install...



CMake Error at /usr/share/cmake-



3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find Gettext (missing: GETTEXT_MSGMERGE_EXECUTABLE
GETTEXT_MSGFMT_EXECUTABLE)


README:




Overview



See the
wiki.



Building



First install Qt 5 and KDE Framework
5 headers. On Debian and its derivatives it can
be done with:



libkf5coreaddons-dev   libkf5i18n-dev libkf5xmlgui-dev
libkf5doctools-dev libkf5kio-dev ```

Then run [cmake](http://www.cmake.org):

cmake -DCMAKE_INSTALL_PREFIX=/path/where/to/install
make install











share|improve this question

























  • You can easily find out what’s occupying space using ncdu or a similar tool. Since you have KDE, perhaps KDirStat.

    – Daniel B
    Jan 28 at 17:44











  • OK, i got it.Its the: /usr/src/linux-4.20.5 directory, got 16.xxGB date in it.

    – Bandoler
    Jan 28 at 18:47











  • If you have another suitable drive/partition elsewhere, you can do all your building there and just transfer the finished result to your root partition. It might take a few tweaks to tell the build apparatus to use another location, but it will prevent you from running out of space on your root partition.

    – Joe
    Feb 4 at 18:41











  • fixed with the command: make clean

    – Bandoler
    Feb 6 at 10:21














1












1








1








As i was compilenig a Linux-Kernel on KDE neon GNU/Linux (upgrade to ubuntu 18.04/Linux-Kernel 4.20.5) the computer crashed and now my Linux pratition (40GB) is full.
Where is the directory where the gcc compiler stores files while its compiling?
I already cleand the partition with BleachBit but still 30GB data on the disk, it sould be around 9GB.



With a greeting





Thanks for the quick response.
I fetched the k4dirstat an tryd to install...



CMake Error at /usr/share/cmake-



3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find Gettext (missing: GETTEXT_MSGMERGE_EXECUTABLE
GETTEXT_MSGFMT_EXECUTABLE)


README:




Overview



See the
wiki.



Building



First install Qt 5 and KDE Framework
5 headers. On Debian and its derivatives it can
be done with:



libkf5coreaddons-dev   libkf5i18n-dev libkf5xmlgui-dev
libkf5doctools-dev libkf5kio-dev ```

Then run [cmake](http://www.cmake.org):

cmake -DCMAKE_INSTALL_PREFIX=/path/where/to/install
make install











share|improve this question
















As i was compilenig a Linux-Kernel on KDE neon GNU/Linux (upgrade to ubuntu 18.04/Linux-Kernel 4.20.5) the computer crashed and now my Linux pratition (40GB) is full.
Where is the directory where the gcc compiler stores files while its compiling?
I already cleand the partition with BleachBit but still 30GB data on the disk, it sould be around 9GB.



With a greeting





Thanks for the quick response.
I fetched the k4dirstat an tryd to install...



CMake Error at /usr/share/cmake-



3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find Gettext (missing: GETTEXT_MSGMERGE_EXECUTABLE
GETTEXT_MSGFMT_EXECUTABLE)


README:




Overview



See the
wiki.



Building



First install Qt 5 and KDE Framework
5 headers. On Debian and its derivatives it can
be done with:



libkf5coreaddons-dev   libkf5i18n-dev libkf5xmlgui-dev
libkf5doctools-dev libkf5kio-dev ```

Then run [cmake](http://www.cmake.org):

cmake -DCMAKE_INSTALL_PREFIX=/path/where/to/install
make install








linux kernel compile






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 28 at 19:09









Mokubai

58k16139157




58k16139157










asked Jan 28 at 17:40









BandolerBandoler

65




65













  • You can easily find out what’s occupying space using ncdu or a similar tool. Since you have KDE, perhaps KDirStat.

    – Daniel B
    Jan 28 at 17:44











  • OK, i got it.Its the: /usr/src/linux-4.20.5 directory, got 16.xxGB date in it.

    – Bandoler
    Jan 28 at 18:47











  • If you have another suitable drive/partition elsewhere, you can do all your building there and just transfer the finished result to your root partition. It might take a few tweaks to tell the build apparatus to use another location, but it will prevent you from running out of space on your root partition.

    – Joe
    Feb 4 at 18:41











  • fixed with the command: make clean

    – Bandoler
    Feb 6 at 10:21



















  • You can easily find out what’s occupying space using ncdu or a similar tool. Since you have KDE, perhaps KDirStat.

    – Daniel B
    Jan 28 at 17:44











  • OK, i got it.Its the: /usr/src/linux-4.20.5 directory, got 16.xxGB date in it.

    – Bandoler
    Jan 28 at 18:47











  • If you have another suitable drive/partition elsewhere, you can do all your building there and just transfer the finished result to your root partition. It might take a few tweaks to tell the build apparatus to use another location, but it will prevent you from running out of space on your root partition.

    – Joe
    Feb 4 at 18:41











  • fixed with the command: make clean

    – Bandoler
    Feb 6 at 10:21

















You can easily find out what’s occupying space using ncdu or a similar tool. Since you have KDE, perhaps KDirStat.

– Daniel B
Jan 28 at 17:44





You can easily find out what’s occupying space using ncdu or a similar tool. Since you have KDE, perhaps KDirStat.

– Daniel B
Jan 28 at 17:44













OK, i got it.Its the: /usr/src/linux-4.20.5 directory, got 16.xxGB date in it.

– Bandoler
Jan 28 at 18:47





OK, i got it.Its the: /usr/src/linux-4.20.5 directory, got 16.xxGB date in it.

– Bandoler
Jan 28 at 18:47













If you have another suitable drive/partition elsewhere, you can do all your building there and just transfer the finished result to your root partition. It might take a few tweaks to tell the build apparatus to use another location, but it will prevent you from running out of space on your root partition.

– Joe
Feb 4 at 18:41





If you have another suitable drive/partition elsewhere, you can do all your building there and just transfer the finished result to your root partition. It might take a few tweaks to tell the build apparatus to use another location, but it will prevent you from running out of space on your root partition.

– Joe
Feb 4 at 18:41













fixed with the command: make clean

– Bandoler
Feb 6 at 10:21





fixed with the command: make clean

– Bandoler
Feb 6 at 10:21










1 Answer
1






active

oldest

votes


















0














A more generic solution would be to look for large directories and files.



du -hc / | sort -rh | less


will list disk usage of your root partition in human readable format with totals and then sort it into descending order putting the output into a pager so you can see it instead of having it all fly by. All the big stuff will be displayed first.



If there are a lot of restricted directories, this can be run with sudo so it can see into them as well.



If you need to run it on all of root or another large partition/file tree, it may take awhile to complete. The sort can't put anything out until it has all the input from du.



If you get a lot of error messages about not being able to examine restricted directories as a regular user, you can use



du -hc / 2>/dev/null | sort -rh | less


to suppress the error messages.






share|improve this answer
























  • THX, i fixed it with the command: make clean

    – Bandoler
    Feb 6 at 10:20











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399356%2fcompiled-linux-kernel-crach-40gb-disk-full-temp-folder%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














A more generic solution would be to look for large directories and files.



du -hc / | sort -rh | less


will list disk usage of your root partition in human readable format with totals and then sort it into descending order putting the output into a pager so you can see it instead of having it all fly by. All the big stuff will be displayed first.



If there are a lot of restricted directories, this can be run with sudo so it can see into them as well.



If you need to run it on all of root or another large partition/file tree, it may take awhile to complete. The sort can't put anything out until it has all the input from du.



If you get a lot of error messages about not being able to examine restricted directories as a regular user, you can use



du -hc / 2>/dev/null | sort -rh | less


to suppress the error messages.






share|improve this answer
























  • THX, i fixed it with the command: make clean

    – Bandoler
    Feb 6 at 10:20
















0














A more generic solution would be to look for large directories and files.



du -hc / | sort -rh | less


will list disk usage of your root partition in human readable format with totals and then sort it into descending order putting the output into a pager so you can see it instead of having it all fly by. All the big stuff will be displayed first.



If there are a lot of restricted directories, this can be run with sudo so it can see into them as well.



If you need to run it on all of root or another large partition/file tree, it may take awhile to complete. The sort can't put anything out until it has all the input from du.



If you get a lot of error messages about not being able to examine restricted directories as a regular user, you can use



du -hc / 2>/dev/null | sort -rh | less


to suppress the error messages.






share|improve this answer
























  • THX, i fixed it with the command: make clean

    – Bandoler
    Feb 6 at 10:20














0












0








0







A more generic solution would be to look for large directories and files.



du -hc / | sort -rh | less


will list disk usage of your root partition in human readable format with totals and then sort it into descending order putting the output into a pager so you can see it instead of having it all fly by. All the big stuff will be displayed first.



If there are a lot of restricted directories, this can be run with sudo so it can see into them as well.



If you need to run it on all of root or another large partition/file tree, it may take awhile to complete. The sort can't put anything out until it has all the input from du.



If you get a lot of error messages about not being able to examine restricted directories as a regular user, you can use



du -hc / 2>/dev/null | sort -rh | less


to suppress the error messages.






share|improve this answer













A more generic solution would be to look for large directories and files.



du -hc / | sort -rh | less


will list disk usage of your root partition in human readable format with totals and then sort it into descending order putting the output into a pager so you can see it instead of having it all fly by. All the big stuff will be displayed first.



If there are a lot of restricted directories, this can be run with sudo so it can see into them as well.



If you need to run it on all of root or another large partition/file tree, it may take awhile to complete. The sort can't put anything out until it has all the input from du.



If you get a lot of error messages about not being able to examine restricted directories as a regular user, you can use



du -hc / 2>/dev/null | sort -rh | less


to suppress the error messages.







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 4 at 19:04









JoeJoe

503613




503613













  • THX, i fixed it with the command: make clean

    – Bandoler
    Feb 6 at 10:20



















  • THX, i fixed it with the command: make clean

    – Bandoler
    Feb 6 at 10:20

















THX, i fixed it with the command: make clean

– Bandoler
Feb 6 at 10:20





THX, i fixed it with the command: make clean

– Bandoler
Feb 6 at 10:20


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399356%2fcompiled-linux-kernel-crach-40gb-disk-full-temp-folder%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Сан-Квентин

Алькесар

Josef Freinademetz