| Summary: | how to migrate a client-server configuration | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Eatdirt <dirteat> |
| Component: | core | Assignee: | Anand Avati <aavati> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.1.2 | CC: | amarts, chrisw, gluster-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | fuse |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Eatdirt
2011-01-25 10:32:35 UTC
(In reply to comment #0) > Hi, > after having read the documentation and the migration pages; there is no > reference on how to migrate a client-server configuration 3.0.4 to the new > 3.1.2. > > As far as I can read, I cannot use the old volume file configuration. Anyway I > tried, and glusterfs segfaults. > > My old config files on 13 nodes are recap below, they were simple, efficient, > and I clearly do not intent to reconfigure my whole cluster; so I hope I can > import them in a easy way; which does not seem to be the case right now. > > Chris. Can you post the backtrace of your segfault? If you tried to use the same volfile and start glusterfsd and glusterfs client (without using glusterd/gluster cli) it should still work in theory. I'm interested to see what caused the segfault. Avati Bug timeout. We have clear documentation about migration now in our wiki. |