Re: aufs4 fails to build on 4.0 - Debian
On 27/07/15 00:36, Ben Hutchings wrote: > On Fri, 2015-07-24 at 19:26 +0100, OmegaPhil wrote: >>> >>> On Monday 25 May 2015 04:55 PM, sf...@users.sourceforge.net wrote: Ritesh Raj Sarraf: > Anyways, in the standalone tree, there are a bunch of patches with no > order defined. Is it to assume that they can all be applied randomly ? No. Please refer to README file in aufs4-standalone.git. >>> >>> >>> Yup. That one explain. Sorry. I completely missed that file. >>> > I was hoping if we can have a standalone/dkms tree, which could build a > kernel module out, easily loadable in the respective kernel ?? Patching is neccessary (by either manually or GIT), which means you will need another kernel as long as debian kernel is unpatched. >>> >>> Then it may not fit in the bill of dkms. Let me check with Ben on how he >>> supported it for Jessie. >> >> >> Did this go anywhere? I'm on Debain Testing, the recent upgrade to v4 >> kernel completely bricked aufs volumes on the 2 machines I use it on >> locally because they removed this (and where was the acceptability of >> such a removal discussed? Nothing comes up on a search)... > > The aufs patches to the kernel are included in Debian packages again as > of Linux 4.1 which will go into unstable soon. You will still have to > build the module separately. > > Ben. Thanks, I'll keep an eye on the kernel and install it from unstable when it appears, and start building this module now. signature.asc Description: OpenPGP digital signature --
Re: aufs4 fails to build on 4.0 - Debian
On Fri, 2015-07-24 at 19:26 +0100, OmegaPhil wrote: > > > > On Monday 25 May 2015 04:55 PM, sf...@users.sourceforge.net wrote: > > > Ritesh Raj Sarraf: > > > > Anyways, in the standalone tree, there are a bunch of patches with no > > > > order defined. Is it to assume that they can all be applied randomly ? > > > No. > > > Please refer to README file in aufs4-standalone.git. > > > > > > Yup. That one explain. Sorry. I completely missed that file. > > > > > > I was hoping if we can have a standalone/dkms tree, which could build a > > > > kernel module out, easily loadable in the respective kernel ?? > > > Patching is neccessary (by either manually or GIT), which means you will > > > need another kernel as long as debian kernel is unpatched. > > > > > > > > > > Then it may not fit in the bill of dkms. Let me check with Ben on how he > > supported it for Jessie. > > > Did this go anywhere? I'm on Debain Testing, the recent upgrade to v4 > kernel completely bricked aufs volumes on the 2 machines I use it on > locally because they removed this (and where was the acceptability of > such a removal discussed? Nothing comes up on a search)... The aufs patches to the kernel are included in Debian packages again as of Linux 4.1 which will go into unstable soon. You will still have to build the module separately. Ben. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature. signature.asc Description: This is a digitally signed message part --
Re: aufs4 fails to build on 4.0 - Debian
> On Monday 25 May 2015 04:55 PM, sf...@users.sourceforge.net wrote: >> Ritesh Raj Sarraf: >>> Anyways, in the standalone tree, there are a bunch of patches with no >>> order defined. Is it to assume that they can all be applied randomly ? >> No. >> Please refer to README file in aufs4-standalone.git. > > > Yup. That one explain. Sorry. I completely missed that file. > >>> I was hoping if we can have a standalone/dkms tree, which could build a >>> kernel module out, easily loadable in the respective kernel ?? >> Patching is neccessary (by either manually or GIT), which means you will >> need another kernel as long as debian kernel is unpatched. >> >> > > Then it may not fit in the bill of dkms. Let me check with Ben on how he > supported it for Jessie. Did this go anywhere? I'm on Debain Testing, the recent upgrade to v4 kernel completely bricked aufs volumes on the 2 machines I use it on locally because they removed this (and where was the acceptability of such a removal discussed? Nothing comes up on a search)... signature.asc Description: OpenPGP digital signature --
Re: aufs4 fails to build on 4.0 - Debian
On Monday 25 May 2015 04:55 PM, sf...@users.sourceforge.net wrote: > Ritesh Raj Sarraf: >> Anyways, in the standalone tree, there are a bunch of patches with no >> order defined. Is it to assume that they can all be applied randomly ? > No. > Please refer to README file in aufs4-standalone.git. Yup. That one explain. Sorry. I completely missed that file. >> I was hoping if we can have a standalone/dkms tree, which could build a >> kernel module out, easily loadable in the respective kernel ?? > Patching is neccessary (by either manually or GIT), which means you will > need another kernel as long as debian kernel is unpatched. > > Then it may not fit in the bill of dkms. Let me check with Ben on how he supported it for Jessie. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." signature.asc Description: OpenPGP digital signature -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
Re: aufs4 fails to build on 4.0 - Debian
Ritesh Raj Sarraf: > Anyways, in the standalone tree, there are a bunch of patches with no > order defined. Is it to assume that they can all be applied randomly ? No. Please refer to README file in aufs4-standalone.git. > I think that will help increase the userbase and eventually include aufs > mainline, or atleast part of its features into mainline overlayfs. About overlayfs, its very basic disign policy is different from aufs. I've discussed about it with the authour of overlayfs, and I don't think a part of aufs features won't be merged into overlayfs. If you know the specific part, describe it spscifically. > I was hoping if we can have a standalone/dkms tree, which could build a > kernel module out, easily loadable in the respective kernel ?? Patching is neccessary (by either manually or GIT), which means you will need another kernel as long as debian kernel is unpatched. J. R. Okajima -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
Re: aufs4 fails to build on 4.0 - Debian
On Sunday 24 May 2015 09:53 PM, sf...@users.sourceforge.net wrote: > Hello Ritesh, > > Ritesh Raj Sarraf: >> I've been trying to build aufs4 on my Debian kernel and run into the >> following build failure. > I am afraid you forgot applying aufs patches to your kernel source tree, > especially aufs4-mmap.patch. > > > J. R. Okajima Thank you for the response. But given the description of standalone vs linux tree, I assumed this would just work. Anyways, in the standalone tree, there are a bunch of patches with no order defined. Is it to assume that they can all be applied randomly ? Second, many of these patches from the standalone tree, are touching other kernel files. My understanding of a standalone tree was that it was self contained, and I could just build a kernel module out of it. But that doesn't seem to be the case AUFS has features that are of interest to me. But it is unfortunate, that like CFS, Linux for now, is using just one union fs, i.e. overlayfs. I think the best bet would be to have aufs easily usable for users. I was thinking of reintroducing it into Debian in the form of a dkms package. (FYI: Debian last shipped AUFS in Jessie in kernel 3.16. But given that overlayfs got merged in 3.18, they've now dropped aufs) I think that will help increase the userbase and eventually include aufs mainline, or atleast part of its features into mainline overlayfs. I was hoping if we can have a standalone/dkms tree, which could build a kernel module out, easily loadable in the respective kernel ?? For example, see the following out-of-tree dkms packages I've been maintaining for Debian. https://packages.qa.debian.org/iscsitarget-dkms http://packages.qa.debian.org/virtualbox-dkms -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." signature.asc Description: OpenPGP digital signature -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
Re: aufs4 fails to build on 4.0 - Debian
Hello Ritesh, Ritesh Raj Sarraf: > I've been trying to build aufs4 on my Debian kernel and run into the > following build failure. I am afraid you forgot applying aufs patches to your kernel source tree, especially aufs4-mmap.patch. J. R. Okajima -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
aufs4 fails to build on 4.0 - Debian
Hi, I've been trying to build aufs4 on my Debian kernel and run into the following build failure. rrs@ril:/var/tmp/aufs4-standalone (aufo4.0)$ make -I/var/tmp/aufs4-standalone/include -DCONFIG_AUFS_FS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST -DCONFIG_AUFS_DEBUG make -C /lib/modules/4.0.0/build M=/var/tmp/aufs4-standalone/fs/aufs EXTRA_CFLAGS="-I/var/tmp/aufs4-standalone/include -DCONFIG_AUFS_FS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST -DCONFIG_AUFS_DEBUG" modules make[1]: Entering directory '/var/tmp/linux-upstream_GIT' CC [M] /var/tmp/aufs4-standalone/fs/aufs/module.o In file included from /var/tmp/aufs4-standalone/fs/aufs/aufs.h:44:0, from /var/tmp/aufs4-standalone/fs/aufs/module.c:24: /var/tmp/aufs4-standalone/fs/aufs/file.h: In function ‘au_vm_prfile_set’: /var/tmp/aufs4-standalone/fs/aufs/file.h:282:5: error: ‘struct vm_area_struct’ has no member named ‘vm_prfile’ vma->vm_prfile = file; ^ scripts/Makefile.build:258: recipe for target '/var/tmp/aufs4-standalone/fs/aufs/module.o' failed make[2]: *** [/var/tmp/aufs4-standalone/fs/aufs/module.o] Error 1 Makefile:1390: recipe for target '_module_/var/tmp/aufs4-standalone/fs/aufs' failed make[1]: *** [_module_/var/tmp/aufs4-standalone/fs/aufs] Error 2 make[1]: Leaving directory '/var/tmp/linux-upstream_GIT' Makefile:42: recipe for target 'fs/aufs/aufs.ko' failed make: *** [fs/aufs/aufs.ko] Error 2 16:26 ♒♒♒☹ => 2 I haven't tried it with stock kernel, but looking at the build failure, I have less reasons to believe that Debian kernels would change any interface. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
