BTRFS device loop2 - using crc32c colored as a warning, why?

[WiredRacing]

Jan  5 13:23:43 urEDC root: Checksum:           crc32c
Jan  5 13:23:43 urEDC root: Number of devices:  1
Jan  5 13:23:43 urEDC root: Devices:
Jan  5 13:23:43 urEDC root:    ID        SIZE  PATH
Jan  5 13:23:43 urEDC root:     1    20.00GiB  /mnt/cache_vms/system/docker/docker.img
Jan  5 13:23:43 urEDC root: 
Jan  5 13:23:43 urEDC kernel: loop2: detected capacity change from 0 to 41943040
Jan  5 13:23:43 urEDC kernel: BTRFS: device fsid 81d0017e-f318-4ab7-bb7c-d50e60034e4a devid 1 transid 6 /dev/loop2 scanned by mount (30483)
Jan  5 13:23:43 urEDC kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm
Jan  5 13:23:43 urEDC kernel: BTRFS info (device loop2): using free space tree
Jan  5 13:23:43 urEDC kernel: BTRFS info (device loop2): enabling ssd optimizations
Jan  5 13:23:43 urEDC kernel: BTRFS info (device loop2): checking UUID tree
Jan  5 13:23:43 urEDC emhttpd: shcmd (360): /etc/rc.d/rc.docker start
Jan  5 13:23:43 urEDC root: starting dockerd ...
Jan  5 13:23:43 urEDC avahi-daemon[30404]: Server startup complete. Host name is urEDC.local. Local service cookie is 3658841664.
Jan  5 13:23:44 urEDC rc.docker: created network macvlan br0 with subnets: 192.168.1.0/24; 
Jan  5 13:23:44 urEDC root: Error response from daemon: failed to allocate secondary ip address (server:192.168.2.0): Address already in use

So the top line "Checksum: crc32c", the "using crc32c (crc32c-intel) checksum algorithm" and the last line (secondary IP address) are all yellow. I understand why the last line would be. What are the other lines trying to tell me? Everything else seems fine (though I looked at the log because my server did seem to 'drop' from the network earlier after trying to start up an array with a new drive). 

 

fwiw, other posts around "loop 2" suggest docker.img corruption, so I gave repairing that a shot (disable, delete, restart, reinstall apps) but these lines still show in yellow. No other problem lines. Docker starts fine.

[itimpi]

The color coding just looks for certain strings in the log entries.    I am guessing that ‘checksum’ and ‘error’ are strings being looked for.    The lines look like perfectly normal information messages.

 

i notice that you are using macvlan networking for docker.   If you experience instability you might want to consider switching to ipvlan as mentioned in the Release Notes.

[WiredRacing]

Ahh okay good. It did seem to just be an 'info' line. And thanks for the heads-up re: networking setting. Instability within the docker containers themselves or within unraid (i.e. my 'dropped network' experience)?

[itimpi]

11 minutes ago, WiredRacing said:

Instability within the docker containers themselves or within unraid (i.e. my 'dropped network' experience)?

Unraid.   If you start getting macvlan crashes it will eventually crash the whole server.