On 10/8/12 2:43 AM, Prashant Shah wrote: > Hi, > > On Fri, Oct 5, 2012 at 11:03 PM, Eric Sandeen <sandeen@xxxxxxxxxx> wrote: >> I haven't looked at your custom code, but freeze has changed a bit lately, >> and "hangs" is a very vague description >> >> -Eric > > I am monitoring the file system (ext3) for block writes and on > linux-2.6.18 (centos - 5.8 64bit) there are lots of writes request per > second with inode number set to 0 even when the file system is idle > and without any work loads. Didnt see this happen on linux-3.x. > > filter: sector=242983 inode=0 if you dumpe2fs your fs you may find those sectors contain metadata not data. Anyway, did you try the suggestions I offered to track down your original question about the freeze deadlock? -Eric > filter: sector=242991 inode=0 > filter: sector=242999 inode=0 > filter: sector=243007 inode=0 > filter: sector=243015 inode=0 > filter: sector=243023 inode=0 > filter: sector=243031 inode=0 > filter: sector=243039 inode=0 > > What are these request with inode number as 0 ? All the special inode > numbers start from 1. > > http://lxr.linux.no/#linux+v2.6.32/include/linux/ext3_fs.h#L56 > > Regards. > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
