Whamcloud - gitweb
b=6514
authorjacob <jacob>
Thu, 7 Jul 2005 00:17:55 +0000 (00:17 +0000)
committerjacob <jacob>
Thu, 7 Jul 2005 00:17:55 +0000 (00:17 +0000)
commited5feb7e89b30d328f2977609f4ce5412258a3f5
tree015dd00764eb830715ff90e359e753ff0d5be5b6
parentf8fc13469ad89323c635cef6f88934be8910f9a8
b=6514
r=adilger,green
originally by nikita

Severity   : major
Frequency  : rare (only unsupported configurations with a node running as an
             OST and a client)
Bugzilla   : 6514, 5137
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.
18 files changed:
lustre/ChangeLog
lustre/include/linux/lustre_net.h
lustre/include/linux/obd.h
lustre/include/linux/obd_support.h
lustre/liblustre/file.c
lustre/llite/file.c
lustre/llite/llite_internal.h
lustre/llite/namei.c
lustre/llite/special.c
lustre/mds/mds_open.c
lustre/obdfilter/filter.c
lustre/obdfilter/filter_internal.h
lustre/obdfilter/filter_io.c
lustre/obdfilter/filter_io_24.c
lustre/obdfilter/filter_io_26.c
lustre/ost/ost_handler.c
lustre/ost/ost_internal.h
lustre/ptlrpc/service.c