network interfaces brought down before fsync to iSCSI target completes
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
network interfaces brought down before fsync to iSCSI target completes
######
OS : CentOS7
Kernel : 4.9.37 #######
Issue
#######
On graceful shutdown of Centos 7 , Network target is stopped before we sync the filesystems and block devices thereby leading to the following error
Synching filesystem and block devices - timed out
>> INFO: task <> blocked for more than 120 seconds.
>> Not tainted <> #1
>> kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. #######
Log
#######
<<<<<log>>>>>>
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Shutting down.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd-shutdown[1]: Syncing filesystems and block devices.
Dec 02 13:04:06 NTNX-10-44-10-134-FAVM kernel: connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4294725853, last ping 4294731264, now 4294736384
02 13:03:55 NTNX-10-44-10-134-FAVM systemd[1]: Stopped target Network.
Dec 02 13:03:55 NTNX-10-44-10-134-FAVM systemd[1]: Stopping Network.
Dec 02 13:03:55 NTNX-10-44-10-134-FAVM systemd[1]: Stopping LSB: Bring up/down networking...
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM network[2736]: Shutting down interface eth0: [ OK ]
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM network[2736]: Shutting down loopback interface: [ OK ]
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Stopped LSB: Bring up/down networking.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Stopping IPv4 firewall with iptables....
.
.
.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Starting Shutdown.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Reached target Final Step.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Starting Final Step.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Starting Power-Off...
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd[1]: Shutting down.
Dec 02 13:03:56 NTNX-10-44-10-134-FAVM systemd-shutdown[1]: Syncing filesystems and block devices.
Dec 02 13:04:06 NTNX-10-44-10-134-FAVM kernel: connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4294725853, last ping 4294731264, now 4294736384
Dec 02 13:04:06 NTNX-10-44-10-134-FAVM kernel: connection1:0: detected conn error (1022)
Synching filesystem and block devices - timed out
>> INFO: task <> blocked for more than 120 seconds.
>> Not tainted <> #1
>> kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<<<<<log>>>>>>
#######
Comments
#######
Is it a bug ? Why would network interfaces brought down before fsync completes and unmount complete on a graceful shutdown ? What is the best way to resolve it ?
Current kernel version is 4.9.37 and OS is CentOS7
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.