Hi Sebastiann,
On Mon, Jan 05, 2015 at 12:01:06AM +, Andy Whitcroft wrote:
On Sun, Jan 04, 2015 at 07:05:24PM +0100, Sebastiaan L. Zoutendijk wrote:
Control: submitter -1 !
Hello Joe,
On Sat 3 Jan 2015 at 16:02:12 -0500, Joseph Salisbury wrote:
Would it be possible for you to
Control: submitter -1 !
Hello Joe,
On Sat 3 Jan 2015 at 16:02:12 -0500, Joseph Salisbury wrote:
Would it be possible for you to also open a bug in Launchpad for
this? It can be done by running the following from a terminal:
ubuntu-bug linux
Thank you for your directions, but I fear I
On Sun, Jan 04, 2015 at 07:05:24PM +0100, Sebastiaan L. Zoutendijk wrote:
Control: submitter -1 !
Hello Joe,
On Sat 3 Jan 2015 at 16:02:12 -0500, Joseph Salisbury wrote:
Would it be possible for you to also open a bug in Launchpad for
this? It can be done by running the following from
On 12/23/2014 09:34 AM, Sebastiaan L. Zoutendijk wrote:
Dear Ubuntu Kernel Team,
I would like to request an upstream patch [1] to be applied to the 3.16
kernel. This patch prevents Btrfs filesystems from going readonly when
a subvolume ID is reused but the corresponding qgroup wasn't destroyed
Control: found -1 3.16.7-ckt2-1
On Thu 27 Nov 2014 at 19:41:20 +0100, Sebastiaan L. Zoutendijk wrote:
On kernel 3.16.7-2, which is in sid and jessie, I have also been able to
reproduce the bug, with the same kind of error messages in dmesg.
Applying the patch again solved the issue. As I
Dear Ubuntu Kernel Team,
I would like to request an upstream patch [1] to be applied to the 3.16
kernel. This patch prevents Btrfs filesystems from going readonly when
a subvolume ID is reused but the corresponding qgroup wasn't destroyed
when the original subvolume was deleted. This patch has
Control: found -1 3.16.7-2
On Wed 26 Nov 2014 at 15:12:59 +0100, Bas Zoutendijk wrote:
Subsequently, I applied the patch to the Debian sources of this kernel
and rebuilt it. I could not reproduce the bug on this patched kernel,
so the patch seems to work. Maybe I can try this with an
Control: found 3.16.5-1~bpo70+1
On Fri 14 Nov 2014 at 17:51:17 +0100, Sebastiaan L. Zoutendijk wrote:
There is a patch for this bug upstream [1], which has been applied to
3.17 [2]. As far as I know, it wasn't applied to 3.16. I have not
tried this patch for reasons of time, but I can if you
Source: linux
Version: 3.16.3-2~bpo70+1
Severity: important
Tags: patch, upstream
Dear Maintainers,
[This bug is actually upstream, and I originally intended to send this
report upstream as well, but 3.16 has gone EOL before I got the time to
do this. I hope the Debian maintainers will be able
9 matches
Mail list logo
