|Subject:||Re: xfs umount with i/o error hang/memory corruption|
|From:||Bob Mastors <bob.mastors@xxxxxxxxxxxxx>|
|Date:||Fri, 4 Apr 2014 13:47:28 -0600|
On Fri, Apr 4, 2014 at 12:50 PM, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> wrote:
Sorry, I don't think I was clear on the nature of the problem and it's wide ranging effects.
Using iscsi to access block storage on another server is the goal.
A failure on the other server is possible which could result in the iscsi initiator returning i/o errors to xfs.
The behavior that I would like from xfs is to put the filesystem in some kind of offline state
on an i/o error from the block device. Today xfs usually has this desirable behavior.
But there is a corner case were instead xfs hangs the entire server, forcing a hard reboot.
On a large file server with many filesystems using iscsi to talk to block storage on multiple
block servers, I would like the failure of a single block server to only impact the filesystems
that are dependent on the block server, and to not impact the other filesystems.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: xfs umount with i/o error hang/memory corruption, Stan Hoeppner|
|Next by Date:||Re: 10GB memorys occupied by XFS, Stan Hoeppner|
|Previous by Thread:||Re: xfs umount with i/o error hang/memory corruption, Stan Hoeppner|
|Next by Thread:||Re: xfs umount with i/o error hang/memory corruption, Dave Chinner|
|Indexes:||[Date] [Thread] [Top] [All Lists]|