** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384711
Title:
btrfs oops on current 3.13
To manage notifications about this
I believe the fix landed in 3.14, namely Btrfs: don't use ram_bytes for
uncompressed inline items and I think this fixes the issue on disc, so
that if you reverted back to 3.13 you would no longer see the bug.
Because we can't test this now I'm not sure how to proceed.
From what I understand
I did originally think Btrfs: check file extent type before anything
else may have been a suitable fix for this
(https://bugzilla.kernel.org/show_bug.cgi?id=60834) however the kernel
you were using included that fix. Hrm.
** Bug watch added: Linux Kernel Bug Tracker #60834
Looks like we have a bad src page when doing the memcpy():
memcpy:
48 89 f8mov%rdi,%rax
48 89 d1mov%rdx,%rcx
f3a4 rep movsb %ds:(%rsi),%es:(%rdi)
// e.g. rep on *rdi++ = *rsi++
c3
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384711
Title:
btrfs oops on current 3.13
To manage
I have since upgraded that server to the upcoming utopic backport (from
the kernel team PPA) and I haven't been able to reproduce this bug. So
it may well be that there are some btrfs bugfixes in 3.16 which haven't
made it to stable.
--
You received this bug notification because you are a member
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384711
Title:
btrfs oops on current 3.13
To manage
This looks similar to bug 1237833 and bug 1235521 . They were both
reported against Saucy. One bug expired and the other found a
workaround.
Comment #5 in bug 1237833 says: I removed the mount options
compressed and booted into recovery mode performing an filesystem
check. now my problem is
Yes, this is 3.13 with btrfs on a single encrypted block device with
zlib compression.
The oops doesn't appear particularly armful now that I've turned off
panic_on_oops so it's not something I'm willing to sacrifice 2TB of free
space to workaround :)
--
You received this bug notification
