From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: "xfs_log_force: error 5 returned." for drive that was removed.
Date: Mon, 18 Apr 2016 20:54:29 +0200 [thread overview]
Message-ID: <20160418185429.GA6730@redhat.com> (raw)
In-Reply-To: <CACo5E_6fz+BV7prpyo35jzH2_dwgswZ4ZkZ26XP9czbdT3g6vw@mail.gmail.com>
On Sun, Apr 17, 2016 at 09:33:27AM -0500, Joe Wendt wrote:
> Hello! This may be a silly question or an interesting one...
> We had a drive fail in a production server, which spawned this error in
> the logs:
> XFS (sde1): xfs_log_force: error 5 returned.
> The dead array was lazy-unmounted, and the drive was hot-swapped, but
> when the RAID array was rebuilt, it came online as /dev/sdk instead of
> /dev/sde.
> Now /dev/sde1 doesn't exist in the system, but we still see this
> message every 30 seconds. I'm assuming a reboot will clear out whatever
> is still trying to access sde1, but I'm trying to avoid that if
> possible. Could someone point me in the direction of what XFS might
> still be trying to do with that device?
> lsof hasn't given me any clues. I can't run xfs_repair on a volume that
> isn't there. I haven't been able to find anything similar yet online.
> Any help would be greatly appreciated!
> Thanks,
> Joe
I believe this is the same problem being discussed in this thread:
XFS hung task in xfs_ail_push_all_sync() when unmounting FS after disk
failure/recovery.
Can you get a stack dump of the system (sysrq-t) and post it in some pastebin?
> _______________________________________________
> 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
next prev parent reply other threads:[~2016-04-18 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 14:33 "xfs_log_force: error 5 returned." for drive that was removed Joe Wendt
2016-04-18 18:54 ` Carlos Maiolino [this message]
2016-05-04 15:48 ` Joe Wendt
2016-05-05 10:05 ` Carlos Maiolino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160418185429.GA6730@redhat.com \
--to=cmaiolino@redhat.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.