Haven't seen it in a few days. I'll reboot and see if I can reproduce
it. It usually happens after rebooting the host, when launching new
containers or existing ones would autostart.
Info you requested. I think the /usr/share/lxc/... might have been a red
herring. I'm exclusively using LXD on
@stforshee I'll uncomment the debugfs mount in my
/usr/share/lxc/config/ubuntu.common.conf (putting it back the way it
was), reboot, and see if I can reproduce it again.
My juju-lxd profile shows:
name: juju-lxd
config:
boot.autostart: "true"
security.nesting: "true"
description: ""
devices:
Interesting. I removed the /sys/kernel/debug mount and containers seem
to start up just fine:
c@mawhrin-skel:~$ grep kernel/debug /usr/share/lxc/config/ubuntu.common.conf
# lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0
c@mawhrin-skel:~$ lxc launch ubuntu-trusty t2
This is the config from the container that had the issue this morning:
c@mawhrin-skel:~/omnibus-layers$ lxc config show
juju-145a3177-d1c0-4974-89f6-feaebb3ca87d-machine-0
name: juju-145a3177-d1c0-4974-89f6-feaebb3ca87d-machine-0
profiles:
- default
- juju-lxd
config:
user.juju-model-uuid:
FWIW I've observed the bug outside of Juju. Launching a trusty
container, sshd did not start until I remounted debug on the host. The
main reason it's been observed with juju is, Juju tries to SSH into the
instance right after cloud-init, but upstart in the container isn't
starting sshd so
I also confirmed that the mountall error message was duplicated every
time I restarted the machine-0 container -- until remounting on the
host.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I'm using lxd with zfs block storage on xenial, and having issues with
trusty containers. I've witnessed this problem when trying to bootstrap
as well as after rebooting the host and a container failed to start.
In the latter case, the container that failed to start was the
Nope, still burnin. A fresh boot it doesn't seem too bad, but this just
happened, coming off of standby (that seems to worsen it):
Wed Aug 6 18:28:53 CEST 2014
193 Load_Cycle_Count0x0012 089 089 000Old_age Always
- 113151
Wed Aug 6 18:29:54 CEST 2014
193
The rate certainly seems slower than before with latest 3.16 kernel
(Linux cloudsong 3.16.0-031600-generic #201408031935 SMP Sun Aug 3
23:36:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux).
Is this looking more like a normal cycle pattern, or still more load
cycles than there should be?
Installed the BIOS update:
root@cloudsong:~# dmidecode -s bios-version sudo dmidecode -s
bios-release-date
G2ETA1WW (2.61 )
04/22/2014
Still burning load cycles on battery power:
root@cloudsong:~# while true;
do
date
smartctl -a /dev/sda | grep Load_Cycle
sleep 60
done
Fri Aug 1
Public bug reported:
When running my Thinkpad x230 on battery, the Load_Cycle_Count increases
at a high rate: about 10-15 load cycles per minute. I discovered this
issue in a quiet room, where I could hear the clicks (or death rattle,
as I've come to think of them).
The following commands will
** Changed in: linux (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1316284
Title:
[HP Probook 4540s] Load/Unload Cycle Count
Status in
I am reopening this because:
1. My harddrive has already been cooked by this bug and I'll probably
have to buy a new one. I set up an upstart script to run the hdparm
command, but it seems to need it run more often than at just startup.
Check it out:
193 Load_Cycle_Count0x0012 090
I'm also seeing a ridiculous load cycle count increase on my thinkpad
x230 running xubuntu 14.04. I got suspicious when I could hear the faint
click in a quiet room, and it reminded me of the issue from several
years back.
193 Load_Cycle_Count0x0012 094 094 000Old_age Always
-
This stopped the runaway load cycles as a workaround:
sudo hdparm -B 254 /dev/sda
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
15 matches
Mail list logo
