Re: btrfs-convert --no-datasum & btrfs check: check_owner_ref: BUG_ON `rec->is_root` triggered, value 1

2017-07-02 Thread Lakshmipathi.G
Looked like I missed few patch. After checking with latest branch. Its working. Cheers, Lakshmipathi.G On Sun, Jul 2, 2017 at 7:30 PM, Lakshmipathi.G wrote: > Hi. > While using btrfs-convert with '--no-datasum' option & running btrfs > check crashes: > > steps:

Re: [PATCH v3 2/4] btrfs-progs: lowmem check: Fix false alert about referencer count mismatch

2017-07-02 Thread Lu Fengqi
On Sun, Jul 02, 2017 at 03:50:31PM +0200, Henk Slager wrote: > >With this patch applied to v4.11, I ran: ># btrfs check -p --mode lowmem /dev/mapper/smr > >no 'referencer count mismatch' anymore, but likely due to other hidden >corruption, the check took more time than I had planned, so after 5

WARN_ON(rc->block_group->reserved > 0)

2017-07-02 Thread Adam Borowski
Hi! I got a WARN_ON(rc->block_group->reserved > 0) on for-4.13 -- just letting you guys know, as there were related fixes recently. I'm on late 4.12-rc7 + kdave/for-4.13-part1 + v4 of Qu's chunk check + unrelated. Filesystem has ssd,compress=lzo. Jul 3 02:01:56 umbar kernel: [169904.878882]

Re: Btrfs check reports errors, filesystem seems fine

2017-07-02 Thread Qu Wenruo
At 07/01/2017 07:59 PM, Filippe LeMarchand wrote: Hello everyone. I have an btrfs root partition on Intel 530 ssd, which mounts without errors and seem to work fine, but `btrfs check` gives me foloowing output (and --repair doesn't remove errors): enabling repair mode Checking filesystem

Re: Deleting mounted subvolumes

2017-07-02 Thread Hans van Kranenburg
On 07/02/2017 11:33 PM, Pete wrote: > I found that I can delete a mounted subvolume using: > btrfs subvolume delete > > This works. Is this the intended action? To me it would seem like a > warning and the command exiting would make sense? Yes, you can do that. It's a bit similar to the fact

Deleting mounted subvolumes

2017-07-02 Thread Pete
I found that I can delete a mounted subvolume using: btrfs subvolume delete This works. Is this the intended action? To me it would seem like a warning and the command exiting would make sense? Pete -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a

Unable to mount filesystem

2017-07-02 Thread Wictor Lund
Hi!   I cannot mount my filesystem anymore. The problem started with it going into read-only mode after the filesystem accidentally became full. At some point the system crashed and after that I got this error. Is it possible to recover the filesystem or at least recover some data from it? Here

btrfs-convert --no-datasum & btrfs check: check_owner_ref: BUG_ON `rec->is_root` triggered, value 1

2017-07-02 Thread Lakshmipathi.G
Hi. While using btrfs-convert with '--no-datasum' option & running btrfs check crashes: steps: mkfs.ext4 tests/t1 mount tests/t1 /data cp -r *.c /data umount /data ./btrfs-convert --no-datasum tests/t1 ./btrfs check tests/t1 cmds-check.c:5488: check_owner_ref: BUG_ON `rec->is_root` triggered,

Re: [PATCH v3 2/4] btrfs-progs: lowmem check: Fix false alert about referencer count mismatch

2017-07-02 Thread Henk Slager
On Mon, Jun 26, 2017 at 12:37 PM, Lu Fengqi wrote: > The normal back reference counting doesn't care about the extent referred > by the extent data in the shared leaf. The check_extent_data_backref > function need to skip the leaf that owner mismatch with the root_id. >