[lxc-users] Args for lxd init via script

[Fajar A. Nugraha]

On Mon, May 22, 2017 at 1:41 PM, gunnar.wagner <gunnar.wagner at netcologne.de>
wrote:

>
>
> On 5/22/2017 2:35 PM, Fajar A. Nugraha wrote:
>
> On Mon, May 22, 2017 at 1:09 PM, gunnar.wagner <
> gunnar.wagner at netcologne.de> wrote:
>
>>
>> On 5/22/2017 11:55 AM, Fajar A. Nugraha wrote:
>>
>>> subvolume with btrfs does not provide correct df.
>>> zfs dataset provide correct df.
>>>
>>
>> isn't    btrfs subvolume usage /path/to/subvolume    the tool to get the
>> correct usage data?
>
>
> The requirement was that "df on the container must return the correct
> output" w.r.t. size and usage.
>
>
> yes, I saw that. Just thought as long as you can get reliable usage data
> one wouldn't mind the particular tool all too much.
>
>

It's kinda similar when people were reading CPU and memory usage. With
cgroups (which is how lxc limits and account resource usage), the correct
place to look was /sys/fs/cgroups. Yet people (and tools they use, like
htop) continue to look at "traditional" places (e.g. /proc/cpuinfo,
/proc/meminfo, etc). And people complain because "top" gives "incorrect"
result inside a container. Thus lxcfs was created to satisfy that
requirement.

-- 
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20170522/019688ee/attachment.html>