On Wed, Oct 23, 2013 at 01:04:11AM +0900, Tomasz Chmielewski wrote: > Actually it's still working. > > If I run this: > > # btrfs scrub status /mnt/lxc1 > scrub status for 8d08ad6d-4543-4fe5-8b1b-640dc1423d41 > scrub started at Tue Oct 22 09:53:34 2013, running for 22101 seconds > total bytes scrubbed: 2.61TB with 0 errors This looks promising. > However, it's not possible to work with this system via SSH, because > these keep popping up few times every minute: Probably only some of the files that get accessed during ssh login is corrupted, but the scrub does not get far enough to let you know the filenames. You can try to look into 'lsof' output which files are open by sshd or it's children. > kernel:[22219.117012] BUG: soft lockup - CPU#2 stuck for 23s! [btrfs:5673] > kernel:[22247.100515] BUG: soft lockup - CPU#0 stuck for 23s! [btrfs:5674] > kernel:[22247.100519] BUG: soft lockup - CPU#2 stuck for 23s! [btrfs:5673] Cpus 0 and 2 are stuck and every other attempt to access the broken files will pin another cpu. -- 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
