FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Device-mapper Development

LinkBack Thread Tools
Old 06-17-2008, 03:56 AM
"Pradipmaya Maharana"
Default Problem with ALUA Support

Hi All,

I am facing a weird problem with RHEL.

Following is the setup I have:
- OS installed on diskless blades
- Blades connected to 2 controllers (so basically 2 paths)
- Trying for ALUA support
- For ALUA support I derived my code from Hannes check for explicit
ALUA support.
- Path_grouping_policy group_by_prio
- Features 1 "queue_if_no_path"
- No_path_retry 20

- When the failover happens, the standby paths are made active by
firing STPG. So far so good.
- When the failback happens, some how the standby paths are failed
(with messages Failing path 8:XX) even before the preferred controller
comes up.
- If the failure is show once, init_function is called again and thing
move fine, but in case this same error happens twice, the path is
marked as failure. In these situation as there are no paths, either
hangs or mounted as read-only.
- This does not happen immediately, it happens in hour or so when I Am
trying continuous failover failback with some gap in between 2

Why does the path fail in such scenarios?
How can this be prevented?

Please suggest.


dm-devel mailing list

Thread Tools

All times are GMT. The time now is 05:49 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org