On Mon, Feb 8, 2010 at 8:57 AM, Jeff Mahoney
Have you looked at the diff in the actual code between Kernel:HEAD and btrfs-unstable?
I see a 126 line patch with extremely minor changes.
Yes, I did ... and discovered that the features/fixes I'm after have _not_ been, in fact, added to the unstable tree, but rather exist in yet another, unmerged location ... "Chris does not merge patches into the tree until they are pushed to Linus. Sometimes he creates "experimental" branches with code for testing but I don't think he has done that recently. You can find proposed unmerged patches at: http://patchwork.kernel.org/project/linux-btrfs/list/" Until that message, I'd not yet heard of the 'patchwork' site. :-( The btrfs wiki, referenced even in the *suse man pages, is, at best, a bit sparse on such info ... The good news is that, as you've pointed out, the diffs are not that significant ... once I figured out the right steps to the process, both the unstable module and tools build against the Suse kernel sources fine: modinfo btrfs filename: /lib/modules/2.6.33-rc6-12-xen/kernel/fs/btrfs/btrfs.ko license: GPL srcversion: 14CB8D6D8EF3012C156FDC1 depends: libcrc32c,zlib_deflate vermagic: 2.6.33-rc6-12-xen SMP mod_unload modversions Xen ls -al /usr/local/bin/btrfs* -rwxr-xr-x 1 root root 655556 2010-02-07 19:33 /usr/local/bin/btrfsck -rwxr-xr-x 1 root root 570459 2010-02-07 19:33 /usr/local/bin/btrfsctl -rwxr-xr-x 1 root root 576799 2010-02-07 19:33 /usr/local/bin/btrfs-debug-tree -rwxr-xr-x 1 root root 574634 2010-02-07 19:33 /usr/local/bin/btrfs-map-logical -rwxr-xr-x 1 root root 573254 2010-02-07 19:33 /usr/local/bin/btrfs-show -rwxr-xr-x 1 root root 569360 2010-02-07 19:33 /usr/local/bin/btrfs-vol btrfs-show Label: TEST uuid: 85aa9ac8-0089-4dd3-b8b2-3c0cbb96c924 Total devices 4 FS bytes used 32.00KB devid 3 size 931.51GB used 2.01GB path /dev/sdc devid 4 size 931.51GB used 2.01GB path /dev/sdd devid 1 size 931.51GB used 2.03GB path /dev/sda devid 2 size 931.51GB used 2.01GB path /dev/sdb Btrfs v0.19-4-gab8fb4c Atm I'm digging through the patchwork patches, and pulling/applying one at a time ... as well as stress-testing the btrfs arrays. Even though it'd be useful to "get out in front" and be testing btrfs-unstable+patches against *Suse Kernel:HEAD I'm guessing that having that all nice-n-tidy in an obs repo isn't likely to happen ... Thanks. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org