@takeseem unfortunately due to a bug in LP I cannot access the image.
Can you rename the image to use latin characters only and upload it
again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
在我们的线上aws ec2出现了这个问题，2天后机器突然重启了。
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To manage notifications about this bug go
may be after updated snapd will trige the bug.
bash # snap changes
ID Status Spawn Ready Summary
48 Error 2 days ago, at 13:34 UTC today at 03:28 UTC Auto-refresh snaps
"amazon-ssm-agent", "snapd", "core18"
49 Donetoday at 03:33 UTCtoday
** Changed in: snapd (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To manage
hi folks, when you provide logs here with SNAPD_DEBUG_HTTP=7 enabled,
please take care to remove sensitive information such as your macaroon
authorization, which may enable someone to login to your ubuntu one
account. For example, any line in the log such as:
X-Device-Authorization: Macaroon
** Attachment removed: "snapd log of telegram-desktop updating after 'stop
snapd'"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+attachment/5426441/+files/snapd%20log%20on%20telegram-desktop%20updating%20after%20restart%20snap.txt
--
You received this bug notification
** Attachment removed: "snapd log of telegram-desktop updating"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+attachment/5426434/+files/snapd%20log%20on%20telegram-telegram-desktop%20updating.txt
** Attachment removed: "snapd.log"
I believe #1831629 is also describing this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To manage notifications
Still happen on 20.10 in 2021. snapd is reducing lifespan of my SDD :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To
After the follow command it got updated. The log is attached.
sudo systemctl stop snapd
Warning: Stopping snapd.service, but it can still be activated by: snapd.socket
** Attachment added: "snapd log of telegram-desktop updating after 'stop snapd'"
It seems yes, downloads fine after I restart snap.
After today's restart, it hangs on the update again on downloading an update of
"telegram-desktop".
Log of `journalctl -u snapd` with SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7 is attached.
** Attachment added: "Log of `journalctl -u snapd` with
This still happens on 20.10.
Now I'm using a proxy for faster downloads, but snapd is still writing
too much to disk (~9MB/s disk writes while ~1.5MB/s downloads).
snapd from journalctl -u with SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7 is
attached.
** Attachment added: "snapd.log"
btw, this only happens when refreshing snaps, but not on installing a
new snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd
If it is stuck on 0% but still writing to the disk, then it's either
getting errors from the network or when starting a download, or
downloading the first chunks fails for some reason. In any case, it
would be useful to find out why. Specifically, as you noted restarting
snapd helps, which may
To stop this SSD killing, I ran `sudo systemctl stop snapd`. The daemon doesn't
stop (probably depends on `snapd.socket`).
But then I run `snap change 79` again and see that` core` is installed, and the
load percentage of `chromium` starts to update. The packets are installed in a
minute.
date
Пт 23 окт 2020 08:11:34 MSK
snap changes
ID Status Spawn Ready Summary
79 Doing today at 06:19 MSK - Автоматически обновить
пакеты "core", "chromium"
snap change 79
Status Spawn Ready Summary
Donetoday
Now I see. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To manage notifications about this bug go to:
It is visible, try running say:
snap install --no-wait spotify
The commands outputs a change number, then run, this periodically:
snap change
On my system it shows:
$ snap change 406
Status SpawnReadySummary
Donetoday at 13:13 CEST today at 13:13
Yes, "updating chromium" with 4Mb/s write non-stop without net
traffic...
I yesterday stop it with `sudo systemctl stop snapd`, `sudo kill -9 $(pgrep -fn
snapd)`. I don't know if it turned on again later due to the fact that I didn't
directly disable snapd.socket.
It seems that the Chromium
The message states that snapd is updating chromium.
Can you attach the output of `snap change 76` command?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very
The problem is still ongoing on 20.04. I have to open the console daily
and run the following commands, due to snapd starts to use my SSD non-
stop when I restart. This is faking as `updating Chromium`.
sudo kill -9 $ (pgrep -fn snapd)
sudo systemctl stop snapd
sudo systemctl stop snapd.socket
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
sudo pidstat -d -T ALL -p `pidof snapd` 5
18时51分41秒 UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
18时51分46秒 0 4326 0.00 7019.20 0.00 0 snapd
18时51分46秒 UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
18时51分51秒 0 4326 0.00
I am suffering the same issue. snapd writing at 2 MB/s for almost 5
straight days. I have poor internet connectivity. Most of the time
network monitor shows zero network activity, so snap is not "actually"
downloading anything.
$snap changes
ID Status Spawn Ready Summary
54
fnotifystat shows during snap refreshing chromium:
Total Open Close Read Write PID Process Pathname
53.2 15.7 15.7 21.90.0 1423 snapd
/var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/3e9f8cfc-6448-4ee5-a063-e6dca36cbd7b
48.5 15.7
Since disabling snapd service and re-enabling it a day later I've been
unable to reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high
One can see the file activity in more detail using:
sudo apt install fnotifystat
sudo fnotifystat
That will show exactly what is going on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Maciej I've re-enabled the snapd service and will report bag with the
results of those debug commands you've suggested when it starts heavy
disk usage again.
I'll add I've never seen such long, sustained and intense disk
access/thrashing apart from when doing large drive to drive backups. I
only
Unfortunately I cannot reproduce this behavior here.
There is obviously a measurable IO when snap is refreshed, but that is
expected, since a new revision needs to be downloaded (writes),
downloads could be retried (read to hash the files and then writes),
followed by the bookkeeping tasks (read
This issue has occurred on my clean 20.04 install. Completely thrashing
my SSD for about 40mins, stopping the service would just have it restart
a few seconds later. "journalctl --system -f -u snapd" didn't reveal
anything of interest. Restarting the OS didn't solve the issue. I've had
to disable
https://news.ycombinator.com/item?id=22972661 Doesn' t matter anymore as
people are removing this shit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high
This still happens on 20.04, could anyone tell me how to get some debug
logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd
What might be happening (would need DEBUG logs to know for sure) is that
the download gets interrupted, so snapd rehashes (-> reads) what's been
downloaded so far before continuing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can confirm this issue happens every time when snap is auto-refreshing a
snap (possibly have to refresh multiple snap at the same time to trigger
the issue) in background. If you show tasks of the current "Doing"
changes, you will see it's downloading something, e.g.: `snap tasks 348`
.
Done
Hi Zygmunt, can you have a look with my added info? @zyga
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To manage
Exactly the same issue, also inside China (mainland). When snapd using
~5M/s of write, `snap changes` is:
ID Status Spawn Ready Summary
347 Doing today at 16:37 HKT - Auto-refresh snaps
"", "wine-platform-runtime"
Disk write is done
Typo in #7: Disk write is *gone*, aka. 0M/s IO
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on 19.04 with snapd 2.39.3
To manage notifications
I see very high (constant disk LED on) on ubuntu 18.04 also. Have to
disable it since I never used it here in China, where snap download
speed is unusable.
** Changed in: snapd (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
This still happens to me on 19.10 when snapd performing auto refresh.
snapd version: 2.41+19.10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
Title:
snapd disk write usage very high on
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: snapd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
I don't know if there is any problem here, but I checked the contents of
the task and interrupted the task. The tasks are as follows:
lihe@system:~$ snap tasks 44
Status Spawn Ready Summary
Done3 days ago, at 09:44 CST 3 days ago, at 09:44 CST Ensure
Thank you for responding to my question, I ran this command and got the
following output
44 Doing 3 days ago, at 09:44 CST - Auto-refresh snap "redis-
desktop-manager"
** Attachment added: "Screenshot from 2019-08-08 13-07-07.png"
Hello
Can you please help us understand the issue. When you are observing disk
IO what is the output of "snap changes"?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
43 matches
Mail list logo
