Re: btrfs lockup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 1, 2016 at 9:51 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
> This is interesting:
>
> Jul 01 11:56:40 kernel: BTRFS info (device nvme0n1p5): relocating
> block group 232511242240 flags 1
>
> a. It's an NVMe drive.
> b. Btrfs at this time is involved in a balance operation of some sort.
The balance operation is one I started manually. It's a coincidence
that it's running at this point and I don't believe it's related to
the lockups because
1) I saw the lockups on a previous baobab scan of my
/var/lib/docker/btrfs/subvolumes when no balance was taking place
and
2) after removing all of docker's subvolumes, the problem has gone away
>
>
> And then what you previously reported, the parts of which I don't follow:
>
> Jul 01 12:00:31 kernel: NMI watchdog: BUG: soft lockup - CPU#0 stuck
> for 22s! [scanner:7121]
I'd guess this is the kernel's protection mechanism to try to recover
when come critical (blocking) thread does not return, looks like it's
essentially killing the process when a watchdog timer expires.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux