kernel-packages team mailing list archive

[Kristian Erik Hermansen <kristian.hermansen@xxxxxxxxx>]

Unable to test sorry.

-- 
Kristian Erik Hermansen
https://www.linkedin.com/in/kristianhermansen
https://profiles.google.com/kristian.hermansen
On Jan 2, 2014 6:10 PM, "Christopher M. Penalver" <
christopher.m.penalver@xxxxxxxxx> wrote:

> Kristian Erik Hermansen, this bug was reported a while ago and there
> hasn't been any activity in it recently. We were wondering if this is
> still an issue? 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 (installed or live) 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>
>
> If reproducible, could you also please test the latest upstream kernel
> available (not the daily folder) following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. 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.13-rc6
>
> 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
>
> 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.
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
> ** Tags added: needs-kernel-logs needs-upstream-testing regression-
> potential
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1187214
>
> Title:
>   "ext4-fs error" -- Ubuntu upgrade from 12.10 to 13.04 corrupted
>   filesystems (ext4 corruption bug)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1187214/+subscriptions
>

-- 
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/1187214

Title:
  "ext4-fs error" -- Ubuntu upgrade from 12.10 to 13.04 corrupted
  filesystems (ext4 corruption bug)

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I thought it would be a good idea to upgrade from 12.10 to 13.04.
  Apparently, Ubuntu likes to corrupt my data. My configuration has
  4xHDD in RAID0 using ecryptfs of user data only. 70% into the upgrade
  process using the recommended GUI upgrade option, the process failed,
  the ext4 file-system became corrupted and all data was lost.
  Eventually, my kernel crashed shortly afterwards and rebooted. I was
  able to snap a quick photo, but it is only the last page of the
  errors....

  ...

  ...

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