search for: aad9

...dev/sda1 * mount /dev/sda1 /a * This will fail with kernel back traces and corruption reported * xfs_repair will report the log vs superblock UUID mismatch I mentioned Here are the volume settings: # gluster volume info adminvm Volume Name: adminvm Type: Replicate Volume ID: de655913-aad9-4e17-bac4-ff0ad9c28223 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: 172.23.254.181:/data/brick_adminvm_slot2 Brick2: 172.23.254.182:/data/brick_adminvm_slot2 Brick3: 172.23.254.183:/data/brick_adminvm_slot2 Options Reconfigured: storage.owner-gid...

...fail with kernel back traces and corruption reported > * xfs_repair will report the log vs superblock UUID mismatch I > mentioned > ? > Here are the volume settings: > ? > # gluster volume info adminvm > ? > Volume Name: adminvm > Type: Replicate > Volume ID: de655913-aad9-4e17-bac4-ff0ad9c28223 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 3 = 3 > Transport-type: tcp > Bricks: > Brick1: 172.23.254.181:/data/brick_adminvm_slot2 > Brick2: 172.23.254.182:/data/brick_adminvm_slot2 > Brick3: 172.23.254.183:/data/brick_adminvm_slot2...

...dev/sda1 * mount /dev/sda1 /a * This will fail with kernel back traces and corruption reported * xfs_repair will report the log vs superblock UUID mismatch I mentioned Here are the volume settings: # gluster volume info adminvm Volume Name: adminvm Type: Replicate Volume ID: de655913-aad9-4e17-bac4-ff0ad9c28223 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: 172.23.254.181:/data/brick_adminvm_slot2 Brick2: 172.23.254.182:/data/brick_adminvm_slot2 Brick3: 172.23.254.183:/data/brick_adminvm_slot2 Options Reconfigured: storage.owner-gid...