Re: Beagle with Samba Share

[Joe Shaw <joeshaw novell com>]

Hi,

On Wed, 2007-01-17 at 16:35 +0000, Stringer Leon (West Midlands
Ambulance Service NHS Trust) wrote:
> It reports: Dl+

This means that it's in disk wait; for some reason it's waiting on IO,
presumably to/from the Samba server.

> "" tid=0x0xb7f1e6d0 this=0x0x21e40:
>   at (wrapper managed-to-native) Mono.Data.SqliteClient.Sqlite.sqlite3_step (intptr) <0x00004>
>   at (wrapper managed-to-native) Mono.Data.SqliteClient.Sqlite.sqlite3_step (intptr) <0xffffffff>
>   at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (intptr,int&,intptr&,intptr&) <0x0002e>
>   at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (intptr) <0x00031>
>   at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (System.Data.CommandBehavior,bool,int&) <0x001d4>
>   at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () <0x0001c>
>   at Beagle.Util.SqliteUtils.DoNonQuery (Mono.Data.SqliteClient.SqliteConnection,string) <0x0006a>
>   at Beagle.Daemon.TextCache..ctor (string,bool) <0x003c6>
>   at Beagle.Daemon.TextCache..ctor (string) <0x0000f>

I guess this is being done on the samba share, and that's what's causing
the disk IO?  It seems like the text cache would be taken care of in the
synchronized directory.

The disk wait stuff happens at the syscall/kernel level... this suggests
that maybe this isn't really Beagle-related.  But I presume other
applications work fine out of this home directory?

Joe