On Sun, Sep 29, 2013 at 01:46:23AM +0200, Aastha Mehta wrote: > I am using linux kernel 3.1.10-1.16, just to let you know. Not that it invalidates the questions below, but that's a really old kernel. You should update to something recent (3.11, or 3.12-rc2) as soon as possible. There are major problems in 3.1 (and most of the subsequent kernels) that have been fixed in 3.11. Of course, there are still major problems in 3.11 that haven't been fixed yet, but we don't know about very many of those. :) (And when we do, we'll be recommending that you upgrade to whatever has them fixed...) Hugo. > Thanks > > On 29 September 2013 01:35, Aastha Mehta <aasthakm@xxxxxxxxx> wrote: > > Hi, > > > > I have few questions regarding logging triggered by calling fsync in BTRFS: > > > > 1. If I understand correctly, fsync will call to log entire inode in > > the log tree. Does this mean that the data extents are also logged > > into the log tree? Are they copied into the log tree, or just > > referenced? Are they copied into the subvolume's extent tree again > > upon replay? > > > > 2. During replay, when the extents are added into the extent > > allocation tree, do they acquire the physical extent number during > > replay? Does they physical extent allocated to the data in the log > > tree differ from that in the subvolume? > > > > 3. I see there is a mount option of notreelog available. After > > disabling tree logging, does fsync still lead to flushing of buffers > > to the disk directly? > > > > 4. Is it possible to selectively identify certain files in the log > > tree and flush them to disk directly, without waiting for the replay > > to do it? > > > > Thanks > > -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- <Diablo-D3> My code is never released, it escapes from the --- git repo and kills a few beta testers on the way out.
Attachment:
signature.asc
Description: Digital signature
