You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
In 1800.4.0 (and 1828.1.0), accessing a CIFS mount will cause a kernel panic. This was working properly in 1745.7.0. First noticed in stable and tried alpha channel, same problem persists. Fresh install of 1745 works properly.
Container Linux Version
Both 1800.4.0 and 1828.1.0
$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1828.1.0
VERSION_ID=1828.1.0
BUILD_ID=2018-07-24-2257
PRETTY_NAME="Container Linux by CoreOS 1828.1.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
Environment
Windows 2016 Standard Edition - Hyper-V
Version 1607 (OS Build 14393.339)
4GB RAM w/dynamic memory, 8 cores, external network
SMB shares are exported from the Windows Server. These are NTFS- and ReFS-backed shares in a Storage Spaces mirrored environment.
//192.168.10.22/S/ on /mnt/data type cifs (rw,relatime,vers=default,cache=strict,username=docker-data,domain=,uid=500,forceuid,gid=500,forcegid,addr=192.168.10.22,file_mode=0777,dir_mode=0777,soft,nounix,serverino,mapposix,nobrl,mfsymlinks,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
Thanks for the report. It seems this was introduced by coreos/linux@748144f in 4.14.55. A revert of that commit is already queued for 4.14.59.
1828.1.0 is on the beta channel, which also ships the 4.14 kernel. The alpha channel ships 4.17 and should not have this problem. Could you test the latest alpha and confirm?
Yes, the alpha release fixes this problem. I was able to test this by creating very large files using dd as well as start and run docker containers with docker-compose.
Issue Report
Bug
In 1800.4.0 (and 1828.1.0), accessing a CIFS mount will cause a kernel panic. This was working properly in 1745.7.0. First noticed in stable and tried alpha channel, same problem persists. Fresh install of 1745 works properly.
Container Linux Version
Both 1800.4.0 and 1828.1.0
Environment
Windows 2016 Standard Edition - Hyper-V
Version 1607 (OS Build 14393.339)
4GB RAM w/dynamic memory, 8 cores, external network
SMB shares are exported from the Windows Server. These are NTFS- and ReFS-backed shares in a Storage Spaces mirrored environment.
localhost ~ # mount.cifs -V
mount.cifs version: 6.8
localhost ~ # mount | grep cifs
fstab
Expected Behavior
Normal access to CIFS shares for reading/writing.
Actual Behavior
Running docker-compose up to start containers results in immediate kernel panic. Writing a large file causes a kernel panic as well.
Reproduction Steps
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.080528 s, 130 MB/s
kernel panic
Other Information
From line 14990 of attached journalctl
coreos.log
The text was updated successfully, but these errors were encountered: