From nobody Wed Nov 26 04:03:01 2025 X-Original-To: freebsd-current@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 4dGQs05Tssz6JKcx for ; Wed, 26 Nov 2025 04:03:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dGQs00bGBz3N1b for ; Wed, 26 Nov 2025 04:03:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=T373u0tQ; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::62e) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-pl1-x62e.google.com with SMTP id d9443c01a7336-2980d9b7df5so76979685ad.3 for ; Tue, 25 Nov 2025 20:03:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1764129794; x=1764734594; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hz5IBK6V0ZlbyRcuMUoRnaJ/RNj1E/p8+heZ27iqNT8=; b=T373u0tQwpYk+4VYeb5ml5njwIp1X+KQx9KxzZYboN1Ksa9lKoII9c1s55Xi0leYZ4 ICwCPdpbrseUBOglN1DVZAEhjaOFzkAJnrwl1qc5sVqKI4tSQ7Z44B9W7nHn8kLhgCAw eFNxgrzuSeuTiHo8AmAMTqJpzd2jO1goN9Q5FRhgXbVynT1ALyhuWaa/GkN1KV5G2qCp vBw26z96nWXP3T0bhJ566sox8RCpzyNxF9vFsG+zIffhuPU8j8WhagXdFbVJqzsCDtr2 HsklYuF+NyNFVl7V3brXbFy14ZEKuX5+XEmAK/PCx6PQsc7Srz/B+Mm4GOTR1b+9m6JG 4+2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764129794; x=1764734594; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=hz5IBK6V0ZlbyRcuMUoRnaJ/RNj1E/p8+heZ27iqNT8=; b=kggSC3VnBizSlH36HnUpzKJFX/l4Z7rEgIwMoyxfDzU6EYjufIOgEKycXHVrL5CPot 4HbpP1zVNUpWgqPT1qsqEQ/aPF+ot7LzHoOx5elCTA8J0WKWrqEZnP0kWeyEKxOBxbU+ XulxCh88/ZehNiScJogaHVrUE9BrFuWl+NXKcfflPvNLvJWIWI/v2DGbRNM0mJvTcah5 Bf/dTd8iUU2VdBdT3l2X3vCFGl8wUrtxNjxeRvtDKOjIQyWDR9kwE216pjr9kFvLG2p8 9/t66VhbNC165z2OO2e5iqnIxKOzBg9ymG7uF3hHB15HFwJLL0iHNqV394ZBSPRjohZQ NuUw== X-Gm-Message-State: AOJu0YxuQ9FGRDnlt1BB5ARvIN61xt2KVL6KzPsrE7aqCkIklNbtjbef dD5V7rijcIFENxZCdm6Nq7xFP2AHt+Ai8colSluy6uSb3pOIoCjwAr6I1cYRhT3i8Fo1Nn7XxJl zghgOgr+pOWp6ckyqpW/lEFGGQKi++2G6ZLAvpANFvP97dWAs2S/awvA= X-Gm-Gg: ASbGncsRT+iCqi7ZMlyBPjeD9/ipBYwuJagzeEBaQb4O2311feWuPyWIfGH8cIBELgi 0I5ZylyuVtkQZdon2PLGvgLc5YJkI27pgvOTtl+LZ/lYFqMT7vWkVkxjkLcae6tPH9luX5Yzh+Q qqcQYj+jUDDDkO8T7a2lS0uXPNqhRNMHt8V/GUvO/tpbtwxk+0mtZyj0A0AUoipfeYbW4qhoIdd V5hbEF/zWYt3+HN7iVvq8u3msa8BUeKIvKc0+P+JYhy2/VNuu2vaPEJIDOsMlZjhYguhGw= X-Google-Smtp-Source: AGHT+IGrXwODx505I4gVCZv0LkWMeD4yp51bLRYIOEjKsZkFQxq8GTc8s0ovwjiRpSbPYBHI2shEx6jPgSmEQHkFNx0= X-Received: by 2002:a17:903:1b50:b0:295:8da5:c631 with SMTP id d9443c01a7336-29b6bf65833mr215151085ad.42.1764129793697; Tue, 25 Nov 2025 20:03:13 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <20251123151439.361dd84c@thor.sb211.local> In-Reply-To: <20251123151439.361dd84c@thor.sb211.local> From: Warner Losh Date: Tue, 25 Nov 2025 21:03:01 -0700 X-Gm-Features: AWmQ_bl3jp4YUgld0M5cRa5eSx2z5jS4FH5fPCrmOSk8Ka4ZdSqtSI7DWC_tquk Message-ID: Subject: Re: freezing on unmountin ext2fs USB device To: A FreeBSD User Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000b0fa170644777995" X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::62e:from]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4dGQs00bGBz3N1b --000000000000b0fa170644777995 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Nov 23, 2025 at 7:15=E2=80=AFAM A FreeBSD User wrote: > Hello, > > running FreeBSD 16.0-CURRENT #4 master-n282101-c8cf5a99f82b: Sun Nov 23 > 13:56:23 CET > 2025 amd64 I'm running into a serious problem when mounting an ext2fs > formated USB Flash > device (512GB). The devince contains files written by a Linux system, > mounting the USB Flash > via extended4fs, the size of the written datafiles is > 128GB. Deleting > those files larger > than some 20GB results in an I/O error reported by FReeBSD (# sudo rm > /mnt/USB/filename). > Unmounting the ext2fs after deletion (sudo umount /mnt) results in a tota= l > freeze of the box. > No crash, no core dump, nothing. I waited almost an hour hoping for > recover. I have to > physically switch off the box. > > I checked with other USB flash I have at hand, one Samsung 256 GB, ZFS - > no problem, another > 128GB, UFS, no problem and several much smaller (4 - 64GB) with FAT or UF= S > filesystems, all no > problem. > > I can not figure out whether it is the USB flash drive itself, the size o= r > the ext2fs itself > causing the problem. > > Does anybody see similar problems or do have an tip to investigate withou= t > risking my box' > health switching it on/off on failure? > I've not seen this on the smaller tests I've been able to run. So can you share the error messages that you get when you say you get I/O errors? I'd like to see if this is due to an error in ext2fs or on the USB drive. It's kinda sounding a little like the particular USB is triggering some kind of issue that at the very least we should work around. Given that it's not happening on all ext2fs drives you try to access, I'm leaning towards the drive, but you never know. Thanks --000000000000b0fa170644777995 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Nov 23,= 2025 at 7:15=E2=80=AFAM A FreeBSD User <freebsd@walstatt-de.de> wrote:
Hello,

running FreeBSD 16.0-CURRENT #4 master-n282101-c8cf5a99f82b: Sun Nov 23 13:= 56:23 CET
2025 amd64 I'm running into a serious problem when mounting an ext2fs f= ormated USB Flash
device (512GB). The devince contains files written by a Linux system, mount= ing the USB Flash
via extended4fs, the size of the written datafiles is > 128GB. Deleting = those files larger
than some 20GB results in an I/O error reported by FReeBSD (# sudo rm /mnt/= USB/filename).
Unmounting the ext2fs after deletion (sudo umount /mnt) results in a total = freeze of the box.
No crash, no core dump, nothing. I waited almost an hour hoping for recover= . I have to
physically switch off the box.

I checked with other USB flash I have at hand, one Samsung 256 GB, ZFS - no= problem, another
128GB, UFS, no problem and several much smaller (4 - 64GB) with FAT or UFS = filesystems, all no
problem.

I can not figure out whether it is the USB flash drive itself, the size or = the ext2fs itself
causing the problem.

Does anybody see similar problems or do have an tip to investigate without = risking my box'
health switching it on/off on failure?

= I've not seen this on the smaller tests I've been able to run.

So can you share the error messages that you get=C2=A0= when you say you get I/O errors? I'd like to see if this is due to an e= rror in ext2fs or on the USB drive. It's kinda sounding a little like t= he particular USB is triggering some kind of issue that at the very least w= e should work around. Given that it's not happening on all ext2fs drive= s you try to access, I'm leaning towards the drive, but you never know.=

Thanks
--000000000000b0fa170644777995--