search for: ablock84

tree: git://github.com/ablock84/linux-btrfs.git btrfs-far head: f9a5bb450a8cc7aa5fd4f11d0306b3f48cf2771d commit: 29aefeaaf482ab396ff53c2bbf5c35ce237b91c0 [19/20] fs: add libfarstream support config: make ARCH=s390 allmodconfig All error/warnings: In file included from include/linux/byteorder/big_endian.h:4:0,...

...d <anand.jain@oracle.com> This patch adds creation-time to the snapshot list display, which would help user to better manage the snapshots when number of snapshots grow substantially. This patch is developed and on top of the send/receive btrfs and btrfs-progs repo at git://github.com/ablock84/linux-btrfs.git (send-v2) git://github.com/ablock84/btrfs-progs.git (send-v2) respectively. Further this patch has the dependency on the following patches Liu Bo: [PATCH 2/3 RESEND] Btrfs-progs: show generation in command btrfs subvol list [PATCH 3/3] Btrfs-progs: list snapshots by gen...

Hello, I''m currently trying to understand how compression in btrfs works. I could not find any detailed description about it. So here are my questions. 1. How is decided what to compress and what not? After a fast test with a 2g image file, I''ve looked into the extents of that file with find-new and it turned out that only some of the first extents were compressed. The file was

We have finished a beta version of the feature. A webrev for it can be found here: http://cr.illumos.org/~webrev/sensille/fits-send/ It adds a command ''zfs fits-send''. The resulting streams can currently only be received on btrfs, but more receivers will follow. It would be great if anyone interested could give it some testing and/or review. If there are no objections,

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...alext@mellanox.com> Alex Villac<ED>s Lasso <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <ag...

...o <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alex Zhuravlev <alexey.zhuravlev@intel.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Frolkin <avf@eldamar.org.uk> Alexander Gordeev <...

...o <a_villacis@palosanto.com> Alex Williamson <alex.williamson@redhat.com> Alex Yang <xiaojuny@qca.qualcomm.com> Alex Zhuravlev <alexey.zhuravlev@intel.com> Alexander Aring <alex.aring@gmail.com> Alexander Bergmann <alex@linlab.net> Alexander Block <ablock84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Frolkin <avf@eldamar.org.uk> Alexander Gordeev <...

Hello, I''m currently implementing parts of a send/receive tool that walks through all inodes and records changes into a tar/pax archive. Changes are determined by the transid of inodes and the generation number of file extent items. An inode/extent is considered to be changed if the transid/generation is higher then a specified generation. While testing the code I found a problem with

Hello, This is the second attempt to bring in cross subvolume reflinks into btrfs. The first attempt was NAKed due to missing vfs mount checks and a clear description of what btrfs subvolumes are and probably also why cross subvolume reflinks are ok in the case of btrfs. This version of the patch comes from David and is in SUSE kernels since a long time, so it is tested and working. The patch

Hello all, in IRC we had a discussion on how we could solve sending live subvolumes and how to send subvolumes without the need to administrate/keep old snapshots for incremental sends. One of the ideas was to introduce "sendshots", which are basically snapshots where no refs are counted for file data. This means, that when file data is changed in the sendshot origin, we do not consume