Diff for "Tech/OCFS2"

Differences between revisions 2 and 3

Create file system
- Local

Update cluster ID for repository on the servers.

Log in one of the servers in the new server pool as root user, update cluster ID for the repository with command
```
# tunefs.ocfs2 --update-cluster-stack /dev/mapper/<device ID for repo>
```
If tunefs.ocfs2 fails with "tunefs.ocfs2: At least one journal has uncommitted changes.", run fsck.ocfs2 to fix first:
```
# fsck.ocfs2 /dev/mapper/<device ID for repo>
```

Verify that the cluster ID has changed with command

# mounted.ocfs2 -d

Example:

1) Check out existing ocfs2 devices
# mounted.ocfs2 -d
Device                                         Stack  Cluster           F  UUID                              Label
/dev/sdg                                       o2cb   c95f71342d824a7e  G  0004FB00000500003057206B0B83CFF4  OVS7206b0b83cff4
/dev/mapper/360a98000486e534d635a685358795331  o2cb   c95f71342d824a7e  G  0004FB00000500003057206B0B83CFF4  OVS7206b0b83cff4
/dev/sdl                                       o2cb   7bc709cf2125f5e2  G  0004FB00000500008794AFB671E38BC8  OVS_POOL_FILESYSTEM
/dev/mapper/360a98000486e58594b4a6853592f6e72  o2cb   7bc709cf2125f5e2  G  0004FB00000500008794AFB671E38BC8  OVS_POOL_FILESYSTEM

7bc709cf2125f5e2 is the new cluster ID, /dev/mapper/360a98000486e58594b4a6853592f6e72 is pool file system, /dev/mapper/360a98000486e534d635a685358795331 is the file system for repository.

2) update cluster ID
# tunefs.ocfs2 --update-cluster-stack /dev/mapper/360a98000486e534d635a685358795331
tunefs.ocfs2: At least one journal has uncommitted changes.  Run fsck.ocfs2 to replay all dirty journals while opening device "/dev/mapper/360a98000486e534d635a685358795331"

# fsck.ocfs2 /dev/mapper/360a98000486e534d635a685358795331
fsck.ocfs2 1.8.0
[RECOVER_CLUSTER_INFO] The running cluster is using the o2cb stack with the cluster name 2d34bc778036dc2c, but the filesystem is configured for the o2cb stack with the cluster name 4b7b1533526cc727.  Thus, fsck.ocfs2 cannot determine whether the filesystem is in use.  fsck.ocfs2 can reconfigure the filesystem to use the currently running cluster configuration.  DANGER: YOU MUST BE ABSOLUTELY SURE THAT NO OTHER NODE IS USING THIS FILESYSTEM BEFORE MODIFYING ITS CLUSTER CONFIGURATION.  Recover cluster configuration information the running cluster? <n> y
Checking OCFS2 filesystem in /dev/mapper/360a98000486e534d635a685358795331:
  Label:              OVSc339e8c5fc68c
  UUID:               0004FB0000050000373C339E8C5FC68C
  Number of blocks:   26214400
  Block size:         4096
  Number of clusters: 204800
  Cluster size:       524288
  Number of slots:    8

/dev/mapper/360a98000486e534d635a685358795331 wasn't cleanly unmounted by all nodes.  Attempting to replay the journals for nodes that didn't unmount cleanly
Checking each slot's journal.
Replaying slot 1's journal.
Slot 1's journal replayed successfully.

/dev/mapper/360a98000486e534d635a685358795331 is clean.  It will be checked after 20 additional mounts.
Slot 1's journal dirty flag removed

# tunefs.ocfs2 --update-cluster-stack /dev/mapper/360a98000486e534d635a685358795331
Updating on-disk cluster information to match the running cluster.
DANGER: YOU MUST BE ABSOLUTELY SURE THAT NO OTHER NODE IS USING THIS FILESYSTEM BEFORE MODIFYING ITS CLUSTER CONFIGURATION.
Update the on-disk cluster information? yes

3) Verifiy the cluster ID is changed.
# mounted.ocfs2 -d /dev/mapper/360a98000486e534d635a685358795331
Device                                         Stack  Cluster           F  UUID                              Label
/dev/mapper/360a98000486e534d635a685358795331  o2cb   7bc709cf2125f5e2  G  0004FB00000500003057206B0B83CFF4  OVS7206b0b83cff4

-  ⇤ ← Revision 2 as of 2013-07-31 20:38:45 → 
  Size: 3752
  Editor: frank
  Comment:
+   ← Revision 3 as of 2013-08-05 22:05:42 → ⇥
  Size: 3799
  Editor: frank
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+. Create file system
  * Local
    {{{
}}}