On Sun, Jun 18, 2017 at 06:20:20AM -0400, Tejun Heo wrote:
> Hello, Christoph.
>
> On Sun, Jun 18, 2017 at 09:33:05AM +0200, Christoph Hellwig wrote:
> > > Both straces attached (gzipped due to size). Note that this on a system
> > > with four NVMe devices, two of which are nvme-loop devices that have the
> > > uuid attribute.
> >
> > And now really attached..
>
> If you "cd /sys/kernel/debug/tracing; cd -" before doing the find,
> does it succeed the first time? It could be that the on-demand
> mounting of tracefs is giving incoherent results across the mounting
> and confusing find.
Before tracefs is automounted
File: '/sys/kernel/debug/tracing'
Size: 0 Blocks: 0 IO Block: 4096 directory
Device: 8h/8d Inode: 2054 Links: 3
Access: (0555/dr-xr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-06-18 03:21:26.241000000 -0700
Modify: 2017-06-18 03:21:26.241000000 -0700
Change: 2017-06-18 03:21:26.241000000 -0700
Birth: -
and after
File: '/sys/kernel/debug/tracing/'
Size: 0 Blocks: 0 IO Block: 4096 directory
Device: 9h/9d Inode: 1 Links: 6
Access: (0700/drwx------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-06-18 03:21:26.241000000 -0700
Modify: 2017-06-18 03:21:26.241000000 -0700
Change: 2017-06-18 03:21:26.241000000 -0700
Birth: -
and it gets mounted while the first find is iterating through it.
Thanks.
--
tejun
