On Tue, Mar 05, 2013 at 04:59:05AM -0700, Stefan Behrens wrote: > On Mon, 4 Mar 2013 14:31:37 -0500, Chris Mason wrote: > > On Mon, Mar 04, 2013 at 10:24:39AM -0700, Stefan Behrens wrote: > >> Just ran the following command sequence and got lots of WARNINGs. > >> The issue is reproducible. > >> The box was running the cmason/for-linus that made it into Linux 3.9 RC1. > >> > >> #!/bin/sh > >> mkfs.btrfs -f /dev/sdl /dev/sdk -m raid1 -d raid1 -l 16384 > >> mount /dev/sdl /mnt > >> dd if=/dev/urandom of=/mnt/urandom.1GB bs=10M count=100 & > >> dd if=/dev/zero of=/mnt/zero.4GB bs=10M count=400 & > >> (cd ~/kernel-src; tar cf - fs) | (cd /mnt && tar xf -) > >> wait > >> > >> ((cd ~/kernel-src; tar cf - drivers) | (cd /mnt && tar xf -)) & > >> sleep 5 > >> btrfs fi balance start /mnt > > > > This doesn't look new, are you able to trigger it with an older kernel? > > > > git bisect identifies the following post v3.8 commit to be the one:
Is your dd running fallocate? Trying to figure out how this is related. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
