| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Thu, 2003-06-26 at 00:17, Dominik Vogt wrote: > On Wed, Jun 25, 2003 at 09:10:13PM -0700, Ben Cahill wrote: > > > The ogfs_glock() function gets called for the following blocks > > > (in the order listed): > > > > > > 20 20 19 17 21 21 2 21 20 21 2 > > > > > > Block 17 is the header of resource group 0 (block bitmap). > > > Block 19 is the resource group index inode. > > > Block 20 is the root directory inode. > > > Block 21 is the block with new inode for foo. > > > Block 2 is in the blank area before the superblock (block 16). No > > > idea what that means. > > > > Great list ... thanks! > > > > After poking around a bit, I think "block 2" is actually the > > lock number of the transaction lock, sdp->sd_trans_gl, and > > *not* a lock on a filesystem block. > > Good finding. Now it would be interesting to have a stack trace > for each of the ogfs_glock() calls to analyse where they all come > from. All you have to do is add a call to dump_stack() (and maybe a way to turn it on/off when you want) and you can see the stack trace. It would be interesting. -- Joe D. <joe@osdl.org> ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Opengfs-devel mailing list Opengfs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opengfs-devel