serious problems with softlockups on kernel 3.11.9

After each reboot everything works until I try to mount btrfs filesystem, then computer hangs for long periods of time. Before kernel update things were working right. I'm using Fedora 19. Follows dmesg output from moment when I try to mount btrfs filesystem in dmcrypt: [ 158.994656] xor:

Soft lockup btrfs-transacti:680

When I try to umount btrfs filesystem I get always this error with kernel 3.11.4 and 3.11.3, but I can mount and umount without error on kernel 3.11.2. Exact error messages are: BUG: soft lockup - CPU#0 stuck for 23s! [btrfs-transacti:680] BUG: soft lockup - CPU#1 stuck for 23s! [umount:1575]

Re: [RFC][PATCH 1/2] Btrfs: try to allocate new chunks with degenerated profile

On Wed, Jan 18, 2012 at 13:41, Hugo Mills h...@carfax.org.uk wrote: On Wed, Jan 18, 2012 at 11:12:20AM +0100, Jan Schmidt wrote: On 17.01.2012 21:58, Chris Mason wrote: These two didn't make my first pull request just because I wanted to get something out the door.  I'll definitely have them

Re: Why does Btrfs allow raid1 with mismatched drives? Also: How to look behind the curtain

On Thu, Jan 5, 2012 at 13:26, Fabian Zeindl fabian.zei...@gmail.com wrote: On Jan 5, 2012, at 11:39 , Martin Steigerwald wrote: Allocating as many chunks as can fit across the drives is also pretty clear to me. So if BTRFS can´t allocate a new chunk on two devices, its full. To me it seems

kernel BUG at fs/btrfs/inode.c:3037

Hello, I'm hitting following kernel bug when trying to rmdir empty directory from btrfs filesystem. I'm on Linux 3.1.1-1.fc16.i686.PAE. rmdir ends with segfault. I have found similar problem in this mailing list but not the same one so I'm reporting it. [ 281.284923] btrfs: could not do orphan

kernel bug

] btrfs_delayed_update_inode+0xdf/0xe1 [btrfs] SS :ESP 0068:e69ebd60 [ 4982.974411] ---[ end trace 9cf7abc81c235a01 ]--- Thanks Roman Kapusta -- 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

Re: kernel bug

I forgot to mention that every process writing to btrfs partition hanged and cannot be killed by 'kill -9', btrfs filesystem cannot be unmounted. -- 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

kerenl bug after btrfs resize (reduce size)

f8 e8 22 c8 ff ff Sep 19 13:01:50 cyro kernel: [13412.118047] EIP: [f88584af] build_backref_tree+0x3de/0xac4 [btrfs] SS:ESP 0068:f521bc04 Sep 19 13:01:50 cyro kernel: [13412.118281] ---[ end trace 209501ab2f807f91 ]--- Thanks Roman Kapusta -- To unsubscribe from this list: send the line

Re: kerenl bug after btrfs resize (reduce size)

On Mon, Sep 19, 2011 at 14:38, Hugo Mills h...@carfax.org.uk wrote: On Mon, Sep 19, 2011 at 02:24:55PM +0200, Roman Kapusta wrote: After running 'btrfs fi resize' I got following error, fortunately, it looks that filesystem is ok. I was changing filesystem size from 256 GB to 192 GB (reducing

btrfs always writes something after sync

to 216050353 (total 6607 milliseconds) and this repeats after each 'sync' with similar totals My system is Fedora 15 kernel 2.6.40.3-2.fc15.i686.PAE (this is should be 3.0.3 with some Fedora patches) Thanks Roman Kapusta -- To unsubscribe from this list: send the line unsubscribe linux-btrfs

btrfs raid health status

I'm playing with mkfs.btrfs -m raid1 -d raid1. I put som data there and now I write random data on one of physical disks directly. Filesystem and file contents looks fine but I cannot see any errors, is there any way to see that one disk from raid1 is failing? Thanks Roman Kapusta

Space used by snapshot

EXCLUDING all space shared by other subvolumes Currently I can use only du, which is not reporting what I want to know. Regards Roman Kapusta -- 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

Re: Space used by snapshot

On Thu, Feb 17, 2011 at 12:54, Hubert Kario h...@qbs.com.pl wrote: On Thursday, February 17, 2011 12:13:53 Roman Kapusta wrote: Hello all, Is there any way how to obtain information how much space is physically allocated by given subvolume? I cannot find any. I'm interested in two values

Re: some issues with lots of snapshots

On Fri, Oct 29, 2010 at 00:03, Pat Regan theh...@patshead.com wrote: On Wed, 27 Oct 2010 10:39:48 +0200 Xavier Nicollet nicol...@jeru.org wrote: Le 26 octobre 2010 à 15:15, Pat Regan a écrit: I turned off the 5-minute snapshots and I'm now just keeping 4 weekly, 7 daily, and 24 hourly

snapshot consumed space

should look somewhere else to find what is consuming my disk space. Roman Kapusta -- 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