similar to: v3.8-rc6: btrfs-transacti Tainted: GF in btrfs_orphan_commit_root

Displaying 20 results from an estimated 400 matches similar to: "v3.8-rc6: btrfs-transacti Tainted: GF in btrfs_orphan_commit_root"

2013 Feb 25
4
WARNING: at fs/btrfs/inode.c:2165 btrfs_orphan_commit_root+0xcb/0xdf()
Is this useful to anyone? Got this after a crash/reboot: if (block_rsv) { WARN_ON(block_rsv->size > 0); <<<<<<<<<<<<<<<<<<<<<< btrfs_free_block_rsv(root, block_rsv); } ------------[ cut here ]------------ WARNING: at fs/btrfs/inode.c:2165 btrfs_orphan_commit_root+0xcb/0xdf() Hardware name: 2429A78 Modules linked in:
2011 Sep 10
12
WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]()
Hi I am hitting this Warning reproducible, the workload is a ceph osd, kernel ist 3.1.0-rc5. Best Regards, martin [ 5472.099766] ------------[ cut here ]------------ [ 5472.099833] WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() [ 5472.099838] Hardware name: MS-96B3 [ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit psmouse sp5100_tco
2011 Nov 09
12
WARNING: at fs/btrfs/inode.c:2198 btrfs_orphan_commit_root+0xa8/0xc0
Hello, I''m seeing a lot of warnings in dmesg with a BTRFS filesystem. I''m using the 3.1 kernel, I found a patch for these warnings ( http://marc.info/?l=linux-btrfs&m=131547325515336&w=2) <http://marc.info/?l=linux-btrfs&m=131547325515336&w=2>, but that patch has already been included in 3.1. Are there any other patches I can try? I''m using
2013 Oct 23
0
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] I''m on Fedora 19 I have run scrub and there are no errors: # btrfs scrub status /home scrub
2013 Jun 11
1
btrfs-transacti:1014 blocked for more than 120 seconds.
Hey, I''ve a 2x4TB RAID1 setup with btrfs on kernel 3.8.0. Under high I/O load (BackupPC dump or writing a large file over gigabit) I get messages in syslog such as the one mentioned in the subject. The full non-logcheck-ignored log is under [1]. A BackupPC dump between the same exact machines onto a 2TB ext4 volume take 90 minutes on average, the process on the btrfs volume took 465
2011 Jul 01
2
Re: [btrfs-transacti] & btrfs-endio-wri] - WAS: Re: [btrfs-delalloc-]
On 06/30/2011 09:13 PM, Josef Bacik wrote: > On 06/30/2011 10:12 AM, Proskurin Kirill wrote: >> On 06/29/2011 08:14 PM, Josef Bacik wrote: >>>> Ok - I upgrade to 2.6.39-2 but it is seems to all things get worse. >>>> Now I see [btrfs-transacti]& btrfs-endio-wri] 80-100% all the time and >>>> io performance looks like lower then before.
2016 Jan 17
2
Need help with changes to 'ScheduleDAGInstrs' on the v3.8 branch
I am stuck trying to adapt my out-of-target implementation to build on SVN head (actually the v3.8 branch, rev #257626). This is currently working on the v3.7.1 sources, but the changes to 'llvm::ScheduleDAGInstrs' have me stumped as to how to revise my implementation to track the changes to this class. Our 'SHAVEAsmScheduler' derives from 'ScheduleDAGInstrs' and uses
2016 Feb 05
2
[LLVM v3.8-rc2] New (tar)balls, please?
HiHo Hans, sorry, but I cannot see any tarballs shipped in [2]? Forgot to upload? Would like to give this pre-release a try on my Ubuntu/precise AMD64 system. Thanks in advance. Regards, - Sedat - [1] http://lists.llvm.org/pipermail/llvm-dev/2016-February/094797.html [2] http://llvm.org/pre-releases/3.8.0/rc2/
2016 Feb 06
2
[LLVM v3.8-rc2] New (tar)balls, please?
On Fri, Feb 5, 2016 at 8:43 AM, Hans Wennborg <hans at chromium.org> wrote: > On Fri, Feb 5, 2016 at 12:48 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> sorry, but I cannot see any tarballs shipped in [2]? >> Forgot to upload? >> >> Would like to give this pre-release a try on my Ubuntu/precise AMD64 system. > > They're not ready yet. It
2017 Jul 25
2
How to migrate x86_sse2_psrl_dq after LLVM v3.8?
Hi LLVM developers, After Remove int_x86_sse2_psll_dq_bs and int_x86_sse2_psrl_dq_bs intrinsics. The builtins aren't used by clang. https://reviews.llvm.org/rL229069 there was no Intrinsic::x86_sse2_psrl_dq any more, then how to migrate: Function *F = Intrinsic::getDeclaration(TheModule, Intrinsic::x86_sse2_psrl_dq); Result = Builder.CreateCall(F,
2016 Feb 08
2
[LLVM v3.8-rc2] New (tar)balls, please?
On Sat, Feb 6, 2016 at 12:34 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Sat, Feb 6, 2016 at 1:55 AM, Hans Wennborg <hans at chromium.org> wrote: >> On Fri, Feb 5, 2016 at 8:43 AM, Hans Wennborg <hans at chromium.org> wrote: >>> On Fri, Feb 5, 2016 at 12:48 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> sorry, but I cannot
2012 Apr 20
44
Ceph on btrfs 3.4rc
After running ceph on XFS for some time, I decided to try btrfs again. Performance with the current "for-linux-min" branch and big metadata is much better. The only problem (?) I''m still seeing is a warning that seems to occur from time to time: [87703.784552] ------------[ cut here ]------------ [87703.789759] WARNING: at fs/btrfs/inode.c:2103
2011 Dec 02
3
[PATCH] Btrfs: protect orphan block rsv with spin_lock
We''ve been seeing warnings coming out of the orphan commit stuff forever from ceph. Turns out it''s because we''re racing with checking if the orphan block reserve is set, because we clear it outside of the spin_lock. So leave the normal fastpath checks where they are, but take the spin_lock and _recheck_ to make sure we haven''t had an orphan block rsv added in
2017 Jun 07
2
Moving from CentOS to GF RPMs
Does anyone have fool-proof documentation for this fool on how to configure repos and what operations to perform to move from the distro RPMs to the GF ones without breaking stuff?
2017 Jun 07
0
Moving from CentOS to GF RPMs
On 07/06/17 13:00, Roger Klorese wrote: > Does anyone have fool-proof documentation for this fool on how to configure > repos and what operations to perform to move from the distro RPMs to the GF > ones without breaking stuff? You'll want to use yum shell to remove the CentOS stock packages and replace them with the GFD ones in a single step. I've documented the process for
2013 Aug 19
11
[RFC PATCH] Btrfs: fix memory leak of orphan block rsv
When adding orphans to an inode''s root, we start a transaction for that root that when ended in several places such as for example extent-tree.c:btrfs_remove_block_group(), inode.c:btrfs_unlink() and inode.c:btrfs_evict_node(), doesn''t result in a commit, that is, inode.c:btrfs_orphan_commit_root() doesn''t get called (via transaction.c:commit_fs_roots()). The respective
2009 Nov 13
6
[Bug 25072] New: KMS Gf 6200 - wrong fb and X resolution
http://bugs.freedesktop.org/show_bug.cgi?id=25072 Summary: KMS Gf 6200 - wrong fb and X resolution Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2006 Jan 12
1
dm_mod: no version for "struct_module" found: kernel tainted
I used the xensource install script for RHEL4 and after trying to boot on the new kernel the system just continually rebooted. I appended a noreboot to the xen line and now i''m seeing the following... Freeing unused kernel memory: 184k freed dm_mod: no version for "struct_module" found: kernel tainted. device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
2006 Oct 31
0
6303398 lseek(., offset, SEEK_HOLE) asserts with tainted offsets
Author: perrin Repository: /hg/zfs-crypto/gate Revision: 39a587f9abc6273f4188996d9e4de4e0ea126efa Log message: 6303398 lseek(., offset, SEEK_HOLE) asserts with tainted offsets Files: update: usr/src/uts/common/fs/ufs/ufs_bmap.c
2007 Oct 02
2
Tainted kernel module?
Hello, Some time ago, I noticed that whilst I had upgraded to Xen 3.1 (kernel 2.6.18-xen), I''d forgot to upgrade the paravirt DomU .cfg kernels from 2.6.16-xen to reflect this. So, I upgraded the DomU kernels & ran into issues with mounting devices, and the ext3 module not being available. After a bit of faffing about, I managed to sort this out and load the ext3 module.