On Wed, Feb 10, 2010 at 11:12 AM, Jeff Mahoney
It's possible. There's already the drivers:filesystems btrfs package. I haven't updated it in ages, though. The big issue now is that the current btrfs is based on 2.6.32+ which fundamentally changed the way filesystem writeback happens. It's a lot of work to get it working again on older kernels and I'd argue that if you're willing to test a file system during the development stage, you're probably ok running the bleeding edge kernel anyway.
personally, i'm not at all interested in getting it working on older kernels. rather, i'm interested in testing/preparing for what's coming ... soon. atm i'm running, uname -ri 2.6.33-rc6-12-xen x86_64 from Kernel:HEAD for OpenSuse12. which is, iiuc, about as "bleeding edge" as I can get within the opensuse repos. (pvops 'bleeds more', but i'm honestly not sure where in opensuse-land those kernels are ....) still, *that* kernel, built from sources pulled kernel upstream and patched w/ *suse 'magic', only include the "stable" btrfs tree. which is not the "unstable" tree which *has* been pushed in the last "for linus" branch. and most certainly does not include the "up -n- coming" fixes & capabiilities in the patchwork trees, waiting for the next merge window. my only point/suggestion is based on the fact btrfs is coming, and that -- eventually -- it will be implemented by *suse in some version of release kernels. it'd be nice to be able to have it as thoroughly vetted as possible before that release -- and I'd argue that that consists of testing the btrfs code as early as possibly in the dev cycle, not just after the merge window's been closed, and we're into rc kernels. this challenge stems from the 'policy' of having four btrfs-related trees -- stable, unstable, for-linus and patchwork (not really a tree -- yet) -- where the relevant, recent work is being done in the patchwork additions, and all of these being out of sync with the upstream mainstream kernel development, which -- of course -- is where the opensuse kernels are based. sure, there's the option of DIY'ing -- which is what I'm doing atm -- but, as you might well images, filing a bugs abt it @ *suse will get generally ignored because it's "not a supported option" &/or "not a priority", and upstream will argue that we should not use the distro's kernels ... or at least not *suse's (they strongly suggest Fedora12/13 as a better alternative :-/) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org