Re: bug when removing device

I have sent a set of patches that address bugs like this. I applied the V2 patchset to kernel-v2.6.32 (actually, I applied them to btrfs-unstalbe, took a kernel-v2.6.32 and replaced its btrfs with the patched one in btrfs-unstable), and did the test, then got: $ sudo btrfs device del

Re: bug when removing device

On Thu, Apr 29, 2010 at 2:11 AM, sniper s3c2...@gmail.com wrote: Hi all, I tried to reproduce the bug reported by Tomas Thiemel (http://www.spinics.net/lists/linux-btrfs/msg04818.html) with loop device, and caught a bug report. kernel: v2.6.34-rc5-279-g1600f9d btrfs_progs:

[PATCH] btrfs: fix shadows sparse warning

Fix sparse warnings: fs/btrfs/free-space-cache.c:1078:40: warning: symbol 'node' shadows an earlier one fs/btrfs/free-space-cache.c:1230:32: warning: symbol 'node' shadows an earlier one Signed-off-by: Bill Pemberton wf...@virginia.edu --- fs/btrfs/free-space-cache.c |4 +--- 1 files

Updating RAID[56] support

I've been looking again at the RAID5/RAID6 support, and updated the tree at git://git.infradead.org/users/dwmw2/btrfs-raid56.git#merged At the moment, we limit writes to a single disk's worth at a time, which means we _always_ do the read-calculateparity-write cycle and suffer the traditional

Undo mkfs.btrfs

I accidentally did a mkfs.btrfs on a used btrfs filesystem, which now shows as empty. Is there any way to get the data back? -- 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

Segmentation fault on partition mount

My distro: Archlinux Kernel: 2.6.34-rc5, 2.6.33.3 I has 522 Gib btrfs partition and. While I was checking out chromium source, free space on my /home btrfs partition was about 20 Gib. Then I received message not enough free space (but there was enough of it). And even after btrfsck I always get

RE: btrfs balance failed and kernel oops'd

Hi Justin, I use Gentoo and I had Kernel OOPS, too (with 2.6.33), until I upgraded to the lastest not stable kernel - 2.6.34-rc5. Now (almost) everything works OK. I also had to re-format partition because there is one small problem: When you add disk (in single mode) and then you rebalance

Re: Updating RAID[56] support

On Thu, Apr 29, 2010 at 07:06:06PM +0100, David Woodhouse wrote: I've been looking again at the RAID5/RAID6 support, and updated the tree at git://git.infradead.org/users/dwmw2/btrfs-raid56.git#merged At the moment, we limit writes to a single disk's worth at a time, which means we _always_

Re: Segmentation fault on partition mount

On Fri, Apr 30, 2010 at 11:26:16AM -0700, Ilya Shestopalov wrote: My distro: Archlinux Kernel: 2.6.34-rc5, 2.6.33.3 I has 522 Gib btrfs partition and. While I was checking out chromium source, free space on my /home btrfs partition was about 20 Gib. Then I received message not enough free

Re: Updating RAID[56] support

- David Woodhouse dw...@infradead.org skrev: I've been looking again at the RAID5/RAID6 support, and updated the tree at git://git.infradead.org/users/dwmw2/btrfs-raid56.git#merged At the moment, we limit writes to a single disk's worth at a time, which means we _always_ do the

Re: Updating RAID[56] support

On Fri, 2010-04-30 at 14:39 -0400, Josef Bacik wrote: It seems to work, and recovery is successful when I mount the file system with -oro,degraded. But in read-write mode it'll oops (even without the below patch) because it's trying to _write_ to the degraded RAID6. Last time I was testing

[no subject]

Bug message: Btrfs loaded device fsid 694983118c1865e7-ed2ca7537412e6ae devid 1 transid 73188 /dev/sda5 [ cut here ] kernel BUG at fs/btrfs/tree-log.c:809! invalid opcode: [#1] PREEMPT SMP last sysfs file:

Re: Re: Segmentation fault on partition mount

Bug message: Btrfs loaded device fsid 694983118c1865e7-ed2ca7537412e6ae devid 1 transid 73188 /dev/sda5 [ cut here ] kernel BUG at fs/btrfs/tree-log.c:809! invalid opcode: [#1] PREEMPT SMP last sysfs file: