From mboxrd@z Thu Jan 1 00:00:00 1970 From: Francis Moreau Subject: Re: tracing at filesystem level Date: Sat, 22 Nov 2008 08:50:14 +0100 Message-ID: References: <515126840@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org To: devzero@web.de Return-path: Received: from fk-out-0910.google.com ([209.85.128.188]:46697 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750965AbYKVHua (ORCPT ); Sat, 22 Nov 2008 02:50:30 -0500 Received: by fk-out-0910.google.com with SMTP id 18so1395871fkq.5 for ; Fri, 21 Nov 2008 23:50:28 -0800 (PST) In-Reply-To: <515126840@web.de> (devzero@web.de's message of "Fri\, 21 Nov 2008 16\:53\:40 +0100") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: devzero@web.de writes: > i`d like to be able to trace filesystem access at early boot time, > i.e to see what files being opened/closed on early boot (and later > on). > > one possible way to do it is using nfs-root, so we can trace it at > the network or server level - but how can this be done without using > network filesystem ? > > i came across tracefs > (http://www.filesystems.org/docs/tracefs-fast04/tracefs.pdf) which > looks very promising, but it seems it`s not actively maintained. > > isn`t there a standard way to do that with recent kernels ? i > searched for a while but didn`t find something appropriate.... Wouldn't inotify be appropriate for this ? Francis