kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

lenosqueeze, thank you for reporting this and helping make Ubuntu better. Lucid reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

** Tags added: needs-kernel-logs needs-upstream-testing regression-
potential

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1097042

Title:
  Risk of filesystem corruption with ext3 in lucid

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  On my system, a default ext3 mount (no fstab entry) results in:
  $ cat /proc/mounts
  /dev/sda6 /media/space ext3 rw,nosuid,nodev,relatime,errors=continue,user_xattr,acl,data=ordered 0 0

  We can see the "barrier=1" option is missing by default, which can
  cause severe filesystem corruption in case of power failure (i've been
  hit recently). Quoting mount(1):

  "barrier=0 / barrier=1
  This enables/disables barriers.  barrier=0 disables it, barrier=1 enables it.  Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe  to  use,  at  some  performance penalty. The ext3 filesystem does not enable write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another.  Otherwise you risk filesystem corruption in case of power failure."

  the issue is fixed in later kernels (precise 3.2.0-35 is not
  affected), but lucid users are left to suffer the consequences of this
  horrifying default.

  $ uname -a
  Linux netbook 2.6.32-45-generic #101-Ubuntu SMP Mon Dec 3 15:41:13 UTC 2012 i686 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1097042/+subscriptions