1 |
Thank Rich, |
2 |
|
3 |
It seems to be tty12 (console logging) - I think disabling it in |
4 |
syslog-ng will be easiest but will do some testing first. |
5 |
|
6 |
The recursive switch shows tty12 regularly ticking up. |
7 |
|
8 |
BillK |
9 |
|
10 |
|
11 |
On 17/2/20 10:13 am, Rich Freeman wrote: |
12 |
> On Sun, Feb 16, 2020 at 7:57 PM William Kenworthy <billk@×××××××××.au> wrote: |
13 |
>> 2 ~ # lxc-attach -n mail -- bash -c "df -h" |
14 |
>> none 492K 320K 172K 66% /dev |
15 |
>> du and ls -al do not give any clues, the host /dev is normal and all |
16 |
>> running lxc instances do it, but at different rates |
17 |
> Are you running ls -al from INSIDE the container? If you're running |
18 |
> it on the host you won't see anything because it is almost certainly |
19 |
> in a separate mount namespace, and so it is invisible from the host. |
20 |
> In particular, any files you see in rootdir/dev from the host are NOT |
21 |
> visible in the container, and vice-versa. |
22 |
> |
23 |
> I don't use lxc, but if I had to take a wild guess your /dev isn't |
24 |
> being properly initialized inside, and some typical device node is |
25 |
> being created as a regular file and stuff like "echo foo > /dev/null" |
26 |
> is actually writing to a real file there, filling up the tmpfs. |
27 |
> |
28 |
> Try: |
29 |
> lxc-attach -n mail -- bash -c "ls -l --recursive /dev" |
30 |
> |
31 |
> Or launch an interactive shell inside the container and just poke |
32 |
> around in there. I have no idea what the "lxc way" to launch a shell |
33 |
> is, but you can always use: |
34 |
> nsenter --target <pid> --all /bin/bash |
35 |
> (where <pid> is the pid on the host of a process inside the container) |
36 |
> |
37 |
> nsenter is part of util-linux |
38 |
> |