| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
> > > > 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. > > I spent some hours yesterday doing something like this manually, > grepping for ogfs_glock() and its wrappers (ogfs_glock_i(), > etc.). I'm writing some notes about it that I would like to > append to your locking document (maybe just before the "Flaws" > section?). I've also got some edits I would like to contribute > to the doc, typos and clarifications, that sort of thing. > Would that be okay? Of course. I have just written the initial version of the document. Everybody is welcome to improve it. Bye Dominik ^_^ ^_^ ------------------------------------------------------- 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