RE: mkdir and fsync

2014-09-14 Thread Samer Al-Kiswany
[mailto:c...@fb.com] Sent: Thursday, September 11, 2014 6:29 AM To: Samer Al-Kiswany; linux-btrfs@vger.kernel.org Subject: Re: mkdir and fsync On 09/10/2014 04:55 PM, Samer Al-Kiswany wrote: > Hi, > > Thank you for help. > > I am seeing a strange behavior when fsync()ing a director

Re: mkdir and fsync

2014-09-11 Thread Chris Mason
On 09/10/2014 04:55 PM, Samer Al-Kiswany wrote: > Hi, > > Thank you for help. > > I am seeing a strange behavior when fsync()ing a directory. > > Here is what I do > > for (i=0; i < 100,000, i++){ > . > mkdir(p/child_i) > fsync(p) > } > > Btrfs seems to achieve around 100k fs

Re: mkdir and fsync

2014-09-10 Thread Christoph Hellwig
On Wed, Sep 10, 2014 at 01:55:35PM -0700, Samer Al-Kiswany wrote: > Btrfs seems to achieve around 100k fsycs/second, which makes me believe it > is not touching the disk during these fsyncs. > After looking at the code, it seems indeed that fsync adds the inode to the > current transaction but does

mkdir and fsync

2014-09-10 Thread Samer Al-Kiswany
Hi, Thank you for help. I am seeing a strange behavior when fsync()ing a directory. Here is what I do for (i=0; i < 100,000, i++){ . mkdir(p/child_i) fsync(p) } Btrfs seems to achieve around 100k fsycs/second, which makes me believe it is not touching the disk during these