To briefly add a useful note to the noise ;)
In general, you should re-yaim (or manually run the DPM schema update
script if you don't like yaim) your DPM head after any update, just in
case. Schema updates are a little more common in the 1.8.x series,
partly because of the large number of features that keep being
integrated, but they're all simple additions of columns to tables and
so should be cheap and fast to apply.
Sam
On 1 June 2012 21:37, Mark Slater <[log in to unmask]> wrote:
> Hi again,
>
> Please ignore the noise - a simple re-yaim and all is well!
>
> Thanks,
>
> Mark
>
> On 01/06/2012 19:34, Mark Slater wrote:
>>
>> Hi All,
>>
>> Today we shifted all our storage on to our new 10gig kit which seemed to
>> to go OK: I powered off the SE head node and then the pool nodes after that
>> before installing the cards and switching over the network. The networking
>> seems fine but after bringing up the SE head node I got a strange error:
>>
>> 06/01 19:24:19.626 31925 dpm_getpoolconf: getting existing disk pool
>> configuration from the DB
>> 06/01 19:24:20.394 31925 dpm_getpoolconf: POOL DPM001 DEFSIZE 200.00M
>> 06/01 19:24:20.397 31925 dpm_list_fs_entry: mysql_query error: Unknown
>> column 'WEIGHT' in 'field list'
>>
>>
>> Note that I haven't restarted the machine (though I think I restarted the
>> dpm service) after upgrading to 1.8.2 (from 1.8.1 I *think*!). Is this the
>> strange schema problem others have seen? In which case, which table should I
>> add this column to?
>>
>> Any help would be greatly appreciated!!
>>
>> Thanks,
>>
>> Mark
|