Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZFS mount/unmount process stuck #6966

Closed
itcrowdsource opened this issue Dec 15, 2017 · 7 comments
Closed

ZFS mount/unmount process stuck #6966

itcrowdsource opened this issue Dec 15, 2017 · 7 comments
Labels
Status: Stale No recent activity for issue

Comments

@itcrowdsource
Copy link

System information

Type Version/Name
Distribution Name Ubuntu
Distribution Version 16.04 / Xenial
Linux Kernel 4.4.0-101-generic
Architecture x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts cpufreq
ZFS Version version: 0.6.5.6-0ubuntu16
SPL Version version: 0.6.5.6-0ubuntu4

Describe the problem you're observing

Specifically were encountering issues within LXD. The ZFS mount point seems to be locked after restarting a LXC container that uses ZFS. This doesnt seem to be a LXD-related problem but rather a bug within ZFS.

LXD log:
action=shutdown created=2017-11-24T15:01:04+0000 ephemeral=false lvl=info msg="Shutting down container" name=c2 t=2017-12-15T05:44:10+0000 timeout=-1s used=2017-11-24T15:06:55+0000
action=shutdown created=2017-11-24T15:01:04+0000 ephemeral=false lvl=info msg="Shut down container" name=c2 t=2017-12-15T05:44:40+0000 timeout=-1s used=2017-11-24T15:06:55+0000
lvl=warn msg="Unable to update backup.yaml at this time." name=c2 t=2017-12-15T05:44:40+0000
lvl=warn msg="ZFS returned EBUSY while "/var/snap/lxd/common/lxd/storage-pools/lxd/containers/c2" is actually not a mountpoint." t=2017-12-15T05:44:50+0000
lvl=warn msg="Unable to update backup.yaml at this time." name=c2 t=2017-12-15T05:44:50+0000

Describe how to reproduce the problem

  1. lxc restart NAME
  2. Container is stuck in the shutdown process
  3. After a while the container isnt running anymore
  4. Unable to start the container

https://github.com/lxc/lxd/issues/4104

Probably also related to:
#5796

Include any warning/errors/backtraces from the system logs

@stgraber
Copy link

This will be addressed by the fix in #7120 so the issue should probably be considered a duplicate of #5796.

@behlendorf
Copy link
Contributor

There is an updated version of the #7207.

@DeadlyMercury
Copy link

DeadlyMercury commented May 25, 2018

I have simmilar problem, but I have no answer from zfs like "ZFS returned EBUSY": it just hangs.
Last message in monitor is:
message: Mounting ZFS storage volume for container "bl-adm" on storage pool "default".

But I am using 18.04 and zfs 0.7.5 (latest in bionic repo)

And after that commands like "zfs list" hangs too with no info, only kernel errors like:
INFO: task lxd:26664 blocked for more than 120 seconds.

#7207 marked as closed and fixed in version 0.7.9. I tried to install it from ppa, but it did not help.

@behlendorf
Copy link
Contributor

This may be a duplicate of #7659.

@vazir
Copy link

vazir commented Jul 20, 2018

@stgraber do you think the fix is going to be in the 18.04 anytime soon?

@DeadlyMercury
Copy link

@vazir you can watch it here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781364

@stale
Copy link

stale bot commented Aug 25, 2020

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: Stale No recent activity for issue label Aug 25, 2020
@stale stale bot closed this as completed Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale No recent activity for issue
Projects
None yet
Development

No branches or pull requests

5 participants