Hi guys,
I decided to bite the bullet and checked this patch in after a few more
cleanups and stress tests.
Do let me know if I broke cvs, build and/or functionalities ..
Thanks!
Murali
On Sun, 17 Sep 2006, Murali Vilayannur wrote:
> Hi Pete,
>
> >
> > Random stuff in pvfs2-cache.c, test/configur
I've been debugging why the metadata server calls fdatasync() five
times during a single create operation. (IO server separate and
not considered here.)
In fs.conf, I had these StorageHints settings
TroveSyncMeta no
TroveSyncData no
CoalescingHighWatermark infinity
CoalescingLowW
Thanks, Phil!
BTW: Do all the ACL stuff work for you guys now on different distros?
Murali
On Wed, 20 Sep 2006, Phil Carns wrote:
> Yes, this works great. Thanks for the quick fix!
>
> -Phil
>
> Murali Vilayannur wrote:
> > Hi Phil,
> > I just checked in a fix for this.
> > Basically, the proble
Yes, this works great. Thanks for the quick fix!
-Phil
Murali Vilayannur wrote:
Hi Phil,
I just checked in a fix for this.
Basically, the problem was that in pvfs2_init_acl(), i wanted to
mark the inode as dirty if its mode changed. Instead i was unconditionally
marking it as dirty..duh
Could
Awesome, Sam!
Can you check in your changes to test/posix/open.c as well?
I will modify the rest (test/posix/io.c, test/posix/iox.c)
thanks!
Murali
>
> Hi Guys,
>
> I finally found the bug(s) causing these hangs. The first problem was
> in the request scheduler, with the new crdirent pass-through
Hi all,
Since I'm being discussed, I thought that I should chime in :).
I agree that what we're talking about here is just a couple of steps in
the right general direction, not where we would really like to be in the
long run.
The zero-conf concept sounds great to me, conceptually. However,
Thanks for figuring this out Sam! -- Rob
Sam Lang wrote:
Hi Guys,
I finally found the bug(s) causing these hangs. The first problem was
in the request scheduler, with the new crdirent pass-through changes.
The handle the crdirent gets queued on is actually the directory handle
instead of t
Hi,
> calling any of the coalescing code. Julian and I had talked about this
> being a problem a while back, but I guess it never got looked at. In
> any case, I was able to cleanup the sync coalescing code some, so it was
> probably worth it.
I remember that I actually commited a fix to my branc
