![]() Therefore all the plexes of a volume are clean, no action is required.ģ. CLEAN : A plex is in a CLEAN state when it is known to contain a good copy (mirror) of the volume. EMPTY : When a volume is created and the plex isn’t initialized the plex is in an EMPTY state.Ģ. A log replay occurs when it becomes necessary to use logged parity and data.ġ. REPLAY : The volume is in a transient state as part of a log replay. NEEDSYNC : The volume will require a parity resyncronization operation the next time it is started.Ħ. SYNC : The volume is either undergoing a parity resyncronization or was having its parity resyncronization when the machine was rebooted.ĥ. If the volume is DISABLED, the parity can’t be guaranteed to be synchronized.Ĥ. ACTIVE : The volume has been started or was in use when the machine was rebooted. The raid-5 plex stripes are consistent.Ģ. CLEAN : The volume is not started and its parity is good. RAID-5 Volume States (Raid-5 have there own set of volume states )ġ. NEEDSYNC : The volume will require a resyncronization operation the next time it is started. If volume is DISABLED it was resyncing when machine was rebooted and the plexes need to be resyncronized.ĥ. If the volume is ENABLED, the plexes are being resyncronized. With read-writeback recovery, plex consistency is recovered by reading data blocks of one plex and writing the data to all other writable plexes. SYNC : The volume is either in read-writeback recovery mode(ENABLED) or was in this mode when the machine was rebooted(DISABLED). The kernel state is always DISABLED when the volume is EMPTY.Ĥ. EMPTY : The volume contents are not initialized. If the volume is DISABLED, the plexes cannot be guaranteed to be consistent, but will be consistent when the volume is started.ģ. ![]() CLEAN : The volume is not started (Kernel state DISABLED) and its plexes are synchronized.Ģ. This information is already available in internet in various formats, what I exactly tried here is just a consolidation, for quick reference.ġ. ![]() In this post, I made little effort to write all the possible Volume and Plex states so that it can be readily useful for others ( including me) for the day to day operations. ![]() While Troubleshooting Veritas Volume Manager, Understanding volume and plex states is key part to investigate about the current issue related to the Veritas Volumes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |