aufs.ko missing from the Precise kernels

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 943119

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Reading package lists... Done
bogdan@NAS:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
bogdan@NAS:~$

Bogdan - Can you describe with a bit more detail why overlayfs is insufficient for your application ?

Tim,

Thank you for the quick answer.
I believe the main reason is that the documentation is basically absent for overlayfs. I spent a lot of time trying to find some but I've only found bits and pieces mainly describing at a general level how it works.
I doubt that it can give me the level of control that aufs is giving me.

I had 6 hard drives (a total of 11 TB of storage space) in my desktop computer (on Ubuntu 11.10) with multimedia content on them stored in a top level folder called multimedia on each drive (all 6 drives have only one partition each). Inside multimedia I have from 1 to 6 subfolders holding different categories of multimedia files depending on the source disk. Besides the multimedia top folder there are some other folders holding various data. I was using AUFS to aggregate all 6 mounting point folders (from /media) in a single merged folder called BFD through this line in fstab:

none /media/BFD aufs br:/media/2TB_1=rw,br:/media/2TB_2=rw,br:/media/2TB_3=rw,br:/media/2TB_4=rw,br:/media/1.5TB_1=rw,br:/media/1.5TB_2=rw,create=tdp,sum 0 0

The policies gave me the liberty to control the behavior of AUFS exactly the way I wanted and that is: new files that are copied on BFD in a folder that originated from one of the drives to be created and stored on the same drive not not on the first writable branch with enough space available on it. I have an application that manages most of the multimedia content of BFD and while for read only access I guess any stackable unification filesystem would be be ok, but for writing, I've found that only aufs was suitable. I've also used to use mhddfs, but that one runs in userspace and on the other hand does not have the policies system so it would always write on the first drive with enough free space.

So I've decided to move the 6 drives in a dedicated NAS box and implement the same mechanism that proved to be the best suitable for what I need. Once I've installed Ubuntu server 12.04 and I've moved all the drives phisically inside the NAS I attempted to re-created BFD with aufs and this was the point where I've encountered the absence of aufs support (through an error that lead me to an open bug, mentioned in this bug's description)

I believe most are confident that overlayfs will replace aufs. However I'm concerned that there is no user-space tool, though "mount -o remount" might be enough.

The lack of documentation and the fact that it's(or was) enabled in the config file, but not included in the package concern me. The other 'big' problem is the aufs-tools package, delete it or make it depend on the correct kernel bits.

Until one of unionfs or overlayfs is merged upstream and considered to be sufficient, we are going to enable aufs. We'll continue to maintain pressure to drop aufs at each development cycle in favor of an upstream solution.

This bug was fixed in the package linux - 3.2.0-18.28

---------------
linux (3.2.0-18.28) precise; urgency=low

  [ Andy Whitcroft ]

  * ubuntu: AUFS -- adapt to the new changelog handling
  * ubuntu: AUFS -- sort out the relative header paths
  * ubuntu: AUFS -- update to d266b0c5d0693d6383976ee54b9e2c0fa9a3f5b0

  [ Chase Douglas ]

  * SAUCE: (drop after 3.3) HID: hid-magicmouse: Add pointer and buttonpad
    properties for Magic Trackpad
  * SAUCE: Input: synaptics - add second variant of two-button clickpad
  * SAUCE: Input: synapticss - Set buttonpad property for all clickpads

  [ Johannes Berg ]

  * SAUCE: iwlwifi: fix key removal
    - LP: #911059

  [ John Johansen ]

  * Revert "SAUCE: AppArmor: Fix unpack of network tables."
  * Revert "SAUCE: AppArmor: Allow dfa backward compatibility with broken
    userspace"
  * SAUCE: AppArmor: Add mising end of structure test to caps unpacking
  * SAUCE: AppArmor: Fix dropping of allowed operations that are force
    audited
  * SAUCE: AppArmor: Fix underflow in xindex calculation
  * SAUCE: AppArmor: fix mapping of META_READ to audit and quiet flags
  * SAUCE: AppArmor: Fix the error case for chroot relative path name
    lookup
    - LP: #925028
  * SAUCE: AppArmor: Retrieve the dentry_path for error reporting when path
    lookup fails
    - LP: #925028
  * SAUCE: AppArmor: Minor cleanup of d_namespace_path to consolidate error
    handling
  * SAUCE: AppArmor: Update dfa matching routines.
  * SAUCE: AppArmor: Move path failure information into aa_get_name and
    rename
  * SAUCE: AppArmor: Make chroot relative the default path lookup type
  * SAUCE: AppArmor: Add ability to load extended policy
  * SAUCE: AppArmor: basic networking rules
  * SAUCE: AppArmor: Add profile introspection file to interface
  * SAUCE: AppArmor: Add the ability to mediate mount
  * SAUCE: AppArmor: Add mount information to apparmorfs

  [ Kees Cook ]

  * SAUCE: AppArmor: refactor securityfs to use structures
  * SAUCE: AppArmor: add initial "features" directory to securityfs
  * SAUCE: AppArmor: add "file" details to securityfs
  * SAUCE: AppArmor: export known rlimit names/value mappings in securityfs

  [ Leann Ogasawara ]

  * Revert "[Config] Enable CONFIG_NVRAM=m"
    - LP: #942193
  * Rebase to v3.2.7
  * [Config] Enable CONFIG_USB_SERIAL_QUATECH2=m on arm and powerpc
  * [Config] Enable CONFIG_USB_SERIAL_QUATECH_USB2=m on arm and powerpc
  * [Config] Add CONFIG_NVRAM to config enforcer
    - LP: #942193
  * [Config] Enable CONFIG_SCSI_IBMVSCSI=m for powerpc
    - LP: #943090
  * [Config] Enable CONFIG_SCSI_IPR=m for powerpc
    - LP: #943090
  * provide ipmi udeb
    - LP: #942926
  * Rebase to v3.2.9
  * Add ibmveth to d-i/modules-powerpc/nic-modules
    - LP: #712188
  * [Config] Enable CONFIG_SCSI_IBMVFC=m for powerpc
    - LP: #712188
  * Add ibmvfc and ibmvscsic to d-i/modules-powerpc/nic-modules
    - LP: #712188

  [ Seth Heasley ]

  * SAUCE: ALSA: hda - Add Lynx Point HD Audio Controller DeviceIDs
    - LP: #900119
  * SAUCE: ahci: AHCI-mode SATA patch for Intel Lynx Point DeviceIDs
    - LP: #900119
  * SAUCE: ata_piix: IDE-mode SATA patch for Intel Lynx Point DeviceIDs
    - LP: #900119
...

Thank you Tim!

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.