Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Tue, Jan 31, 2012 at 09:03:04AM -0800, envisionrx wrote: > > > Lars Ellenberg wrote: > > > > On Mon, Jan 30, 2012 at 02:56:57PM -0600, Ronald Wells wrote: > > > >>Only that 8.4.0 is much more seriously broken than 8.4.1 :-/ > > > I was afraid of that.. I am planning to go back to 8.3 branch, but wanted > to post this in hopes it would help fix a bug. > > > > > >>I suggest you retry and configure > >> "no-disk-barriers; no-disk-flushes; no-md-flushes;" > >>for at least the stacked resource, > >>that may help working around this issue. > > If doing that would help debug the prob I'm happy to, I'm assuming that > would not be recommended for a production system? Does not make a difference: the lower level DRBD does not support barrier requests, but fails them with -EOPNOTSUPP. So the stacked one would detect that, and disable this option anyways. In fact, recommended for a production system: decent storage controllers with as big a (battery backed or otherwise) non-volatile cache you can afford. In which case it is also recommended to turn off barrier usage. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com