* [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free
@ 2014-02-11 15:36 Martin Steigerwald
2014-02-11 20:50 ` Dave
0 siblings, 1 reply; 5+ messages in thread
From: Martin Steigerwald @ 2014-02-11 15:36 UTC (permalink / raw)
To: linux-btrfs
Hi!
Today I started getting those on 3.14-rc. One core as displayed as 100%
system CPU. I rebooted cause the system didn´t respond consistently to
user input anymore.
I "solved" this by adding about the last 13,5 GiB of free space on this
Intel SSD 320 to it:
merkaba:~> df -hT /home
Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf
/dev/dm-1 btrfs 254G 243G 6,6G 98% /home
merkaba:~> btrfs filesystem resize max /home
Resize '/home' of 'max'
merkaba:~> df -hT /home
Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf
/dev/dm-1 btrfs 267G 243G 21G 93% /home
In the weeks and months before this with BTRFS having about 8-9 GiB free I
already saw btrfs-delalloc thread in D state for longer amounts of time and
the machine locking up for some seconds.
Is that considered a bug or is this somehow expected behaviour when a BTRFS
runs almost full? I´d tend to see this as a bug :)
A scrub completed successfully.
A fstrim on that volume takes very long with indicates highly fragmented free
space, aged filesystem to me as on a freshly created and restored from backup
/home its almost instantly.
Free space figures after adding 13,5 GiB to it:
#> ./btrfs fi df /home
Disk size: 266.99GB
Disk allocated: 254.52GB
Disk unallocated: 12.47GB
Used: 240.90GB
Free (Estimated): 21.89GB (Max: 22.08GB, min: 15.85GB)
Data to disk ratio: 98 %
(seems BTRFS already took another 1 GiB chunk after adding free space to it.)
#> merkaba:… btrfs-progs-unstable> ./btrfs fi disk-usage /home
Data,Single: Size:246.49GB, Used:238.94GB
/dev/dm-1 246.49GB
Metadata,Single: Size:8.00MB, Used:0.00
/dev/dm-1 8.00MB
Metadata,DUP: Size:4.00GB, Used:1.96GB
/dev/dm-1 8.00GB
System,Single: Size:4.00MB, Used:0.00
/dev/dm-1 4.00MB
System,DUP: Size:8.00MB, Used:48.00KB
/dev/dm-1 16.00MB
Unallocated:
/dev/dm-1 12.47GB
Huh, I thought I used Metadata, Single, but maybe I didn´t. So that would be
an option to gain another GiB.
#> ./btrfs device disk-usage /home
/dev/dm-1 266.99GB
Data,Single: 246.49GB
Metadata,Single: 8.00MB
Metadata,DUP: 8.00GB
System,Single: 4.00MB
System,DUP: 16.00MB
Unallocated: 12.47GB
Mount options:
merkaba:~> grep "/home " /proc/mounts
/dev/dm-1 /home btrfs rw,noatime,compress=lzo,ssd,space_cache 0 0
Here is an excerpt of syslog. I copied the whole syslog. So I can pull out more context.
Feb 11 15:56:02 merkaba kernel: [ 2136.447054] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:1621]
Feb 11 15:56:02 merkaba kernel: [ 2136.447057] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtabl
es x_tables cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) binfmt_misc vboxdrv(O) uinput ext4 crc16
mbcache jbd2 sbs sbshc joydev hdaps(O) tp_smapi(O) thinkpad_ec(O) loop firewire_sbp2 fuse ecryptfs dm_crypt snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generi
c snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm thinkpad_acpi nvram intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_m
idi kvm snd_seq_midi_event iwldvm snd_rawmidi mac80211 snd_seq microcode psmouse serio_raw pcspkr snd_seq_device snd_timer iwlwifi snd i2c_i801 cfg80211 lpc_ich mfd_core s
oundcore rfkill ac tpm_tis tpm battery evdev processor btrfs xor raid6_pq md_mod dm_mirror dm_region_hash dm_log dm_mod sg sd_mod sr_mod crc_t10dif cdrom crct10dif_pclmul
crc32_pclmul crc32c_intel ghash_clmulni_intel ahci aesni_intel ehci_pci libahci sata_sil24 aes_x86_64 lrw ehci_hcd gf128mul glue_helper sdhci_pci ablk_helper cryptd libata
sdhci mmc_core scsi_mod firewire_ohci firewire_core crc_itu_t usbcore usb_common thermal e1000e ptp pps_core
Feb 11 15:56:02 merkaba kernel: [ 2136.447128] CPU: 1 PID: 1621 Comm: btrfs-transacti Tainted: G D O 3.14.0-rc1-tp520+ #44
Feb 11 15:56:02 merkaba kernel: [ 2136.447129] Hardware name: LENOVO 42433WG/42433WG, BIOS 8AET63WW (1.43 ) 05/08/2013
Feb 11 15:56:02 merkaba kernel: [ 2136.447131] task: ffff8800371f6140 ti: ffff8800cf36e000 task.ti: ffff8800cf36e000
Feb 11 15:56:02 merkaba kernel: [ 2136.447132] RIP: 0010:[<ffffffff8107035b>] [<ffffffff8107035b>] do_raw_spin_lock+0x15/0x21
Feb 11 15:56:02 merkaba kernel: [ 2136.447138] RSP: 0000:ffff8800cf36fd30 EFLAGS: 00000297
Feb 11 15:56:02 merkaba kernel: [ 2136.447139] RAX: 000000000000c2c1 RBX: ffffffff81113171 RCX: 0000000000000000
Feb 11 15:56:02 merkaba kernel: [ 2136.447140] RDX: 00000000000000c2 RSI: 0000000000008050 RDI: ffff8802123fd340
Feb 11 15:56:02 merkaba kernel: [ 2136.447142] RBP: ffff8800cf36fd30 R08: 000000000001af40 R09: 0000000000000000
Feb 11 15:56:02 merkaba kernel: [ 2136.447143] R10: 0000000000000040 R11: 0000000000000060 R12: ffffea000337b140
Feb 11 15:56:02 merkaba kernel: [ 2136.447144] R13: ffff88021e29af80 R14: 0000000000b98da9 R15: ffff880211212600
Feb 11 15:56:02 merkaba kernel: [ 2136.447145] FS: 0000000000000000(0000) GS:ffff88021e280000(0000) knlGS:0000000000000000
Feb 11 15:56:02 merkaba kernel: [ 2136.447146] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 11 15:56:02 merkaba kernel: [ 2136.447148] CR2: 00007f0ff8006850 CR3: 0000000001a0b000 CR4: 00000000000407e0
Feb 11 15:56:02 merkaba kernel: [ 2136.447149] Stack:
Feb 11 15:56:02 merkaba kernel: [ 2136.447149] ffff8800cf36fd48 ffffffff8144182f ffff8802123fd340 ffff8800cf36fda0
Feb 11 15:56:02 merkaba kernel: [ 2136.447152] ffffffffa029dc76 ffff8800cf36fd90 ffffffffa025244b 0000000000000000
Feb 11 15:56:02 merkaba kernel: [ 2136.447154] 0000003d70cd8000 ffff8800372b1a00 0000003d70cd8000 ffff88020e0b4000
Feb 11 15:56:02 merkaba kernel: [ 2136.447156] Call Trace:
Feb 11 15:56:02 merkaba kernel: [ 2136.447162] [<ffffffff8144182f>] _raw_spin_lock+0x1a/0x1d
Feb 11 15:56:02 merkaba kernel: [ 2136.447182] [<ffffffffa029dc76>] __btrfs_add_free_space+0x47/0x2bd [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447193] [<ffffffffa025244b>] ? block_group_cache_tree_search+0xb7/0xc5 [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447204] [<ffffffffa0256b9c>] unpin_extent_range.isra.54+0xa2/0x194 [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447216] [<ffffffffa02598e2>] btrfs_finish_extent_commit+0xa9/0xb9 [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447229] [<ffffffffa026a46e>] btrfs_commit_transaction+0x6cc/0x83c [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447241] [<ffffffffa0266887>] transaction_kthread+0xf3/0x1a6 [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447253] [<ffffffffa0266794>] ? btrfs_cleanup_transaction+0x429/0x429 [btrfs]
Feb 11 15:56:02 merkaba kernel: [ 2136.447255] [<ffffffff810536e7>] kthread+0xa9/0xb1
Feb 11 15:56:02 merkaba kernel: [ 2136.447257] [<ffffffff8105363e>] ? __kthread_parkme+0x5c/0x5c
Feb 11 15:56:02 merkaba kernel: [ 2136.447259] [<ffffffff8144617c>] ret_from_fork+0x7c/0xb0
Feb 11 15:56:02 merkaba kernel: [ 2136.447261] [<ffffffff8105363e>] ? __kthread_parkme+0x5c/0x5c
Feb 11 15:56:02 merkaba kernel: [ 2136.447262] Code: 14 44 81 48 89 e5 72 0c 31 c0 48 81 ff 34 1b 44 81 0f 92 c0 5d c3 55 b8 00 01 00 00 48 89 e5 f0 66 0f c1 07 0f b6 d4 38 c2 74 0a <8a> 07 38 d0 74 04 f3 90 eb f6 5d c3 55 48 89 e5 f0 ff 07 5d c3
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free
2014-02-11 15:36 [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free Martin Steigerwald
@ 2014-02-11 20:50 ` Dave
2014-02-17 10:35 ` Martin Steigerwald
0 siblings, 1 reply; 5+ messages in thread
From: Dave @ 2014-02-11 20:50 UTC (permalink / raw)
To: Martin Steigerwald; +Cc: linux-btrfs
On Tue, Feb 11, 2014 at 10:36 AM, Martin Steigerwald
<Martin@lichtvoll.de> wrote:
> Today I started getting those on 3.14-rc. One core as displayed as 100%
> system CPU. I rebooted cause the system didn´t respond consistently to
> user input anymore.
Does 3.14-rc1 have Joseph's delayed refs throttling code? I had two
separate machines that exhibited similar symptoms. Chris's for-linus
branch has a fix for this which solved my problems:
https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=for-linus&id=27a377db745ed4d11b3b9b340756857cb8dde07f
--
-=[dave]=-
Entropy isn't what it used to be.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free
2014-02-11 20:50 ` Dave
@ 2014-02-17 10:35 ` Martin Steigerwald
2014-02-17 13:06 ` Chris Mason
0 siblings, 1 reply; 5+ messages in thread
From: Martin Steigerwald @ 2014-02-17 10:35 UTC (permalink / raw)
To: Dave; +Cc: linux-btrfs
Am Dienstag, 11. Februar 2014, 15:50:12 schrieb Dave:
> On Tue, Feb 11, 2014 at 10:36 AM, Martin Steigerwald
>
> <Martin@lichtvoll.de> wrote:
> > Today I started getting those on 3.14-rc. One core as displayed as 100%
> > system CPU. I rebooted cause the system didn´t respond consistently to
> > user input anymore.
>
> Does 3.14-rc1 have Joseph's delayed refs throttling code? I had two
> separate machines that exhibited similar symptoms. Chris's for-linus
> branch has a fix for this which solved my problems:
> https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h=for-linus&id=27a377db745ed4d11b3b9b340756857cb8dde07f
I also got this now under 3.14-rc3 with almost 16 GiB left on heavy KMail /
Akonadi activity. 3.14-rc3 includes above commit.
As I now also got it with more free space and never saw this with upto
3.13 I think this is a regression.
Another trace:
Feb 17 11:22:38 merkaba kernel: [ 1816.159830] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:1618]
Feb 17 11:22:38 merkaba kernel: [ 1816.159834] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs libcrc32c rfcomm
bnep bluetooth 6lowpan_iphc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables cpufreq_userspace cpufreq_
stats cpufreq_powersave cpufreq_conservative pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) binfmt_misc vboxdrv(O) uinput ext4 crc16 mbc
ache jbd2 sbs sbshc hdaps(O) tp_smapi(O) thinkpad_ec(O) loop firewire_sbp2 fuse ecryptfs dm_crypt joydev snd_hda_codec_hdmi snd_hda_codec
_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm intel_rapl x86_pkg_temp_thermal i
ntel_powerclamp thinkpad_acpi nvram coretemp kvm_intel snd_seq_midi kvm snd_seq_midi_event iwldvm mac80211 snd_rawmidi microcode snd_seq
pcspkr psmouse iwlwifi serio_raw snd_seq_device snd_timer lpc_ich cfg80211 mfd_core i2c_i801 snd soundcore rfkill battery ac tpm_tis tpm
evdev processor btrfs xor raid6_pq md_mod dm_mirror dm_region_hash dm_log dm_mod sg sr_mod cdrom sd_mod crc_t10dif hid_generic usbhid hid
crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel firewire_ohci aesni_intel sdhci_pci aes_x86_64 lrw gf128mul sdhci glue_he
lper ablk_helper firewire_core mmc_core crc_itu_t sata_sil24 ahci ehci_pci libahci libata cryptd ehci_hcd scsi_mod usbcore e1000e usb_com
mon ptp pps_core thermal
Feb 17 11:22:38 merkaba kernel: [ 1816.159946] CPU: 1 PID: 1618 Comm: btrfs-transacti Tainted: G O 3.14.0-rc3-tp520 #46
Feb 17 11:22:38 merkaba kernel: [ 1816.159948] Hardware name: LENOVO 42433WG/42433WG, BIOS 8AET63WW (1.43 ) 05/08/2013
Feb 17 11:22:38 merkaba kernel: [ 1816.159951] task: ffff88020ed19850 ti: ffff88020ed14000 task.ti: ffff88020ed14000
Feb 17 11:22:38 merkaba kernel: [ 1816.159953] RIP: 0010:[<ffffffff81070279>] [<ffffffff81070279>] do_raw_spin_lock+0x15/0x21
Feb 17 11:22:38 merkaba kernel: [ 1816.159961] RSP: 0018:ffff88020ed15d30 EFLAGS: 00000297
Feb 17 11:22:38 merkaba kernel: [ 1816.159963] RAX: 0000000000003130 RBX: ffffffff8111239e RCX: 0000000000000000
Feb 17 11:22:38 merkaba kernel: [ 1816.159965] RDX: 0000000000000031 RSI: 0000000000008050 RDI: ffff880036dfc640
Feb 17 11:22:38 merkaba kernel: [ 1816.159967] RBP: ffff88020ed15d30 R08: 000000000001af40 R09: 0000000000000000
Feb 17 11:22:38 merkaba kernel: [ 1816.159969] R10: 0000000000000009 R11: 0000000000000008 R12: ffffea00058e2640
Feb 17 11:22:38 merkaba kernel: [ 1816.159971] R13: ffff88021e29af80 R14: 000000000193ecd5 R15: ffff88021135d900
Feb 17 11:22:38 merkaba kernel: [ 1816.159974] FS: 0000000000000000(0000) GS:ffff88021e280000(0000) knlGS:0000000000000000
Feb 17 11:22:38 merkaba kernel: [ 1816.159976] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 17 11:22:38 merkaba kernel: [ 1816.159978] CR2: 00007fe3963e1000 CR3: 0000000001a0b000 CR4: 00000000000407e0
Feb 17 11:22:38 merkaba kernel: [ 1816.159979] Stack:
Feb 17 11:22:38 merkaba kernel: [ 1816.159981] ffff88020ed15d48 ffffffff81441c6d ffff880036dfc640 ffff88020ed15da0
Feb 17 11:22:38 merkaba kernel: [ 1816.159985] ffffffffa02d8c6c ffff88020ed15d90 ffffffffa028d46a 0000000000000000
Feb 17 11:22:38 merkaba kernel: [ 1816.159989] 0000003fe0a04000 ffff8800cf824c00 0000003fe0a04000 ffff880037232000
Feb 17 11:22:38 merkaba kernel: [ 1816.159993] Call Trace:
Feb 17 11:22:38 merkaba kernel: [ 1816.160000] [<ffffffff81441c6d>] _raw_spin_lock+0x1a/0x1d
Feb 17 11:22:38 merkaba kernel: [ 1816.160031] [<ffffffffa02d8c6c>] __btrfs_add_free_space+0x47/0x2bd [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160048] [<ffffffffa028d46a>] ? block_group_cache_tree_search+0xb7/0xc5 [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160063] [<ffffffffa0291bb9>] unpin_extent_range.isra.54+0xa2/0x194 [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160080] [<ffffffffa02948ff>] btrfs_finish_extent_commit+0xa9/0xb9 [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160097] [<ffffffffa02a548a>] btrfs_commit_transaction+0x6cc/0x83c [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160114] [<ffffffffa02a18a3>] transaction_kthread+0xf3/0x1a6 [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160132] [<ffffffffa02a17b0>] ? btrfs_cleanup_transaction+0x429/0x429 [btrfs]
Feb 17 11:22:38 merkaba kernel: [ 1816.160135] [<ffffffff81053607>] kthread+0xa9/0xb1
Feb 17 11:22:38 merkaba kernel: [ 1816.160138] [<ffffffff8105355e>] ? __kthread_parkme+0x5c/0x5c
Feb 17 11:22:38 merkaba kernel: [ 1816.160142] [<ffffffff8144657c>] ret_from_fork+0x7c/0xb0
Feb 17 11:22:38 merkaba kernel: [ 1816.160145] [<ffffffff8105355e>] ? __kthread_parkme+0x5c/0x5c
Feb 17 11:22:38 merkaba kernel: [ 1816.160147] Code: 18 44 81 48 89 e5 72 0c 31 c0 48 81 ff 72 1f 44 81 0f 92 c0 5d c3 55 b8 00 01 00 00 48 89 e5 f0 66 0f c1 07 0f b6 d4 38 c2 74 0a <8a> 07 38 d0 74 04 f3 90 eb f6 5d c3 55 48 89 e5 f0 ff 07 5d c3
(I will save kern.log in case you need more context)
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free
2014-02-17 10:35 ` Martin Steigerwald
@ 2014-02-17 13:06 ` Chris Mason
2014-02-17 13:19 ` Martin Steigerwald
0 siblings, 1 reply; 5+ messages in thread
From: Chris Mason @ 2014-02-17 13:06 UTC (permalink / raw)
To: Martin Steigerwald, Dave; +Cc: linux-btrfs
On 02/17/2014 05:35 AM, Martin Steigerwald wrote:
> Am Dienstag, 11. Februar 2014, 15:50:12 schrieb Dave:
>> On Tue, Feb 11, 2014 at 10:36 AM, Martin Steigerwald
>>
>> <Martin@lichtvoll.de> wrote:
>>> Today I started getting those on 3.14-rc. One core as displayed as 100%
>>> system CPU. I rebooted cause the system didn´t respond consistently to
>>> user input anymore.
>>
>> Does 3.14-rc1 have Joseph's delayed refs throttling code? I had two
>> separate machines that exhibited similar symptoms. Chris's for-linus
>> branch has a fix for this which solved my problems:
>> https://urldefense.proofpoint.com/v1/url?u=https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/?h%3Dfor-linus%26id%3D27a377db745ed4d11b3b9b340756857cb8dde07f&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=EO6xV8TuAFpGsdd9TfvXbfHYgIFA8%2BKZo1KnQ%2BZ6yzU%3D%0A&s=c9c8769a12e5537247d6ef176681cf19e2bf80fef186ead748b8a2cd2bac6a85
>
> I also got this now under 3.14-rc3 with almost 16 GiB left on heavy KMail /
> Akonadi activity. 3.14-rc3 includes above commit.
>
> As I now also got it with more free space and never saw this with upto
> 3.13 I think this is a regression.
Do we eventually recover or is it stuck like this forever?
-chris
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free
2014-02-17 13:06 ` Chris Mason
@ 2014-02-17 13:19 ` Martin Steigerwald
0 siblings, 0 replies; 5+ messages in thread
From: Martin Steigerwald @ 2014-02-17 13:19 UTC (permalink / raw)
To: Chris Mason; +Cc: Dave, linux-btrfs
Am Montag, 17. Februar 2014, 08:06:50 schrieb Chris Mason:
> On 02/17/2014 05:35 AM, Martin Steigerwald wrote:
> > Am Dienstag, 11. Februar 2014, 15:50:12 schrieb Dave:
> >> On Tue, Feb 11, 2014 at 10:36 AM, Martin Steigerwald
> >>
> >> <Martin@lichtvoll.de> wrote:
> >>> Today I started getting those on 3.14-rc. One core as displayed as 100%
> >>> system CPU. I rebooted cause the system didn´t respond consistently to
> >>> user input anymore.
> >>
> >> Does 3.14-rc1 have Joseph's delayed refs throttling code? I had two
> >> separate machines that exhibited similar symptoms. Chris's for-linus
> >> branch has a fix for this which solved my problems:
> >> https://urldefense.proofpoint.com/v1/url?u=https://git.kernel.org/cgit/li
> >> nux/kernel/git/mason/linux-btrfs.git/commit/?h%3Dfor-linus%26id%3D27a377d
> >> b745ed4d11b3b9b340756857cb8dde07f&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2
> >> FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=EO6xV8TuAFpGsdd9TfvXbfHYgIFA8%2BKZo1Kn
> >> Q%2BZ6yzU%3D%0A&s=c9c8769a12e5537247d6ef176681cf19e2bf80fef186ead748b8a2c
> >> d2bac6a85>
> > I also got this now under 3.14-rc3 with almost 16 GiB left on heavy KMail
> > /
> > Akonadi activity. 3.14-rc3 includes above commit.
> >
> > As I now also got it with more free space and never saw this with upto
> > 3.13 I think this is a regression.
>
> Do we eventually recover or is it stuck like this forever?
Well I got the lock up again and again and watched it for some minutes until I
lost patience and did a hard reboot, so I don´t know actually. Each lockup was
about 22 or 23 seconds.
I will try to trigger that workload again. Since I freed 2-3 more GB, it may
not trigger, but when it does, how long do you suggest me to wait for it to
recover?
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-02-17 13:19 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-11 15:36 [3.14-rc1] BUG: soft lockup - CPU#1 stuck for 22s with 255 GiB BTRFS with only 6 GiB free Martin Steigerwald
2014-02-11 20:50 ` Dave
2014-02-17 10:35 ` Martin Steigerwald
2014-02-17 13:06 ` Chris Mason
2014-02-17 13:19 ` Martin Steigerwald
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).