Re: [PATCH] btrfs-progs: btrfs-convert: Add larger device support

Hi Qu, Seems like its a known issue with older bitmaps. http://linux-ext4.vger.kernel.narkive.com/wkNbJe0b/patch-debugfs-open-with-ext2-flag-64bits Cheers. Lakshmipathi.G On Fri, Apr 28, 2017 at 09:48:10AM +0800, Qu Wenruo wrote: > > > At 04/28/2017 09:27 AM, Qu Wenruo wrote: > >At 04/27/2017

Re: File system corruption, btrfsck abort

On Tue, Apr 25, 2017 at 11:50 AM, Christophe de Dinechin wrote: > > The last filesystem corruption is documented here: > https://bugzilla.redhat.com/show_bug.cgi?id=1444821. The dmesg log is in > there. And also from the bug: >How reproducible: Seen at least 4 times on 3

Re: File system corruption, btrfsck abort

At 04/26/2017 01:50 AM, Christophe de Dinechin wrote: Hi, I”ve been trying to run btrfs as my primary work filesystem for about 3-4 months now on Fedora 25 systems. I ran a few times into filesystem corruptions. At least one I attributed to a damaged disk, but the last one is with a brand

[GIT PULL] Btrfs

Hi Linus, We have one more for btrfs: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 This is dropping a new WARN_ON from rc1 that ended up making more noise than we really want. The larger fix for the underflow got delayed a bit and it's better for now

Re: No space left on device when doing "mkdir"

On Thu, Apr 27, 2017 at 10:46 AM, Gerard Saraber wrote: > After a reboot, I found this in the logs: > [ 322.510152] BTRFS info (device sdm): The free space cache file > (36114966511616) is invalid. skip it > [ 488.702570] btrfs_printk: 847 callbacks suppressed > > > > On

Subvolume copy fails with "ERROR: empty stream is not considered valid"

I've just reported a bug (https://bugzilla.kernel.org/show_bug.cgi?id=195597) that hit me after recent update of btrfs-progs. It seems to be a false-positive that resulted from the changes that aimed to fix another issue. Short version of it is following: root@nazar-pc:~# /bin/btrfs send

Re: [PATCH v6 2/2] btrfs: scrub: Fix RAID56 recovery race condition

On 2017-04-26 02:13, Qu Wenruo wrote: > > > At 04/26/2017 01:58 AM, Goffredo Baroncelli wrote: >> I Qu, >> >> I tested these two patches on top of 4.10.12; however when I >> corrupt disk1, It seems that BTRFS is still unable to rebuild >> parity. >> >> Because in the past the patches set V4

Re: No space left on device when doing "mkdir"

After a reboot, I found this in the logs: [ 322.510152] BTRFS info (device sdm): The free space cache file (36114966511616) is invalid. skip it [ 488.702570] btrfs_printk: 847 callbacks suppressed On Thu, Apr 27, 2017 at 10:18 AM, Gerard Saraber wrote: > no snapshots and

Re: No space left on device when doing "mkdir"

no snapshots and no qgroups, just a straight up large volume. shrapnel gerard-store # btrfs fi df /home/exports Data, RAID1: total=20.93TiB, used=20.86TiB System, RAID1: total=32.00MiB, used=3.73MiB Metadata, RAID1: total=79.00GiB, used=61.10GiB GlobalReserve, single: total=512.00MiB,

Re: File system corruption, btrfsck abort

> On 27 Apr 2017, at 16:58, Christophe de Dinechin wrote: > >> On 25 Apr 2017, at 19:50, Christophe de Dinechin wrote: > >> The cause of the abort is that we call set_extent_dirty from >> check_extent_refs with rec->max_size == 0. I’ve instrumented

Re: File system corruption, btrfsck abort

> On 25 Apr 2017, at 19:50, Christophe de Dinechin wrote: > The cause of the abort is that we call set_extent_dirty from > check_extent_refs with rec->max_size == 0. I’ve instrumented to try to see > where we set this to 0 (see >

Re: No space left on device when doing "mkdir"

On Thu, 27 Apr 2017 08:52:30 -0500 Gerard Saraber wrote: > I could just reboot the system and be fine for a week or so, but is > there any way to diagnose this? `btrfs fi df` for a start. Also obligatory questions: do you have a lot of snapshots, and do you use qgroups?

No space left on device when doing "mkdir"

Hi everyone, I'm running: Linux shrapnel 4.11.0-rc8 #2 SMP Mon Apr 24 08:47:46 CDT 2017 x86_64 Intel(R) Xeon(R) CPU 5140 @ 2.33GHz GenuineIntel GNU/Linux 32GB memory There's a kworker taking 100% cpu: 30856 root 20 0 0 0 0 R 100.0 0.0 19:26.90 kworker/u8:0 and writing

Error during backup to zlib-compressed btrfs-volume (kernel stack frame pointer at ffff9f1f433ebf50 in kworker/u8:7:6702 has bad value (null))

Hi, During a backup to an external USB3 hdd with the following mount options "rw,nosuid,nodev,relatime,compress-force=zlib,space_cache,subvolid=5,subvol=/,user" runnning linux-4.10.11-200.fc25.x86_64 I got the backtrace at the end of the email. Best regards, Clemens [ 3723.511132] WARNING:

[PATCH] btrfs-progs: btrfs-convert: Add larger device support

Bug: Fail to convert 22TB EXT4 to BTRFS https://bugzilla.kernel.org/show_bug.cgi?id=194795 Signed-off-by: Lakshmipathi.G --- convert/source-ext2.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/convert/source-ext2.c