xfs_do_force_shutdown

xfs_do_force_shutdown

[Kuo Hugo]

[-- Attachment #1.1: Type: text/plain, Size: 2555 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 2964 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_do_force_shutdown

[Carlos Maiolino]

On Tue, Jul 19, 2016 at 05:17:25PM +0800, Kuo Hugo wrote:
>    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 ?
>    ```

It's certainly an I/O error, but why it happened needs further investigation. I
can't say what happened without looking on the remaining logs to see if is there
something else there. There are probably more errors from the block layer than
the one you pasted here, please, attach the complete log of the system where it
happened, dmesg and /var/log/messages files.

Also, the device might be working properly again, because you haven't tried to
read/write sector 3909224960, which is the sector that looks to have triggered
the errors you specified.

Also, what's the kernel version you are using? the amount of
"xfs_log_force: error -5 returned" messages, says it's a quite old kernel.


Cheers.

>    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

> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs


-- 
Carlos

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: xfs_do_force_shutdown

[Eric Sandeen]

On 7/19/16 2:17 AM, Kuo Hugo wrote:
> 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

The root cause here is that IO error from the block device.
Everything else is XFS reacting to that error; it does not
indicate an xfs bug.

-Eric

> 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
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs