From owner-freebsd-bugs@freebsd.org Thu Feb 13 08:22:24 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C53F250E19 for ; Thu, 13 Feb 2020 08:22:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48J8dD1q9qz4dpt for ; Thu, 13 Feb 2020 08:22:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 3DF5E250E18; Thu, 13 Feb 2020 08:22:24 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3DB78250E17 for ; Thu, 13 Feb 2020 08:22:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48J8dD0wkdz4dps for ; Thu, 13 Feb 2020 08:22:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 199667AE8 for ; Thu, 13 Feb 2020 08:22:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 01D8MNJr096925 for ; Thu, 13 Feb 2020 08:22:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 01D8MNRv096897 for bugs@FreeBSD.org; Thu, 13 Feb 2020 08:22:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 244089] lsextattr on a specific UFS file locks system Date: Thu, 13 Feb 2020 08:22:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ml@netfence.it X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2020 08:22:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244089 Bug ID: 244089 Summary: lsextattr on a specific UFS file locks system Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: ml@netfence.it I've got a 11.3p6/amd64 UFS-based system, where Samba 4.10 is running in a = jail as an AD member. Yesterday I tried enabling vfs_fruit and streams_xattr: apparently everythi= ng worked fine for a while and extended attributes were created on files/direc= tory a Mac client accessed. After a while the client lost connection to the server: I checked and saw a smbd process taking 100% CPU; such a process was unkillable to the point it even prevented rebooting. Reset button had to be pressed. I pinpointed this to reading the extended attributes that were attached to = some file in a particular directory. I.e. Something like: find {dir} -exec lsextattr user "{}" ";" produces a process: lsextattr user {file} taking 100% cpu and not willing to die in any way. Again, only the reset button could get me out of this situation. "fsck -y" found no sign of troubles on that filesystem. I was able to use rsync to make a copy of the whole share without extended attributes, so the server is working again. However, for now, I'm keeping the "bad" copy around for testing. System is 11.3p6/amd64 with custom kernel, i.e.: _ UFS_ACL, UFS_GJOURNAL, QUOTA, MD_ROOT, NFS*, COMPAT*, AUDIT, CAPABILIT*, = MAC, RACCT*, RCTL were removed, along with unused drivers; _ GEOM_MIRROR, aesni and NULLFS were added. # tunefs -p /dev/mirror/gm0f=20 tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time Note soft update journaling is now temporarily disabled, but was enabled wh= en the problem first arose. One intersting thing would be to exfiltrate this "bad" directory and copy i= t to a test server, as I cannot perform many things on this remote production sy= stem (especially considering I cannot press reset remotely). However just reading the data hangs it, so I have no idea how to do this. --=20 You are receiving this mail because: You are the assignee for the bug.=