You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux melchior 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Architecture
x86_64
ZFS Version
0.8.0-rc3_66_gf8bb2a7e0
SPL Version
0.8.0-rc3_66_gf8bb2a7e0
Describe the problem you're observing
I have an encrypted path that has lots of smaller files in it. I was able to mount it without a problem and use it, although with heavy use, I was getting an error and the filesystem would hang until rebooted. I changed to USB 2.0 as I had seen errors related to USB and was testing when it crashed again when doing a chown -R in the encrypted directory. Upon reboot, I updated the pool, as I've been reluctant to do so and was hoping that would help. Once I imported the pool, I ran the zpool upgrade and then ran zfs load-key -a, put in the key (which was accepted) and did a zfs mount -a (at this point it did something (with heavy i/o) for about 2 minutes before returning i/o error and dmesg showed the crash as listed below.
Include any warning/errors/backtraces from the system logs
System information
Describe the problem you're observing
I have an encrypted path that has lots of smaller files in it. I was able to mount it without a problem and use it, although with heavy use, I was getting an error and the filesystem would hang until rebooted. I changed to USB 2.0 as I had seen errors related to USB and was testing when it crashed again when doing a chown -R in the encrypted directory. Upon reboot, I updated the pool, as I've been reluctant to do so and was hoping that would help. Once I imported the pool, I ran the zpool upgrade and then ran zfs load-key -a, put in the key (which was accepted) and did a zfs mount -a (at this point it did something (with heavy i/o) for about 2 minutes before returning i/o error and dmesg showed the crash as listed below.
Include any warning/errors/backtraces from the system logs
-->
The text was updated successfully, but these errors were encountered: