Description: I'm not sure if the issue is exactly with the kernel-space modules for nilfs2 or with the userland. I have a Seagate 4TB backup drive that I have partitioned with GPT, my system is definitely new enough to read GPT partition information, encrypted with LUKS (this was going to be my backup drive), and formatted with nilfs2 (for automatic pseudo-versioning via checkpoints/snapshots). Every time I do something that triggers a write operation (running touch/cp/mv/etc) on this drive I notice that my system becomes unresponsive with any task that requires disk I/O, this doesn't always happen immediately after running a command but can be triggered by calling sync. I haven't found a way to recover from this other than rebooting the whole system, in which case if I unlock the external hard drive and mount it the drive appears empty as the write operation failed.


Additional info:
* linux: 4.8.10-1 cryptsetup: 1.7.3-1 nilfs-utils: 2.2.6-1
* Output of dmesg attached


Steps to reproduce:
# cryptsetup luksFormat /dev/sdxN (Replace x with drive letter and N with partition)
# cryptsetup luksOpen /dev/sdxN test
(insert password to decrypt drive)
# mkfs.nilfs2 /dev/mapper/test
# mount /dev/mapper/test /mnt
# touch /mnt/foo
# sync

I doubt it is the drive itself because if I format the drive with a different filesystem (tested with JFS) it works fine.