Merge b1_4_bug3389 from b1_4 (20050729_0312)
Description: Mounting a Lustre file system on a node running as an OST could lead to deadlocks Details : OSTs now allocate memory needed to write out data at startup, instead of when needed, to avoid having to allocate memory in possibly low memory situations. Specifically, if the file system is mounted on on OST, memory pressure could force it to try to write out data, which it needed to allocate memory to do. Due to the low memory, it would be unable to do so and the node would become unresponsive. b=6514, b=5137 Description: Addition of lconf --service command line option Details : lconf now accepts a '--service <arg>' option, which is shorthand for 'lconf --group <arg> --select <arg>=<hostname>' b=7015 Description: Failover mode is now the default for OSTs. Details : By default, OSTs will now run in failover mode. To return to the old behaviour, add '--failout' to the lmc line for OSTs. b=6101 Description: Health checks are now provided for MDS and OSTs Details : Additional detailed health check information on MSD and OSTs is now provided through the procfs health_check value. b=1693 Description: Disk fragmentation on the OSTs could eventually cause slowdowns after numerous create/delete cycles Details : The ext3 inode allocation policy would not allocate new inodes very well on the OSTs because there are no new directories being created. Instead we look for groups with free space if the parent directories are nearly full. b=4466 Description: Network or server problems during mount may cause partially mounted clients instead of returning an error. Details : The config llog parsing code may overwrite the error return code during mount error handling, returning success instead of an error. b=6302
Please register or sign in to comment