CVSROOT:/cvs/cluster
Module name:cluster
Branch: RHEL46
Changes by: [EMAIL PROTECTED] 2008-01-11 14:24:19
Modified files:
cman/cman_tool : join_ccs.c
Log message:
Always the node name from cluster.conf as the node name.
Fix fixes fencing and
Hi,
Now in the -nmw git tree,
Steve.
On Fri, 2008-01-11 at 13:44 -0600, Bob Peterson wrote:
Hi,
This is a small I/O performance enhancement to gfs2. (Actually, it is a
rework of
an earlier version I got wrong). The idea here is to check if the write
extends
past the last block in
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Fri, 2008-01-11 at 13:31 -0600, Bob Peterson wrote:
Hi,
This patch removes a vestigial variable i_spin from the gfs2_inode
structure. This not only saves us memory (30 of these in memory
for the oom test) it also saves us time because
CVSROOT:/cvs/cluster
Module name:cluster
Changes by: [EMAIL PROTECTED] 2008-01-11 21:32:51
Modified files:
rgmanager/src/resources: lvm_by_vg.sh
Log message:
- Bug #428448
- HA LVM service fails to relocate when I/O is running
Was
CVSROOT:/cvs/cluster
Module name:cluster
Branch: RHEL5
Changes by: [EMAIL PROTECTED] 2008-01-11 21:32:55
Modified files:
rgmanager/src/resources: lvm_by_vg.sh
Log message:
- Bug #428448
- HA LVM service fails to relocate when I/O is running
Hi,
This is a small I/O performance enhancement to gfs2. (Actually, it is a rework
of
an earlier version I got wrong). The idea here is to check if the write extends
past the last block in the file. If so, the function can save itself a lot of
time and trouble because it knows an allocate
CVSROOT:/cvs/cluster
Module name:cluster
Branch: RHEL4
Changes by: [EMAIL PROTECTED] 2008-01-11 21:33:31
Modified files:
rgmanager/src/resources: lvm_by_vg.sh
Log message:
- Bug #428475
- HA LVM service fails to relocate when I/O is running
Hi,
This patch removes a vestigial variable i_spin from the gfs2_inode
structure. This not only saves us memory (30 of these in memory
for the oom test) it also saves us time because we don't have to
spend time initializing it (i.e. slightly better performance).
Regards,
Bob Peterson
Red
Wendy Cheng wrote:
The point here is with this patch, f_locks it not used at all any
more. Note that we have a nice inline function nlm_file_inuse, why
should we use f_locks (that I assume people agree that it is awkward)
? Could we simply drop f_locks all together in this section of code?
