Where are snaps saved
![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
2
down vote
favorite
I'm running Ubuntu 16.04. I have a few snaps installed. Looking in the system monitor it looks like there are several versions of each snap installed and that each version is consuming space on the hard drive.
Looking in my home folder it seems like there are just a few empty folders under the ~/snap
folder.
But then it seems like the binaries for each snap are actually located under /snap
.
So here are my three questions.
- What is the system monitor actually showing in terms of space used?
- What it
~/snap
used for? - What are the
/dev/loopX
files used for?
I know that there should be only one question in each post but in this case I think the questions are dependent on each other.
snap ubuntu-core
add a comment |Â
up vote
2
down vote
favorite
I'm running Ubuntu 16.04. I have a few snaps installed. Looking in the system monitor it looks like there are several versions of each snap installed and that each version is consuming space on the hard drive.
Looking in my home folder it seems like there are just a few empty folders under the ~/snap
folder.
But then it seems like the binaries for each snap are actually located under /snap
.
So here are my three questions.
- What is the system monitor actually showing in terms of space used?
- What it
~/snap
used for? - What are the
/dev/loopX
files used for?
I know that there should be only one question in each post but in this case I think the questions are dependent on each other.
snap ubuntu-core
1
/dev/loop* 'files' aren't using disk space but are virtual devices (everything has to be a file in *nix, this accomplishes this using minimal memory & ~no disk space). /snap/* is the actual location of data stored on disk (real files here and not virtual). For loop devices maybe look at en.wikipedia.org/wiki/Loop_device
â guiverc
Apr 18 at 6:21
2
Possible duplicate of askubuntu.com/questions/834093/â¦or it may be useful anyway
â guiverc
Apr 18 at 6:24
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm running Ubuntu 16.04. I have a few snaps installed. Looking in the system monitor it looks like there are several versions of each snap installed and that each version is consuming space on the hard drive.
Looking in my home folder it seems like there are just a few empty folders under the ~/snap
folder.
But then it seems like the binaries for each snap are actually located under /snap
.
So here are my three questions.
- What is the system monitor actually showing in terms of space used?
- What it
~/snap
used for? - What are the
/dev/loopX
files used for?
I know that there should be only one question in each post but in this case I think the questions are dependent on each other.
snap ubuntu-core
I'm running Ubuntu 16.04. I have a few snaps installed. Looking in the system monitor it looks like there are several versions of each snap installed and that each version is consuming space on the hard drive.
Looking in my home folder it seems like there are just a few empty folders under the ~/snap
folder.
But then it seems like the binaries for each snap are actually located under /snap
.
So here are my three questions.
- What is the system monitor actually showing in terms of space used?
- What it
~/snap
used for? - What are the
/dev/loopX
files used for?
I know that there should be only one question in each post but in this case I think the questions are dependent on each other.
snap ubuntu-core
snap ubuntu-core
edited Apr 30 at 14:32
guntbert
8,750123067
8,750123067
asked Apr 18 at 6:01
g3blv
15318
15318
1
/dev/loop* 'files' aren't using disk space but are virtual devices (everything has to be a file in *nix, this accomplishes this using minimal memory & ~no disk space). /snap/* is the actual location of data stored on disk (real files here and not virtual). For loop devices maybe look at en.wikipedia.org/wiki/Loop_device
â guiverc
Apr 18 at 6:21
2
Possible duplicate of askubuntu.com/questions/834093/â¦or it may be useful anyway
â guiverc
Apr 18 at 6:24
add a comment |Â
1
/dev/loop* 'files' aren't using disk space but are virtual devices (everything has to be a file in *nix, this accomplishes this using minimal memory & ~no disk space). /snap/* is the actual location of data stored on disk (real files here and not virtual). For loop devices maybe look at en.wikipedia.org/wiki/Loop_device
â guiverc
Apr 18 at 6:21
2
Possible duplicate of askubuntu.com/questions/834093/â¦or it may be useful anyway
â guiverc
Apr 18 at 6:24
1
1
/dev/loop* 'files' aren't using disk space but are virtual devices (everything has to be a file in *nix, this accomplishes this using minimal memory & ~no disk space). /snap/* is the actual location of data stored on disk (real files here and not virtual). For loop devices maybe look at en.wikipedia.org/wiki/Loop_device
â guiverc
Apr 18 at 6:21
/dev/loop* 'files' aren't using disk space but are virtual devices (everything has to be a file in *nix, this accomplishes this using minimal memory & ~no disk space). /snap/* is the actual location of data stored on disk (real files here and not virtual). For loop devices maybe look at en.wikipedia.org/wiki/Loop_device
â guiverc
Apr 18 at 6:21
2
2
Possible duplicate of askubuntu.com/questions/834093/â¦or it may be useful anyway
â guiverc
Apr 18 at 6:24
Possible duplicate of askubuntu.com/questions/834093/â¦or it may be useful anyway
â guiverc
Apr 18 at 6:24
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
- What is the system monitor actually showing in terms of space used?
Snaps are squashfs images that are mounted into place, which is what you're seeing there. They are presented as disks which are 100% full, since each image is only as large as necessary to hold its data.
- What it
~/snap
used for?
Snaps are (typically) confined, by default limited to a few areas when it comes to reading/writing. ~/snap
holds snaps' user data (e.g. config files, etc.) since they can't by default write to $HOME
.
- What are the
/dev/loopX
files used for?
Loop devices are what are used to make files accessible as a block device, such as when mounting the snap (squashfs) files. So when you install a snap, it's mounted, and a loop device is used. When a snap is updated, it keeps three revisions around (current and two old ones) in case you want to revert, so these old ones are using loop devices as well.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
- What is the system monitor actually showing in terms of space used?
Snaps are squashfs images that are mounted into place, which is what you're seeing there. They are presented as disks which are 100% full, since each image is only as large as necessary to hold its data.
- What it
~/snap
used for?
Snaps are (typically) confined, by default limited to a few areas when it comes to reading/writing. ~/snap
holds snaps' user data (e.g. config files, etc.) since they can't by default write to $HOME
.
- What are the
/dev/loopX
files used for?
Loop devices are what are used to make files accessible as a block device, such as when mounting the snap (squashfs) files. So when you install a snap, it's mounted, and a loop device is used. When a snap is updated, it keeps three revisions around (current and two old ones) in case you want to revert, so these old ones are using loop devices as well.
add a comment |Â
up vote
3
down vote
accepted
- What is the system monitor actually showing in terms of space used?
Snaps are squashfs images that are mounted into place, which is what you're seeing there. They are presented as disks which are 100% full, since each image is only as large as necessary to hold its data.
- What it
~/snap
used for?
Snaps are (typically) confined, by default limited to a few areas when it comes to reading/writing. ~/snap
holds snaps' user data (e.g. config files, etc.) since they can't by default write to $HOME
.
- What are the
/dev/loopX
files used for?
Loop devices are what are used to make files accessible as a block device, such as when mounting the snap (squashfs) files. So when you install a snap, it's mounted, and a loop device is used. When a snap is updated, it keeps three revisions around (current and two old ones) in case you want to revert, so these old ones are using loop devices as well.
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
- What is the system monitor actually showing in terms of space used?
Snaps are squashfs images that are mounted into place, which is what you're seeing there. They are presented as disks which are 100% full, since each image is only as large as necessary to hold its data.
- What it
~/snap
used for?
Snaps are (typically) confined, by default limited to a few areas when it comes to reading/writing. ~/snap
holds snaps' user data (e.g. config files, etc.) since they can't by default write to $HOME
.
- What are the
/dev/loopX
files used for?
Loop devices are what are used to make files accessible as a block device, such as when mounting the snap (squashfs) files. So when you install a snap, it's mounted, and a loop device is used. When a snap is updated, it keeps three revisions around (current and two old ones) in case you want to revert, so these old ones are using loop devices as well.
- What is the system monitor actually showing in terms of space used?
Snaps are squashfs images that are mounted into place, which is what you're seeing there. They are presented as disks which are 100% full, since each image is only as large as necessary to hold its data.
- What it
~/snap
used for?
Snaps are (typically) confined, by default limited to a few areas when it comes to reading/writing. ~/snap
holds snaps' user data (e.g. config files, etc.) since they can't by default write to $HOME
.
- What are the
/dev/loopX
files used for?
Loop devices are what are used to make files accessible as a block device, such as when mounting the snap (squashfs) files. So when you install a snap, it's mounted, and a loop device is used. When a snap is updated, it keeps three revisions around (current and two old ones) in case you want to revert, so these old ones are using loop devices as well.
edited Apr 20 at 22:28
answered Apr 18 at 14:22
![](https://i.stack.imgur.com/Zz9P7.jpg?s=32&g=1)
![](https://i.stack.imgur.com/Zz9P7.jpg?s=32&g=1)
Kyle
3,8981219
3,8981219
add a comment |Â
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%2f1026015%2fwhere-are-snaps-saved%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
1
/dev/loop* 'files' aren't using disk space but are virtual devices (everything has to be a file in *nix, this accomplishes this using minimal memory & ~no disk space). /snap/* is the actual location of data stored on disk (real files here and not virtual). For loop devices maybe look at en.wikipedia.org/wiki/Loop_device
â guiverc
Apr 18 at 6:21
2
Possible duplicate of askubuntu.com/questions/834093/â¦or it may be useful anyway
â guiverc
Apr 18 at 6:24