Re: Data-logging and md as / fs bug

[Chris Mason <mason@suse.com>]

On Fri, 2003-05-09 at 16:21, Manuel Krause wrote:
> Thanks for your description below about what is really useful... :-))
> 
> On 02/23/03 you posted a kinoded-9.diff.gz to the list that solved a 
> "device busy" on here when umounting a partition directly after copying 
> some GB data to it.

kinoded-9 was fixing a symptom, the real problem  was the patch to allow
dirty inodes to hang around instead of logging them instantly.  With the
right workload you could reproduce the device busy on unmount problem
with kinoded-9 applied too.

> In those days you proposed to also use kinoded when not having the quota 
> patches applied. (That were the times when dirty-inodes-for-kinoded.diff
> was new.)
> 
> My questions:
> Is kinoded really useless without quota?

Right now, yes.

> Did you discontinue the kinoded-9 changes?

kinoded-9 changes are still good, I need to post an updated patch.  They
are not critical though.

> Does it conflict with the recent data-logging changes?

No

> And, I just read on the list that Kerin Millar wrote about 
> device/resource busy error messages and was wondering if that had 
> something to do with it.
> 

The software raid problems are different, that was a long standing bug
in the journal relocation code.

-chris