Your message dated Sat, 24 Apr 2021 11:04:17 +0200 with message-id <E1laECj-001JJx-9I@hullmann.westfalen.local> and subject line Closing this bug has caused the Debian Bug report #696945, regarding kernel BUG at [...]/fs/btrfs/transaction.c:1337! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 696945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696945 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: btrfs bug?
- From: Γιώργος Πάλλας <gpall@ccf.auth.gr>
- Date: Thu, 24 May 2012 08:40:10 +0300
- Message-id: <4FBDC9BA.6070800@ccf.auth.gr>
Package: linux-image-3.2.0-2-amd64 Hello!I'm sending this bug report using a simple email because the reportbug tool always fails due to timeouts when used on the kernel (probably because there are many bugs).I'm using a fully updated squeeze with 3.2.0-2-amd64.I guess the whole thing happened due to a (temporary?) fail of the disk, but anyway btrfs dumped some things which you may find interesting.In your disposal for any additional data. Giorgos PallasAttachment: btrfsBug.txt.bz2
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: 696945-done@bugs.debian.org
- Subject: Closing this bug
- From: jmm@debian.org
- Date: Sat, 24 Apr 2021 11:04:17 +0200
- Message-id: <E1laECj-001JJx-9I@hullmann.westfalen.local>
This bug was filed for a very old kernel. If you can reproduce it with - the current version in unstable/testing - the latest kernel from buster.backports please reopen the bug, see https://www.debian.org/Bugs/server-control
--- End Message ---