Hello,
-- Původní e-mail --
Od: Nikolay Borisov
Komu: Zdenek Sojka , linux-btrfs@vger.kernel.org
Datum: 11. 9. 2019 10:16:49
Předmět: Re: possible circular locking dependency detected
(sb_internal/fs_reclaim)
On 11.09.19 г. 10:54 ч., Zdenek Sojka wrote:
> He
On 11.09.19 г. 10:54 ч., Zdenek Sojka wrote:
> Hello,
>
> this is my fourth attempt to post this message to the mailing list; this
> time, without any attached kernel config (because it has over 100KiB). I also
> tried contacting the kernel btrfs maintainers directly by email, but they
> p
t -O2 (gcc-8.3.0).
Please let me know if I can provide any more information.
Best regards,
Zdenek Sojka
The dmesg warning I recently triggered:
[30560.303721] ==
[30560.303722] WARNING: possible circular locking dependency detected
[30560.3037
] ==
[ 233.710303] WARNING: possible circular locking dependency detected
[ 233.710574] 4.17.0+ #4 Not tainted
[ 233.710757] --
[ 233.711006] kswapd0/749 is trying to acquire lock:
[ 233.711244] e4661f1f (&delayed_node->mutex){+.
Hi,
after scrub start, scrub cancel, umount, mount of a two disk raid1
(data + metadata):
[12999.229791] ==
[12999.236029] WARNING: possible circular locking dependency detected
[12999.242261] 4.14.35 #36 Not tainted
[12999.245806
trfs issue:
> >
> > [ 94.192907] ======
> > [ 94.192911] WARNING: possible circular locking dependency detected
> > [ 94.192917] 4.15.0-0.rc2.git2.1.fc28.x86_64 #1 Not tainted
>
> I'm not seeing it so far with 4.15.0-0.rc
94.192911] WARNING: possible circular locking dependency detected
> [ 94.192917] 4.15.0-0.rc2.git2.1.fc28.x86_64 #1 Not tainted
I'm not seeing it so far with 4.15.0-0.rc3.git0.1.fc28.x86_64+debug.
--
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe lin
Hi,
Jut done upgrade on my laptop to the latest Fedora rawhide packages.
After reboot and login in dmesg I found logged btrfs issue:
[ 94.192907] ==
[ 94.192911] WARNING: possible circular locking dependency detected
[ 94.192917] 4.15.0-0
Raw oops dump:
[ 173.695170] ==
[ 173.695175] WARNING: possible circular locking dependency detected
[ 173.695181] 4.14.0-0.rc2.git3.1.fc28.x86_64 #1 Tainted: G OE
[ 173.695186
On Thu, 09 Aug 2012 18:44:12 +0200, Stefan Behrens wrote:
> On Thu, 9 Aug 2012 18:01:57 +0200, David Sterba wrote:
>> On Thu, Aug 09, 2012 at 05:36:54PM +0200, Stefan Behrens wrote:
>>> Aug 9 16:02:21 qvarne kernel: [ 543.479460] -> #2
>>> (&fs_info->cleaner_mutex){+.+...}:
>>> Aug 9 16:02:21 q
On Thu, 9 Aug 2012 18:01:57 +0200, David Sterba wrote:
> On Thu, Aug 09, 2012 at 05:36:54PM +0200, Stefan Behrens wrote:
>> Aug 9 16:02:21 qvarne kernel: [ 543.479460] -> #2
>> (&fs_info->cleaner_mutex){+.+...}:
>> Aug 9 16:02:21 qvarne kernel: [ 543.541341][]
>> lock_acquire+0x95/0x1
On Thu, Aug 09, 2012 at 05:36:54PM +0200, Stefan Behrens wrote:
> Aug 9 16:02:21 qvarne kernel: [ 543.479460] -> #2
> (&fs_info->cleaner_mutex){+.+...}:
> Aug 9 16:02:21 qvarne kernel: [ 543.541341][]
> lock_acquire+0x95/0x150
> Aug 9 16:02:21 qvarne kernel: [ 543.612269][]
d /mnt2; tar xf -) 2>/dev/null
echo fails with ENOSPC after some seconds
umount /mnt2
mount /dev/sdo /mnt2
btrfs dev add /dev/sdq /mnt2
btrfs dev del /dev/sdp /mnt2
echo causes the 'INFO: possible circular locking dependency detected'
echo fails with 'ERROR: error removing the dev
On Thu, Nov 20, 2008 at 05:00:15PM +0100, Diego Calleja wrote:
> I got this lockdep warning while running tiobench on a clean btrfs filesystem
> with the latest code available (commit
> 2c41b36dd2f9fb5dee150f20c84895496e0642f2)
> But it was a purely read-only workload: only root could write to the
"denied permission" errors.
[ 5177.201587] ===
[ 5177.201594] [ INFO: possible circular locking dependency detected ]
[ 5177.201601] 2.6.28-rc5-dirty #7
[ 5177.201604] ---
[ 5177.201
15 matches
Mail list logo
