Storage

I experienced the following error on starting up a GPFS node in a cluster: unexpected token conflict in recovery: majType 1 minType 7 tokType Inode key F657ED5089ABDE89:00000000000FC191:0000000000000000 node 1 mode xw flags 0x0 seqNum 1141739 The resulting in the node in question asserting and other nodes remote asserting, making the cluster unstable. IBM states this is related to the token memory (TM) management which can lead to unexpected result when being exhausted....

At the University of Bristol, we are currently in the process of migrating from one storage vendor to another for our block storage requirements. This includes our Oracle databases running on Solaris 10. In an attempt to minimise downtime, a number of other changes were scheduled at the same time, including moving from Fibre Channel to iSCSI and moving file system from UFS to ZFS (this should start ringing alarm bells for many of you)....