Why are there multiple loop devices for the same snap?
Clash Royale CLAN TAG#URR8PPP up vote
3
down vote
favorite
I used lsblk to check connected devices, when I found that there are a total of 3 loop devices for the same snap "core", with revision numbers.
loop1 7:1 0 81.6M 1 loop /snap/core/4110
loop2 7:2 0 81.7M 1 loop /snap/core/4017
loop0 7:0 0 81.3M 1 loop /snap/core/3887
On checking the mount directory of snaps, this is what I get:
drwxr-xr-x 24 root root 321 Jan 22 13:17 3887
drwxr-xr-x 24 root root 321 Feb 6 20:48 4017
drwxr-xr-x 24 root root 321 Feb 20 22:37 4110
lrwxrwxrwx 1 root root 4 Feb 23 19:31 current -> 4110
and snap list shows this:
core 16-2.31.1 4110 canonical core
Why is snapd not removing the old versions of snap core? Is it a normal behavior, or is there any way to remove this if this is not supposed to happen? I'm using Ubuntu 16.04.
16.04 mount snap loop-device
edited Mar 4 at 9:11
muru
130k19274467
asked Mar 4 at 7:56
Apurv
184
add a comment |Â
up vote
3
down vote
favorite
I used lsblk to check connected devices, when I found that there are a total of 3 loop devices for the same snap "core", with revision numbers.
loop1 7:1 0 81.6M 1 loop /snap/core/4110
loop2 7:2 0 81.7M 1 loop /snap/core/4017
loop0 7:0 0 81.3M 1 loop /snap/core/3887
On checking the mount directory of snaps, this is what I get:
drwxr-xr-x 24 root root 321 Jan 22 13:17 3887
drwxr-xr-x 24 root root 321 Feb 6 20:48 4017
drwxr-xr-x 24 root root 321 Feb 20 22:37 4110
lrwxrwxrwx 1 root root 4 Feb 23 19:31 current -> 4110
and snap list shows this:
core 16-2.31.1 4110 canonical core
Why is snapd not removing the old versions of snap core? Is it a normal behavior, or is there any way to remove this if this is not supposed to happen? I'm using Ubuntu 16.04.
16.04 mount snap loop-device
edited Mar 4 at 9:11
muru
130k19274467
asked Mar 4 at 7:56
Apurv
184
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I used lsblk to check connected devices, when I found that there are a total of 3 loop devices for the same snap "core", with revision numbers.
loop1 7:1 0 81.6M 1 loop /snap/core/4110
loop2 7:2 0 81.7M 1 loop /snap/core/4017
loop0 7:0 0 81.3M 1 loop /snap/core/3887
On checking the mount directory of snaps, this is what I get:
drwxr-xr-x 24 root root 321 Jan 22 13:17 3887
drwxr-xr-x 24 root root 321 Feb 6 20:48 4017
drwxr-xr-x 24 root root 321 Feb 20 22:37 4110
lrwxrwxrwx 1 root root 4 Feb 23 19:31 current -> 4110
and snap list shows this:
core 16-2.31.1 4110 canonical core
Why is snapd not removing the old versions of snap core? Is it a normal behavior, or is there any way to remove this if this is not supposed to happen? I'm using Ubuntu 16.04.
16.04 mount snap loop-device
edited Mar 4 at 9:11
muru
130k19274467
asked Mar 4 at 7:56
Apurv
184
I used lsblk to check connected devices, when I found that there are a total of 3 loop devices for the same snap "core", with revision numbers.
loop1 7:1 0 81.6M 1 loop /snap/core/4110
loop2 7:2 0 81.7M 1 loop /snap/core/4017
loop0 7:0 0 81.3M 1 loop /snap/core/3887
On checking the mount directory of snaps, this is what I get:
drwxr-xr-x 24 root root 321 Jan 22 13:17 3887
drwxr-xr-x 24 root root 321 Feb 6 20:48 4017
drwxr-xr-x 24 root root 321 Feb 20 22:37 4110
lrwxrwxrwx 1 root root 4 Feb 23 19:31 current -> 4110
and snap list shows this:
core 16-2.31.1 4110 canonical core
Why is snapd not removing the old versions of snap core? Is it a normal behavior, or is there any way to remove this if this is not supposed to happen? I'm using Ubuntu 16.04.
16.04 mount snap loop-device
16.04 mount snap loop-device
edited Mar 4 at 9:11
muru
130k19274467
asked Mar 4 at 7:56
Apurv
184
edited Mar 4 at 9:11
muru
130k19274467
asked Mar 4 at 7:56
Apurv
184
edited Mar 4 at 9:11
muru
130k19274467
edited Mar 4 at 9:11
muru
130k19274467
edited Mar 4 at 9:11
muru
130k19274467
130k19274467
asked Mar 4 at 7:56
Apurv
184
asked Mar 4 at 7:56
Apurv
184
asked Mar 4 at 7:56
Apurv
184
184
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
In speaking with Ubuntu developers, the current default is to keep three prior versions of a snap so that you can roll-back to a prior version if needed. This default setting is not configurable.
You can use the command snap remove --revision=<an old one> snapname to remove an older revision of a snap.
They are considering whether to have only the current snap mounted as a loop filesystem, but I don't know the status of that.
answered Apr 9 at 21:05
j1mc
325511
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
In speaking with Ubuntu developers, the current default is to keep three prior versions of a snap so that you can roll-back to a prior version if needed. This default setting is not configurable.
You can use the command snap remove --revision=<an old one> snapname to remove an older revision of a snap.
They are considering whether to have only the current snap mounted as a loop filesystem, but I don't know the status of that.
answered Apr 9 at 21:05
j1mc
325511
add a comment |Â
up vote
1
down vote
accepted
In speaking with Ubuntu developers, the current default is to keep three prior versions of a snap so that you can roll-back to a prior version if needed. This default setting is not configurable.
You can use the command snap remove --revision=<an old one> snapname to remove an older revision of a snap.
They are considering whether to have only the current snap mounted as a loop filesystem, but I don't know the status of that.
answered Apr 9 at 21:05
j1mc
325511
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
In speaking with Ubuntu developers, the current default is to keep three prior versions of a snap so that you can roll-back to a prior version if needed. This default setting is not configurable.
You can use the command snap remove --revision=<an old one> snapname to remove an older revision of a snap.
They are considering whether to have only the current snap mounted as a loop filesystem, but I don't know the status of that.
answered Apr 9 at 21:05
j1mc
325511
In speaking with Ubuntu developers, the current default is to keep three prior versions of a snap so that you can roll-back to a prior version if needed. This default setting is not configurable.
You can use the command snap remove --revision=<an old one> snapname to remove an older revision of a snap.
They are considering whether to have only the current snap mounted as a loop filesystem, but I don't know the status of that.
answered Apr 9 at 21:05
j1mc
325511
answered Apr 9 at 21:05
j1mc
325511
answered Apr 9 at 21:05
j1mc
325511
answered Apr 9 at 21:05
j1mc
325511
325511
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%2f1011728%2fwhy-are-there-multiple-loop-devices-for-the-same-snap%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