Re: file system deadlock in RELENG_11

[Ronald Klop]

Running procstat -kk  will display on what syscall a process/thread  
is blocking.

That might give some valuable information to people.

Regards,
Ronald.


On Thu, 24 Aug 2017 22:01:25 +0200, Mike Tancsa  wrote:


OK, this is fairly easy to repeat. If I start a sync of a snapshot via
zrep, it hangs the box.  CTRL+T shows


DEBUG: overiding stale lock on zroot/chyves from pid 19378
sending zroot/chyves@zrep_10 to 10.151.9.2:zroot/chyves
cannot receive new filesystem stream: destination
'zroot/chyves/guests/resi/disk1' exists
must specify -F to overwrite it
^C
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 358.94r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 360.42r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 360.79r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 360.99r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.19r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.37r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.55r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.74r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 361.92r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.11r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.31r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.50r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.69r 0.00u 0.00s 0%
3476k
load: 0.48  cmd: zfs 29690 [tx->tx_sync_done_cv] 362.90r 0.00u 0.00s 0%
3476k
load: 0.52  cmd: zfs 29690 [tx->tx_sync_done_cv] 363.08r 0.00u 0.00s 0%
3476k



On 8/24/2017 11:48 AM, Mike Tancsa wrote:

I upgraded a server yesterday from RELENG_11 from march 2017 to r322800
(Aug 22) and noticed that under heavy disk IO in a VM, the server is
locking up.  In the vm, I was doing a large untar and I noticed that
prior to the lockup, the hypervisor would be struggling to keep up the
disk writes.  The VM is on a zvol if that makes any difference. A few
times in the VM, IO would be clogged to the point that the disk would
timeout in the VM

Aug 24 08:32:02 kernel: ahcich6: Timeout on slot 14 port 0
Aug 24 08:32:02 kernel: ahcich6: is  cs  ss  rs
 tfd 50 serr  cmd 0001db17
Aug 24 08:32:02 kernel: (ada1:ahcich6:0:0:0): WRITE_FPDMA_QUEUED. ACB:
61 00 a8 47 d8 40 01 00 00 01 00 00
Aug 24 08:32:02 kernel: (ada1:ahcich6:0:0:0): CAM status: Command  
timeout

Aug 24 08:32:02 kernel: (ada1:ahcich6:0:0:0): Retrying command

When the parent deadlocks, I cant run anything thats not already in RAM.
shutdown doesnt work and I have to reboot the box via IPMI.

Any ideas how to debug this or try and better understand the problem so
I can at least work around it ?

---Mike




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[11-Stable] Freeswitch doesn't exit unless SIGKILLed

[Eric Masson]

Hello,

I'm facing an issue with Freeswitch (1.6.x or 1.8.x, FreeBSD port or
manual build from FS git) on 11-Stable.

When stopping the application, it stucks and I have to SIGKILL it to
really stop the process.

I've gathered information that is available in a ticket on Freeswitch
JIRA :
https://freeswitch.org/jira/browse/FS-10580

The problem seems to be related to 11-Stable as I can't reproduce the
issue with 10.3-RELEASE.

Any idea, anyone ?

Regards

Éric Masson
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Call for testing VMware open-vm-tools update

[Josh Paetzel]

VMware has been contributing to making FreeBSD a first class citizen for
their open source vmware tools.

As a continuing part of this contribution there's a new version of
open-vm-tools in the works.  The INO64 work in FreeBSD HEAD broke
building open-vm-tools for HEAD/i386, and there was a kernel panic that
affected HEAD/amd64.  That has been addressed and vmware has started QA
for the tools for FreeBSD 11.1-R and 10.3-R  amd64 and i386.

I've given this update a fair amount of testing and it gets a "works on
my machine" certification from me.

The new version is available as a port at
https://people.freebsd.org/~jpaetzel/open-vm-tools.tar.gz . Feel free to
give it a spin and please report any issues by filing a bug at
https://bugs.freebsd.org/   If you tag the bug you create as ports
emulators/open-vm-tools it will get auto-assigned to me.

-- 

Thanks,

Josh Paetzel
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"