From nobody Sun Jul 14 10:13:17 2024 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WMLlJ4pWzz5QlFZ for ; Sun, 14 Jul 2024 10:13:48 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WMLlJ1Zvtz4bs4 for ; Sun, 14 Jul 2024 10:13:48 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1720952015; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0War64JkLCQqXcTJLCxMp4kYEeqDBa4E2nmr/TEbvlo=; b=LjylkgdR96oOw2IG2+ddgD1xbn/+ryaDVLpVG0wW+lU845ms/nva5nppJEyD5Agb+/UEO+ 2ZeuB3ZegRjufxpQFR0qxyP/a110AczKFLpFAuBdcbzDx4vOD+JMQKOx5sjIXituagiHiw PAd6T0+eMTjW+XCUzA7C4fGk8a8Eg0aZKTOcA/3ycZwxbsVeLo6Fr/Cp0yI9asJG/xuGWt y+KENQ7vpL6pb2VZYnsieTfR3icN870d6j3mHodtuQttTi6n6VNLkofTPr28ZzCMd2YH2u JYKnMPwR9k7f0htGP5SPV2n+z5z9g0RfY0CBP/bfmpBedG5h4rX8Q0ahSgkV+w== Date: Sun, 14 Jul 2024 12:13:17 +0200 From: Alexander Leidinger To: Garrett Wollman Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Possible bug in zfs send or pipe implementation? In-Reply-To: <26259.17366.276955.824313@hergotha.csail.mit.edu> References: <26259.12713.114036.564205@hergotha.csail.mit.edu> <26259.17366.276955.824313@hergotha.csail.mit.edu> Message-ID: <2a8e7892280dbc5be1d34a53a5f36587@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_26d7ff65f42eda061c5d904c2ac65c3b"; micalg=pgp-sha256 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4WMLlJ1Zvtz4bs4 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_26d7ff65f42eda061c5d904c2ac65c3b Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-07-14 05:19, schrieb Garrett Wollman: > < said: > >> # ps axHl >> should show you what wchan's the processes are waiting on and that >> might >> give you a clue w.r.t. what is happening? > > zfs is waiting to write into the pipe and pv (the progress meter) is > waiting in select. > >> If is easy to build a kernel from sources and boot that, you could try >> defining >> PIPE_NODIRECT in sys/kern/sys_pipe.c and see if that avoids the hangs? > > It's easy to build a kernel from sources, but not easy to reboot the > server -- it's being retired shortly, and because of time constraints > I need to get it drained before the next scheduled outage. As you need to stop the process anyway: I always use mbuffer with "-m 50M" (50M buffer, and with "-v 2" you will also get some progress info) between the sender and the receiver. This may or may not change the behavior your see (given you have some time constraint which prevents certain investigative stuff and gives priority to get the job done). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_26d7ff65f42eda061c5d904c2ac65c3b Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmaTpMsACgkQEg2wmwP4 2IYLkA/+IBCmIfp4hksBbQ//nAF8vvJ+HEPZIaCOBBPXDb+MnE637lLMBcqwrdrl mQtlTM8GpBrb5hJnMc/zy2RJkkVR+tuCP2hbIPaj/hi0xfbxzQ+t80DSY+pSib8x TMOBavGcpoJfn8CWQ4ZadWNpK+cUfQ0K/twqgD2IjCpW/Dj7lLuF71PgPcddo4RF v0VOJwCZi6oX9BqJ4FglX5x9vVTlyjzksOEha47SJKnFrLahPISSw+PUGWM9KKeW XxQOBQPgXdpaizQzM28h2I3wIBbRgBwjOZLeS36IewGT0eYzsJC5EMpwin04ulNR x5C/3fMvUxG+olmQZ55GNX9qJens0RZzEX7rynu8+mTAJIRZWMN//7Y8WhxzXwDY 2JJ4xan2hefMKAJoKl6VQCDkR/1LVQkQ6tW6IfbAt16mfVBOtS6Rh1oKMhQbpl/C JV05xakd1i//3WetqjS+5uvMdtNKuhYbytjn7kydCWDgIm4OIQb5MOSqquIVCh0x BotYf1L0ygSMvHrdmXyqVugjd6v+YMZr+36tvgdbXqHkaEZkMG3yrCoxIrTjGI4J LeMxQCKbh98KWoTAKJqbvkXIn4fL0lPeFlAyga5KZHkbIwaAAVMlAk4mcPc6zFGK TGqysTven06EOFRgdarEZYm/gJK8MQvajC7dBpTE90IodI7dpcU= =B1Ev -----END PGP SIGNATURE----- --=_26d7ff65f42eda061c5d904c2ac65c3b--