On Fri, May 29, 2015 at 11:14:13PM +0200, Markus Schauler wrote:
Hi,
I'm having an issue with Btrfs on an opensuse Tumbleweed system using
kernel 4.0.4-1
Here's what happened:
I use the snapper tool to create periodic snapshots of the root FS
After having problems with an update, I
Since commit bafc9b754f75 (vfs: More precise tests in d_invalidate),
mounted subvolumes can be deleted because d_invalidate() won't fail.
However, we run into problems when we attempt to delete the default
subvolume while it is mounted as the root filesystem:
# btrfs subvol list /
On Fri, Feb 27, 2015 at 8:26 AM, Qu Wenruo quwen...@cn.fujitsu.com wrote:
Before this patch, qgroup show won't check btrfs qgroup status, so even
the INCONSISTENT flags is set, user is not aware of it.
This patch will include BTRFS_QGROUP_STATUS_ITEM in the search range and
check the flag, if
Can anyone help me with the next steps? Any chance to recover the data?
Mit freundlichen Grüßen/Kind regards
Felix Koop
Felix Koop f...@fkoop.de hat am 26. Mai 2015 um 22:15 geschrieben:
Qu Wenruo quwen...@cn.fujitsu.com hat am 26. Mai 2015 um 07:56
geschrieben:
Label: none
Currently BTRFS allows you to make bad choices of data and
metadata levels. For example -d raid1 -m raid0 means you can
only use half your total disk space, but will loose everything
if 1 disk fails. It should give a warning in these cases.
When making a filesystem check that metadata mode is at
When the btrfs on a device is overwritten with a new btrfs (mkfs),
the old btrfs instance in the kernel becomes stale. So with this
patch if kernel finds device is overwritten then delete the stale
fsid/uuid.
Signed-off-by: Anand Jain anand.j...@oracle.com
---
v5.1-v5.2: accepts David's review
Hi David, Thanks for comments, more below..
On 05/27/2015 07:34 PM, David Sterba wrote:
On Fri, May 22, 2015 at 11:33:48PM +0800, Anand Jain wrote:
+void btrfs_free_stale_device(struct btrfs_device *cur_dev)
+{
+ int del = 0;
+ struct btrfs_fs_devices *fs_devs;
+ struct
