I am using linux kernel 3.1.10-1.16, just to let you know. Thanks
On 29 September 2013 01:35, Aastha Mehta <aasth...@gmail.com> 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 > > -- > Aastha Mehta -- Aastha Mehta -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
