[I'm the original bug reporter. Sorry for getting so late into the
conversation]
On Thu, Apr 05, 2007 at 12:47:49AM +0400, Michael Tokarev wrote:
> Neil Brown wrote:
> > On Tuesday April 3, [EMAIL PROTECTED] wrote:
> []
> >> After the power cycle the kernel boots, devices are discovered, among
> >
On Wednesday April 11, [EMAIL PROTECTED] wrote:
> > From: Mark Hahn [mailto:[EMAIL PROTECTED]
> >
> > > In its current implementation write-back mode acknowledges writes
> before
> > > they have reached non-volatile media.
> >
> > which is basically normal for unix, no?
> I am referring to when b
Dan Williams wrote:
> In write-through mode bi_end_io is called once writes to the data disk(s)
> and the parity disk have completed.
>
> In write-back mode bi_end_io is called immediately after data has been
> copied into the stripe cache, which also causes the stripe to be marked
> dirty.
This i
> From: Mark Hahn [mailto:[EMAIL PROTECTED]
>
> > In its current implementation write-back mode acknowledges writes
before
> > they have reached non-volatile media.
>
> which is basically normal for unix, no?
I am referring to when bi_end_io is called on the bio submitted to MD.
Normally it is no
In its current implementation write-back mode acknowledges writes before
they have reached non-volatile media.
which is basically normal for unix, no?
are you planning to support barriers? (which are the block system's way
of supporting filesystem atomicity).
-
To unsubscribe from this list:
-stable review patch. If anyone has any objections, please let us know.
--
From: Neil Brown <[EMAIL PROTECTED]>
If 'num_pages' were ever 1 more than a multiple of 8 (32bit platforms)
for of 16 (64 bit platforms). filemap_attr would be allocated one
'unsigned long' shorter than re
