Any updates on this? I'm still unable to use my Steam Controller (and by extension, play any of the games I'd use it with), even with a clean install of Steam from a few weeks ago, because Steam still crashes in the same way while trying to migrate the controller profile.
I confirmed same problem. When I moved the system from on ZFS to ext4, Steam controller setting works without crash. VALVE should fix this problem, IMHO.
After using a different computer to migrate my controller's profile (to avoid Steam crashing before completing the migration), I have discovered that Steam crashes with the same assertion about the chunk size not aligning to the disk sector size whenever I try to change the controller's setting (such as editing the key mappings in the desktop configuration). In addition to the information in the original bug report, I'm currently running kernel 4.7.4 and zfs 0.6.5.8 (the latest release from http://zfsonlinux.org/)
Hi, ran into the same issue :)
Running Archlinux with 4.7.7-1-ck and ZFS 0.6.5.8.
I worked around the problem by creating a new dataset with a fixed record size for the Steam installation, lets call it tank/Steam.
zfs create tank/Steam
Applied a fixed record size that matched the drive sector size, check your harddrive specs. It should be either 512 or 4k. You can set additional things here if you wish. The record size is the only one that causes the crash.
zfs set recordsize=4k tank/Steam
I then rsynced the entire ~/.local/share/Steam over to tank/Steam except steamapps, because I still wanted a larger record size there. If you rsync everything that should also be fine.
rsync -a --exclude={steamapps} ~/.local/share/Steam tank/Steam
And created the rest...
zfs create -o recordsize=1M tank/Steam/steamapps
rsync -a ~/.local/share/Steam/steamapps tank/Steam/steamapps
Set the mountpoint to legacy
zfs set mountpoint=legacy tank/Steam
and added mountpoint to fstab
tank/Steam /home/USERNAME/.local/share/Steam/ zfs defaults,noatime 0 0
mv ~/.local/share/Steam ~/.local/share/SteamOLD
mount -a
Hope it help anyone else, though I am not sure why they are sanity checking for this :)
Seems like a needless check, especially since ZFS and XFS both have variable record/chunk sizes.
Edit:
If anyone from Valve feels like having a go at reproducing this, the following dataset settings caused the crash, though I assume the only necessary one to cause the crash is the recordsize property.
NAME PROPERTY VALUE SOURCE
tank/Games type filesystem -
tank/Games creation Sat Dec 12 13:25 2015 -
tank/Games used 174G -
tank/Games available 1.90T -
tank/Games referenced 93.9G -
tank/Games compressratio 1.12x -
tank/Games mounted yes -
tank/Games quota none default
tank/Games reservation none default
tank/Games recordsize 1M inherited from tank
tank/Games mountpoint /media/data/Games inherited from tank
tank/Games sharenfs off default
tank/Games checksum on default
tank/Games compression lz4 inherited from tank
tank/Games atime on default
tank/Games devices on default
tank/Games exec on default
tank/Games setuid on default
tank/Games readonly off default
tank/Games zoned off default
tank/Games snapdir hidden default
tank/Games aclinherit restricted default
tank/Games canmount on default
tank/Games xattr sa inherited from tank
tank/Games copies 1 default
tank/Games version 5 -
tank/Games utf8only off -
tank/Games normalization none -
tank/Games casesensitivity sensitive -
tank/Games vscan off default
tank/Games nbmand off default
tank/Games sharesmb off default
tank/Games refquota none default
tank/Games refreservation none default
tank/Games primarycache all default
tank/Games secondarycache all default
tank/Games usedbysnapshots 168K -
tank/Games usedbydataset 93.9G -
tank/Games usedbychildren 80.2G -
tank/Games usedbyrefreservation 0 -
tank/Games logbias latency default
tank/Games dedup off default
tank/Games mlslabel none default
tank/Games sync standard default
tank/Games refcompressratio 1.03x -
tank/Games written 88K -
tank/Games logicalused 196G -
tank/Games logicalreferenced 97.1G -
tank/Games filesystem_limit none default
tank/Games snapshot_limit none default
tank/Games filesystem_count none default
tank/Games snapshot_count none default
tank/Games snapdev hidden default
tank/Games acltype off default
tank/Games context none default
tank/Games fscontext none default
tank/Games defcontext none default
tank/Games rootcontext none default
tank/Games relatime on temporary
tank/Games redundant_metadata all default
tank/Games overlay off default
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
When I connect my Steam Controller in Big Picture Mode it prompts me to migrate the settings profile (I hadn't used my controller in some time) then Steam crashes while migrating. Otherwise Steam and the games I've tried playing through it work fine. I'm on a 64-bit Gentoo with STEAM_RUNTIME disabled and ZFS filesystems (Steam is running off an SSD with a ZFS filesystem having a 16K recordsize and lz4 compression enabled, no encryption though). The relevant bit of output from Steam, from when I turned on the controller until it crashed:
I suspect the assertion about chunk size not aligning to disk sector size is checking for the wrong thing or in some other way is not valid, and is the source of the problem with the controller crashing steam under Linux for some folks.
Steps for reproducing this issue: