xfs
[Top] [All Lists]

xfs_do_force_shutdown

To: xfs@xxxxxxxxxxx
Subject: xfs_do_force_shutdown
From: Kuo Hugo <tonytkdk@xxxxxxxxx>
Date: Tue, 19 Jul 2016 17:17:25 +0800
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=ul4sj6vUv+Z3P0TDfXC2gIcSofnxWDtx+odOEjIdOoY=; b=IJ4BXwhbhwdFi6SFIV4It2Q9fBUTGwk1WYzbiiTS5e/QZ9kib9sIoMLl3OSyWWwGiF qRLrpbK95ymiJ60B1EeEhc3jw0r93+zzWLpowk3PXUBaVkPDiSSzcULc4r9T501Ri1+1 QUcLMPtYIgUXYTFqAqSNF1vYy2RE5zeLfLVG/CwhtFJdPqAjVS5+AiWItK8pVvNlW5ih CcPegWT7mdAfCcli2rkoxgMBzMybr4oqWoSFpSSEPetHwYVt3Suw+Rf3t010AlvKXUKt +80fD1vo57hHx5SAFX6KUjB/3Gbr33Lf5t7PgVdtV4YUiQGBoJgBOOD8/MrnCGRAVCao 3lyw==
Hi Folks,Â

I got a question regarding to xfs_do_force_shutdown. The smartctl doesn't show any clue about disk bad. The device works properly again after remount. The xfs_repair complete to repair the device very quick and these's not too much suspecious.Â


* Is this a xfs level issue about dirty logs ?Â
* Is this HBA problem ?


```
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.330404] blk_update_request: I/O error, dev sdy, sector 3909224960
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.330650] XFS (sdy): metadata I/O error: block 0xe9020a00 ("xlog_iodone") error 5 numblks 64
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.330939] XFS (sdy): xfs_do_force_shutdown(0x2) called from line 1179 of file /build/linux-lts-vivid-whAhIw/linux-lts-vivid-3.19.0/fs/xfs/xfs_log.c. Return address = 0xffffffffc06a1d96
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.330973] XFS (sdy): xfs_log_force: error -5 returned.
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.330999] XFS (sdy): Log I/O Error Detected. Shutting down filesystem
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.331206] XFS (sdy): Please umount the filesystem and rectify the problem(s)
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.331443] Buffer I/O error on dev sdy, logical block 18, lost async page write
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.337098] Buffer I/O error on dev sdy, logical block 30523594, lost async page write
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.348492] Buffer I/O error on dev sdy, logical block 19, lost async page write
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.359941] Buffer I/O error on dev sdy, logical block 30523599, lost async page write
Jul 17 22:52:31 HBGTCOBSON02 kernel: [9291040.380649] XFS (sdy): xfs_log_force: error -5 returned.
Jul 17 22:52:59 HBGTCOBSON02 kernel: [9291069.111432] XFS (sdy): xfs_log_force: error -5 returned.
Jul 17 22:53:29 HBGTCOBSON02 kernel: [9291099.215252] XFS (sdy): xfs_log_force: error -5 returned.
Jul 17 22:53:33 HBGTCOBSON02 kernel: [9291102.517951] XFS (sdy): xfs_log_force: error -5 returned.
Jul 17 22:53:33 HBGTCOBSON02 kernel: [9291102.517981] XFS (sdy): xfs_log_force: error -5 returned.
Jul 17 22:53:33 HBGTCOBSON02 kernel: [9291102.518006] XFS (sdy): xfs_log_force: error -5 returned.
Jul 18 08:35:55 HBGTCOBSON02 kernel: [9326072.158898] XFS (sdy): Mounting V4 Filesystem
Jul 18 08:35:55 HBGTCOBSON02 kernel: [9326072.279516] XFS (sdy): Starting recovery (logdev: internal)
Jul 18 08:35:55 HBGTCOBSON02 kernel: [9326072.725549] XFS (sdy): Ending recovery (logdev: internal)
```

thanks // Hugo
<Prev in Thread] Current Thread [Next in Thread>