NVMe partitions, dev/loop partitions?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
3
down vote
favorite
I'm using an NVMe drive, but I don't understand what all these dev/loops- partitions are. Should I do something about it, or is this perfectly normal?
df -h
Filsystem Størrelse Brukt Tilgj. Bruk% Montert pÃÂ¥
udev 3,9G 0 3,9G 0% /dev
tmpfs 786M 3,4M 782M 1% /run
/dev/nvme0n1p6 78G 26G 49G 35% /
tmpfs 3,9G 43M 3,8G 2% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/loop0 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop1 22M 22M 0 100% /snap/gnome-logs/31
/dev/loop3 6,0M 6,0M 0 100% /snap/communitheme/246
/dev/loop2 13M 13M 0 100% /snap/gnome-characters/69
/dev/loop6 28M 28M 0 100% /snap/ohmygiraffe/3
/dev/loop5 163M 163M 0 100% /snap/spotify/13
/dev/loop8 141M 141M 0 100% /snap/gnome-3-26-1604/62
/dev/loop7 13M 13M 0 100% /snap/gnome-characters/86
/dev/loop9 87M 87M 0 100% /snap/core/4571
/dev/loop12 87M 87M 0 100% /snap/core/4650
/dev/loop10 94M 94M 0 100% /snap/slack/6
/dev/loop11 6,0M 6,0M 0 100% /snap/communitheme/285
/dev/loop13 141M 141M 0 100% /snap/gnome-3-26-1604/59
/dev/loop15 221M 221M 0 100% /snap/pycharm-educational/6
/dev/loop14 21M 21M 0 100% /snap/gnome-logs/25
/dev/loop16 2,4M 2,4M 0 100% /snap/gnome-calculator/167
/dev/loop17 129M 129M 0 100% /snap/auryo/13
/dev/loop18 1,7M 1,7M 0 100% /snap/gnome-calculator/154
/dev/loop19 87M 87M 0 100% /snap/core/4486
/dev/nvme0n1p1 256M 32M 225M 13% /boot/efi
tmpfs 786M 16K 786M 1% /run/user/120
tmpfs 786M 72K 786M 1% /run/user/1000
/dev/loop20 6,0M 6,0M 0 100% /snap/communitheme/306
/dev/loop4 218M 218M 0 100% /snap/pycharm-educational/7
partitions nvme
add a comment |Â
up vote
3
down vote
favorite
I'm using an NVMe drive, but I don't understand what all these dev/loops- partitions are. Should I do something about it, or is this perfectly normal?
df -h
Filsystem Størrelse Brukt Tilgj. Bruk% Montert pÃÂ¥
udev 3,9G 0 3,9G 0% /dev
tmpfs 786M 3,4M 782M 1% /run
/dev/nvme0n1p6 78G 26G 49G 35% /
tmpfs 3,9G 43M 3,8G 2% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/loop0 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop1 22M 22M 0 100% /snap/gnome-logs/31
/dev/loop3 6,0M 6,0M 0 100% /snap/communitheme/246
/dev/loop2 13M 13M 0 100% /snap/gnome-characters/69
/dev/loop6 28M 28M 0 100% /snap/ohmygiraffe/3
/dev/loop5 163M 163M 0 100% /snap/spotify/13
/dev/loop8 141M 141M 0 100% /snap/gnome-3-26-1604/62
/dev/loop7 13M 13M 0 100% /snap/gnome-characters/86
/dev/loop9 87M 87M 0 100% /snap/core/4571
/dev/loop12 87M 87M 0 100% /snap/core/4650
/dev/loop10 94M 94M 0 100% /snap/slack/6
/dev/loop11 6,0M 6,0M 0 100% /snap/communitheme/285
/dev/loop13 141M 141M 0 100% /snap/gnome-3-26-1604/59
/dev/loop15 221M 221M 0 100% /snap/pycharm-educational/6
/dev/loop14 21M 21M 0 100% /snap/gnome-logs/25
/dev/loop16 2,4M 2,4M 0 100% /snap/gnome-calculator/167
/dev/loop17 129M 129M 0 100% /snap/auryo/13
/dev/loop18 1,7M 1,7M 0 100% /snap/gnome-calculator/154
/dev/loop19 87M 87M 0 100% /snap/core/4486
/dev/nvme0n1p1 256M 32M 225M 13% /boot/efi
tmpfs 786M 16K 786M 1% /run/user/120
tmpfs 786M 72K 786M 1% /run/user/1000
/dev/loop20 6,0M 6,0M 0 100% /snap/communitheme/306
/dev/loop4 218M 218M 0 100% /snap/pycharm-educational/7
partitions nvme
Please do not post pictures of text and post text as text and format it accordingly.
â Thomas
May 26 at 11:06
Can you copy/paste the text you want to show, instead of posting an image of a window of a program with that text inside.
â mikewhatever
May 26 at 11:08
Sorry, will do this in my next questions.
â Mr. Wilhelm
May 26 at 11:10
Welcome to AskUbuntu. Please do not change the title of your questions to include word's like[Solved]
, mark the answers which where useful for you as accepted by clicking the checkmark beside them. Thank you.
â Videonauth
May 26 at 11:34
Suggest takingNVMe
out of the title because it has nothing to do with thesnap
loop devices.
â WinEunuuchs2Unix
May 26 at 20:09
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm using an NVMe drive, but I don't understand what all these dev/loops- partitions are. Should I do something about it, or is this perfectly normal?
df -h
Filsystem Størrelse Brukt Tilgj. Bruk% Montert pÃÂ¥
udev 3,9G 0 3,9G 0% /dev
tmpfs 786M 3,4M 782M 1% /run
/dev/nvme0n1p6 78G 26G 49G 35% /
tmpfs 3,9G 43M 3,8G 2% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/loop0 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop1 22M 22M 0 100% /snap/gnome-logs/31
/dev/loop3 6,0M 6,0M 0 100% /snap/communitheme/246
/dev/loop2 13M 13M 0 100% /snap/gnome-characters/69
/dev/loop6 28M 28M 0 100% /snap/ohmygiraffe/3
/dev/loop5 163M 163M 0 100% /snap/spotify/13
/dev/loop8 141M 141M 0 100% /snap/gnome-3-26-1604/62
/dev/loop7 13M 13M 0 100% /snap/gnome-characters/86
/dev/loop9 87M 87M 0 100% /snap/core/4571
/dev/loop12 87M 87M 0 100% /snap/core/4650
/dev/loop10 94M 94M 0 100% /snap/slack/6
/dev/loop11 6,0M 6,0M 0 100% /snap/communitheme/285
/dev/loop13 141M 141M 0 100% /snap/gnome-3-26-1604/59
/dev/loop15 221M 221M 0 100% /snap/pycharm-educational/6
/dev/loop14 21M 21M 0 100% /snap/gnome-logs/25
/dev/loop16 2,4M 2,4M 0 100% /snap/gnome-calculator/167
/dev/loop17 129M 129M 0 100% /snap/auryo/13
/dev/loop18 1,7M 1,7M 0 100% /snap/gnome-calculator/154
/dev/loop19 87M 87M 0 100% /snap/core/4486
/dev/nvme0n1p1 256M 32M 225M 13% /boot/efi
tmpfs 786M 16K 786M 1% /run/user/120
tmpfs 786M 72K 786M 1% /run/user/1000
/dev/loop20 6,0M 6,0M 0 100% /snap/communitheme/306
/dev/loop4 218M 218M 0 100% /snap/pycharm-educational/7
partitions nvme
I'm using an NVMe drive, but I don't understand what all these dev/loops- partitions are. Should I do something about it, or is this perfectly normal?
df -h
Filsystem Størrelse Brukt Tilgj. Bruk% Montert pÃÂ¥
udev 3,9G 0 3,9G 0% /dev
tmpfs 786M 3,4M 782M 1% /run
/dev/nvme0n1p6 78G 26G 49G 35% /
tmpfs 3,9G 43M 3,8G 2% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/loop0 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop1 22M 22M 0 100% /snap/gnome-logs/31
/dev/loop3 6,0M 6,0M 0 100% /snap/communitheme/246
/dev/loop2 13M 13M 0 100% /snap/gnome-characters/69
/dev/loop6 28M 28M 0 100% /snap/ohmygiraffe/3
/dev/loop5 163M 163M 0 100% /snap/spotify/13
/dev/loop8 141M 141M 0 100% /snap/gnome-3-26-1604/62
/dev/loop7 13M 13M 0 100% /snap/gnome-characters/86
/dev/loop9 87M 87M 0 100% /snap/core/4571
/dev/loop12 87M 87M 0 100% /snap/core/4650
/dev/loop10 94M 94M 0 100% /snap/slack/6
/dev/loop11 6,0M 6,0M 0 100% /snap/communitheme/285
/dev/loop13 141M 141M 0 100% /snap/gnome-3-26-1604/59
/dev/loop15 221M 221M 0 100% /snap/pycharm-educational/6
/dev/loop14 21M 21M 0 100% /snap/gnome-logs/25
/dev/loop16 2,4M 2,4M 0 100% /snap/gnome-calculator/167
/dev/loop17 129M 129M 0 100% /snap/auryo/13
/dev/loop18 1,7M 1,7M 0 100% /snap/gnome-calculator/154
/dev/loop19 87M 87M 0 100% /snap/core/4486
/dev/nvme0n1p1 256M 32M 225M 13% /boot/efi
tmpfs 786M 16K 786M 1% /run/user/120
tmpfs 786M 72K 786M 1% /run/user/1000
/dev/loop20 6,0M 6,0M 0 100% /snap/communitheme/306
/dev/loop4 218M 218M 0 100% /snap/pycharm-educational/7
partitions nvme
edited May 26 at 11:30
asked May 26 at 11:02
Mr. Wilhelm
235
235
Please do not post pictures of text and post text as text and format it accordingly.
â Thomas
May 26 at 11:06
Can you copy/paste the text you want to show, instead of posting an image of a window of a program with that text inside.
â mikewhatever
May 26 at 11:08
Sorry, will do this in my next questions.
â Mr. Wilhelm
May 26 at 11:10
Welcome to AskUbuntu. Please do not change the title of your questions to include word's like[Solved]
, mark the answers which where useful for you as accepted by clicking the checkmark beside them. Thank you.
â Videonauth
May 26 at 11:34
Suggest takingNVMe
out of the title because it has nothing to do with thesnap
loop devices.
â WinEunuuchs2Unix
May 26 at 20:09
add a comment |Â
Please do not post pictures of text and post text as text and format it accordingly.
â Thomas
May 26 at 11:06
Can you copy/paste the text you want to show, instead of posting an image of a window of a program with that text inside.
â mikewhatever
May 26 at 11:08
Sorry, will do this in my next questions.
â Mr. Wilhelm
May 26 at 11:10
Welcome to AskUbuntu. Please do not change the title of your questions to include word's like[Solved]
, mark the answers which where useful for you as accepted by clicking the checkmark beside them. Thank you.
â Videonauth
May 26 at 11:34
Suggest takingNVMe
out of the title because it has nothing to do with thesnap
loop devices.
â WinEunuuchs2Unix
May 26 at 20:09
Please do not post pictures of text and post text as text and format it accordingly.
â Thomas
May 26 at 11:06
Please do not post pictures of text and post text as text and format it accordingly.
â Thomas
May 26 at 11:06
Can you copy/paste the text you want to show, instead of posting an image of a window of a program with that text inside.
â mikewhatever
May 26 at 11:08
Can you copy/paste the text you want to show, instead of posting an image of a window of a program with that text inside.
â mikewhatever
May 26 at 11:08
Sorry, will do this in my next questions.
â Mr. Wilhelm
May 26 at 11:10
Sorry, will do this in my next questions.
â Mr. Wilhelm
May 26 at 11:10
Welcome to AskUbuntu. Please do not change the title of your questions to include word's like
[Solved]
, mark the answers which where useful for you as accepted by clicking the checkmark beside them. Thank you.â Videonauth
May 26 at 11:34
Welcome to AskUbuntu. Please do not change the title of your questions to include word's like
[Solved]
, mark the answers which where useful for you as accepted by clicking the checkmark beside them. Thank you.â Videonauth
May 26 at 11:34
Suggest taking
NVMe
out of the title because it has nothing to do with the snap
loop devices.â WinEunuuchs2Unix
May 26 at 20:09
Suggest taking
NVMe
out of the title because it has nothing to do with the snap
loop devices.â WinEunuuchs2Unix
May 26 at 20:09
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
These are from snap packages. You have several of your packages installed using snap
(which happens by default in ubuntu 18.04). This is normal and aside from removing those packages and installing them without snap you can't (or at least shouldn't) do anything against them.
Update: To clarify in regard to your question in comment, these are not exactly partitions but files that contain a filesystem inside and that are mounted to the respective location. That way the package creator can package up a whole application in a single file but the OS using the application can access all the files as it normally would. The concept used here are so called loop
mounts.
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
These are from snap packages. You have several of your packages installed using snap
(which happens by default in ubuntu 18.04). This is normal and aside from removing those packages and installing them without snap you can't (or at least shouldn't) do anything against them.
Update: To clarify in regard to your question in comment, these are not exactly partitions but files that contain a filesystem inside and that are mounted to the respective location. That way the package creator can package up a whole application in a single file but the OS using the application can access all the files as it normally would. The concept used here are so called loop
mounts.
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
add a comment |Â
up vote
0
down vote
accepted
These are from snap packages. You have several of your packages installed using snap
(which happens by default in ubuntu 18.04). This is normal and aside from removing those packages and installing them without snap you can't (or at least shouldn't) do anything against them.
Update: To clarify in regard to your question in comment, these are not exactly partitions but files that contain a filesystem inside and that are mounted to the respective location. That way the package creator can package up a whole application in a single file but the OS using the application can access all the files as it normally would. The concept used here are so called loop
mounts.
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
These are from snap packages. You have several of your packages installed using snap
(which happens by default in ubuntu 18.04). This is normal and aside from removing those packages and installing them without snap you can't (or at least shouldn't) do anything against them.
Update: To clarify in regard to your question in comment, these are not exactly partitions but files that contain a filesystem inside and that are mounted to the respective location. That way the package creator can package up a whole application in a single file but the OS using the application can access all the files as it normally would. The concept used here are so called loop
mounts.
These are from snap packages. You have several of your packages installed using snap
(which happens by default in ubuntu 18.04). This is normal and aside from removing those packages and installing them without snap you can't (or at least shouldn't) do anything against them.
Update: To clarify in regard to your question in comment, these are not exactly partitions but files that contain a filesystem inside and that are mounted to the respective location. That way the package creator can package up a whole application in a single file but the OS using the application can access all the files as it normally would. The concept used here are so called loop
mounts.
edited May 26 at 11:28
answered May 26 at 11:18
![](https://i.stack.imgur.com/k9JBf.jpg?s=32&g=1)
![](https://i.stack.imgur.com/k9JBf.jpg?s=32&g=1)
Lienhart Woitok
808211
808211
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
add a comment |Â
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Thank you for your answer. Maybe I should check out how snaps work because I find it a bit strange how it would create a partition for a program. Maybe its a way of virtualization? Will do some research now, but thanks again
â Mr. Wilhelm
May 26 at 11:23
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
Huh, clever Well, ok - I will let them be :)
â Mr. Wilhelm
May 26 at 11:33
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1040555%2fnvme-partitions-dev-loop-partitions%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Please do not post pictures of text and post text as text and format it accordingly.
â Thomas
May 26 at 11:06
Can you copy/paste the text you want to show, instead of posting an image of a window of a program with that text inside.
â mikewhatever
May 26 at 11:08
Sorry, will do this in my next questions.
â Mr. Wilhelm
May 26 at 11:10
Welcome to AskUbuntu. Please do not change the title of your questions to include word's like
[Solved]
, mark the answers which where useful for you as accepted by clicking the checkmark beside them. Thank you.â Videonauth
May 26 at 11:34
Suggest taking
NVMe
out of the title because it has nothing to do with thesnap
loop devices.â WinEunuuchs2Unix
May 26 at 20:09