From owner-freebsd-fs@freebsd.org Sun Mar 20 03:03:17 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50AC9AD6187 for ; Sun, 20 Mar 2016 03:03:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 411BE1AB1 for ; Sun, 20 Mar 2016 03:03:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2K33Fev046304 for ; Sun, 20 Mar 2016 03:03:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 208130] smbfs is slow because it (apparently) doesn't do any caching/buffering Date: Sun, 20 Mar 2016 03:03:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: 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-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2016 03:03:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208130 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Mar 20 21:01:21 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1168AD73B1 for ; Sun, 20 Mar 2016 21:01:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B02839BC for ; Sun, 20 Mar 2016 21:01:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2KL01eo016727 for ; Sun, 20 Mar 2016 21:01:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201603202101.u2KL01eo016727@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 20 Mar 2016 21:01:21 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2016 21:01:21 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f 4 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun Mar 20 23:21:18 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5EDC0AD6889 for ; Sun, 20 Mar 2016 23:21:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F51FF8D for ; Sun, 20 Mar 2016 23:21:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2KNLGv1089237 for ; Sun, 20 Mar 2016 23:21:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 203201] on zfs extattr behaviour broken after unlink Date: Sun, 20 Mar 2016 23:21:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2016 23:21:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203201 --- Comment #11 from commit-hook@freebsd.org --- A commit references this bug: Author: mav Date: Sun Mar 20 23:20:16 UTC 2016 New revision: 297087 URL: https://svnweb.freebsd.org/changeset/base/297087 Log: MFC r290266 (by avg): zfs: allow the lookup of extended attributes of an unlinked file That's required for extattr_get_fd(2) and the like to work properly. PR: 203201 Changes: _U stable/10/ stable/10/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_dir.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Mar 24 11:42:18 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E426ADC299 for ; Thu, 24 Mar 2016 11:42:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4EE1216ED for ; Thu, 24 Mar 2016 11:42:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2OBgIpL051066 for ; Thu, 24 Mar 2016 11:42:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 203201] on zfs extattr behaviour broken after unlink Date: Thu, 24 Mar 2016 11:42:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: 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-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 11:42:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203201 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #12 from Andriy Gapon --- Thank you, Alexander. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Mar 24 18:23:08 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C1DCADCC19 for ; Thu, 24 Mar 2016 18:23:08 +0000 (UTC) (envelope-from nishida@asusa.net) Received: from asusam.asj-hosting.net (asusa.asj-hosting.net [219.118.222.245]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (Client CN "*.asj-hosting.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 026D91EB5 for ; Thu, 24 Mar 2016 18:23:06 +0000 (UTC) (envelope-from nishida@asusa.net) Received: (qmail 13295 invoked by uid 89); 25 Mar 2016 03:16:22 +0900 X-ASJ-Track-ID: <20160324181622.13295.qmail@asusam.asj-hosting.net> X-Spam-Checker-Version: ASJ KMsrv Spam Check Process Internal X-Spam-Status: No, hits=0.0 X-Spam-Flag: No X-Virus-Scanned: ASJ KMsrv Virus Check Process 08041001 X-ASJ-SMTP-Authentication: nishida@asusa.net X-ASJ-Arrival-IP: 50.207.112.201 X-ASJ-SPF-Info: auth X-ASJ-Scan-ID: <1458843382.467161.13288@asusam.asj-hosting.net> X-ASJ-Received-SPF: pass (send with smtp authentication by nishida@asusa.net@50.207.112.201) Received: from gw.asusa.net (HELO rd03.asusa-internal.net) (nishida@asusa.net@50.207.112.201) by asusams.asj-hosting.net with ESMTPS (AES128-SHA encrypted); 25 Mar 2016 03:16:22 +0900 To: freebsd-fs@freebsd.org From: Hiroshi Nishida Subject: Problem with FUSE + fts Message-ID: <56F42EF4.5000505@asusa.net> Date: Thu, 24 Mar 2016 11:16:20 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 18:23:08 -0000 Hi, I found a weird error with FUSE + fts_read(). Every time a command like find, rm -r that calls fts_read() is used for a FUSE mounted filesystem, it outputs "XXX: No such file or directory" errors for some (not all) files/directories. In /usr/src/lib/libc/gen/fts.c, there is fts_safe_changedir(FTS *, FTSENT *, int, char *) and the error seems to occur there in the following way: FTS *sp; FTSENT *p = sp->fts_cur; // Current node DIR *dirp = opendir2(p->fts_accpath, oflag); // Open dir int fd = _dirfd(dirp); // File descriptor of dirp struct stat sb; _fstat(fd, &sb); // fstat current node through fd p->fts_ino != sb.st_ino // This happens for some reason...... and sets errno = ENOENT When the error happens, p->fts_ino always has a small number and sb.st_ino has a great number like: p->fts_ino = 13, sb.st_ino = 54136 So, a new inode number seems to be allocated to sb.st_ino though the node already has an inode number. I would appreciate hearing any feedback on this, though I already posted fuse-devel ML and haven't received any helpful responses yet. The problem seems to be particular to FreeBSD because I don't get any errors with Ubuntu. The sample FUSE program is located at https://github.com/scopedog/FUSE-Test and fts.c is also located under freebsd and ubuntu dirs (interestingly, fts.c of FreeBSD and Ubuntu are almost identical). Thank you. -- Hiroshi Nishida nishida@asusa.net From owner-freebsd-fs@freebsd.org Fri Mar 25 08:40:00 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 569F0ADD444 for ; Fri, 25 Mar 2016 08:40:00 +0000 (UTC) (envelope-from Administrator@nayatelgateway.com) Received: from ngw1.nayatel.com (ngw1.nayatel.com [203.82.48.130]) by mx1.freebsd.org (Postfix) with ESMTP id AA81C163D for ; Fri, 25 Mar 2016 08:39:58 +0000 (UTC) (envelope-from Administrator@nayatelgateway.com) Date: Fri, 25 Mar 2016 13:24:46 +0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: True Type Executable File Violation From: Administrator@nayatelgateway.com To: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2016 08:40:00 -0000 You attempted to send a message that contained a true type executable file. Our company policy prohibits the sending of executable files via email. The message was not delivered. From owner-freebsd-fs@freebsd.org Fri Mar 25 08:40:12 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A593ADD469 for ; Fri, 25 Mar 2016 08:40:12 +0000 (UTC) (envelope-from Administrator@nayatelgateway.com) Received: from ngw1.nayatel.com (ngw1.nayatel.com [203.82.48.130]) by mx1.freebsd.org (Postfix) with ESMTP id CEF3216A3 for ; Fri, 25 Mar 2016 08:40:11 +0000 (UTC) (envelope-from Administrator@nayatelgateway.com) Date: Fri, 25 Mar 2016 13:24:46 +0500 Message-ID: <0D.13.15314.EC5F4F65@ngw1.nayatel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Executable File Violation From: Administrator@nayatelgateway.com To: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2016 08:40:12 -0000 You attempted to send a message that contained an executable file. Our company policy prohibits the sending of executable files via email. The message was not delivered. From owner-freebsd-fs@freebsd.org Fri Mar 25 08:40:13 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB019ADD46C for ; Fri, 25 Mar 2016 08:40:13 +0000 (UTC) (envelope-from Administrator@nayatelgateway.com) Received: from ngw1.nayatel.com (ngw1.nayatel.com [203.82.48.130]) by mx1.freebsd.org (Postfix) with ESMTP id 1FACF16A5 for ; Fri, 25 Mar 2016 08:40:12 +0000 (UTC) (envelope-from Administrator@nayatelgateway.com) Date: Fri, 25 Mar 2016 13:24:46 +0500 Message-ID: <1D.13.15314.EC5F4F65@ngw1.nayatel.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=====mte=boundary=number=25376=====" Subject: Email Policy Violation From: Administrator@nayatelgateway.com To: freebsd-fs@freebsd.org X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2016 08:40:13 -0000 --=====mte=boundary=number=25376===== Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit The attached message contains content which violates our email policy. The message was not delivered. --=====mte=boundary=number=25376===== Content-type: message/rfc822 X-AuditID: 73babc58-08fff70000003bd2-a7-56f4f5cd1a5c From: freebsd-fs@freebsd.org To: naqeeb@spopk.org Subject: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====mte=boundary=number=25375=====" --=====mte=boundary=number=25375===== Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Some parts of this message were removed because they violated your mail server's policies. document.exe was removed from the message because it violates your mail server's policy. --=====mte=boundary=number=25375===== Content-Type: message/rfc822 X-AuditID: 73babc58-08fff70000003bd2-a7-56f4f5cd1a5c Received: from a.smtp.cyber.net.pk (smtp.cyber.net.pk [61.5.158.182]) by (Symantec Messaging Gateway) with SMTP id EC.13.15314.DC5F4F65; Fri, 25 Mar 2016 13:24:46 +0500 (PKT) Received: from freebsd.org (unknown [124.29.198.204]) by a.smtp.cyber.net.pk (Postfix) with ESMTP id A633C14A04 for ; Fri, 25 Mar 2016 13:24:41 +0500 (PKT) Message-ID: From: freebsd-fs@freebsd.org To: naqeeb@spopk.org Subject: Date: Fri, 25 Mar 2016 13:22:50 +0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear user naqeeb@spopk.org, We have found that your e-mail account was used to send a huge amount of spam messages during this week. Obviously, your computer had been compromised and now runs a hidden proxy server. We recommend you to follow instruction in order to keep your computer safe. Have a nice day, spopk.org technical support team. --=====mte=boundary=number=25375=====-- --=====mte=boundary=number=25376=====-- From owner-freebsd-fs@freebsd.org Fri Mar 25 23:53:46 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB7EEADDCEC for ; Fri, 25 Mar 2016 23:53:46 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3581185 for ; Fri, 25 Mar 2016 23:53:43 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:6vCp7BT7ZKXdvOcK7L9MOfBe2dpsv+yvbD5Q0YIujvd0So/mwa64YxKN2/xhgRfzUJnB7Loc0qyN4/CmAzVLuMfJmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3BPAZ4bt74BpTVx5zukbviq9uJOk4R1XKUWvBbElaflU3prM4YgI9veO4a6yDihT92QdlQ3n5iPlmJnhzxtY+a9Z9n9DlM6bp6r5YTGY2zRakzTKRZATI6KCh1oZSz7ViQBTeIs1sdSGINkhsAJQne7BD2V9+ltCrhtutx0QGTJtDtRPYyVCj0vIlxTxq9siYMNHYc+WrUjsF1xPZBpRuqpBhyxqbJZ46IOf5mfuXWdIVJFiJ6Qs9NWnkZUcuHZIwVAr9EZL4Aog== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DQAQChzvVW/61jaINehAF9BrpYAQ2BcBcKhSJKAoFjFAEBAQEBAQEBYyeCLYIUAQEBAwEBAQEgBCcgCwULAgEIGAICDRkCAicBCSYCBAgHBAEcBId+CA6wWpA8AQEBAQEBBAEBAQEBARYEfIUigXuCSYQKDAcBAQeDFoJWBZdghXGCcoI3hFCHdIUxjwgCHgEBQoQBIDAHh1kBCBcffgEBAQ X-IronPort-AV: E=Sophos;i="5.24,392,1454994000"; d="scan'208";a="274535784" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 25 Mar 2016 19:53:36 -0400 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 665BB15F579; Fri, 25 Mar 2016 19:53:36 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 2uw-qyATx3hD; Fri, 25 Mar 2016 19:53:35 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 10DFA15F57B; Fri, 25 Mar 2016 19:53:35 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id u7k54cHRoeIF; Fri, 25 Mar 2016 19:53:34 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id E1CE415F579; Fri, 25 Mar 2016 19:53:34 -0400 (EDT) Date: Fri, 25 Mar 2016 19:53:34 -0400 (EDT) From: Rick Macklem To: Hiroshi Nishida Cc: freebsd-fs@freebsd.org Message-ID: <1294209833.31699182.1458950014610.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <56F42EF4.5000505@asusa.net> References: <56F42EF4.5000505@asusa.net> Subject: Re: Problem with FUSE + fts MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - IE7 (Win)/8.0.9_GA_6191) Thread-Topic: Problem with FUSE + fts Thread-Index: JVjynZEdPTCikLadX0Ej/KgjQZyEmg== X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Mar 2016 23:53:46 -0000 Hiroshi Nishida wrote: > Hi, > > I found a weird error with FUSE + fts_read(). > Every time a command like find, rm -r that calls fts_read() is used for a > FUSE mounted filesystem, it outputs "XXX: No such file or directory" errors > for some (not all) files/directories. > I think I see the same thing when doing an "rm -r" on a fuse/GlusterFS volume. To be honest, I just add a "-f" to the command to shut it up and then it deleted the tree. I think, in general, what readdir() returns after an entry is unlink'd is undefined behaviour. As such, the safe way to delete all of a directory is something like: - in a loop until readdir() returns EOF - opendir() - readdir() the first entry - unlink() that entry - closedir() --> So that all you ever do is readdir() the first entry after an opendir(). However few, if any, apps do this and loop on readdir(), unlink() instead. >From my limited experience with fuse, the directory offset is an index (which isn't monotonically increasing for GlusterFS) and those indexes only work while the directory is open. I think that in Linux, an opendir(), readdir() reads an entire directory into storage maintained by the libc functions and then readdir() returns subsequent entries without doing a kernel syscall. As such, deletion of entries that, in turn, change directory offsets in the file system, don't affect this. In FreeBSD, this (reading the entire directory when opened) is done for "unionfs", but not otherwise. --> This causes grief for NFS, due to directory offsets (called cookies in NFS) change when entries are deleted. --> It is also the case that many (including Linux, I think) return these "cookies" in their "struct dirent", but FreeBSD does not. I have been tempted to enable "read the entire directory on opendir()" for other file system types, but the downside is that apps. will use memory for this (possibly lots for large directories). Since most use UFS or ZFS and don't see problems, I haven't tried to make a case for this change. (I may try if I find that this change fixes fuse.) If you don't mind rebuilding libc from sources, take a look at opendir.c and readdir.c (I can't remember exactly how it is done, but you should find where it chooses to read the entire directory upon opendir or the first readdir) and you could try enabling that for fuse. The directory offset problem is a thorny one, but will at least be partially fixed by a new "struct dirent" with a d_off field in it. This has to be done someday to make ino_t 64bits anyhow. *** If you see this for cases other than "rm -r", such as "ls -lR", then all of the above is bogus. Another issue (which I doubt is causing this) is that FreeBSD has a 32bit ino_t but fuse uses a 64bit inode#, so the FreeBSD fuse interface ends up truncating the high order 32bits off. (GlusterFS uses more than 32bits, but the high order bits are invariant, so it doesn't break things.) Hope this somehow helps, rick > In /usr/src/lib/libc/gen/fts.c, there is fts_safe_changedir(FTS *, FTSENT *, > int, char *) and the error seems to occur there in the following way: > > FTS *sp; > FTSENT *p = sp->fts_cur; // Current node > DIR *dirp = opendir2(p->fts_accpath, oflag); // Open dir > int fd = _dirfd(dirp); // File descriptor of dirp > struct stat sb; _fstat(fd, &sb); // fstat current node through fd > > p->fts_ino != sb.st_ino // This happens for some reason...... and sets errno > = ENOENT > > When the error happens, p->fts_ino always has a small number and sb.st_ino > has a great number like: > p->fts_ino = 13, sb.st_ino = 54136 > > So, a new inode number seems to be allocated to sb.st_ino though the node > already has an inode number. > > I would appreciate hearing any feedback on this, though I already posted > fuse-devel ML and haven't received any helpful responses yet. > The problem seems to be particular to FreeBSD because I don't get any errors > with Ubuntu. > > The sample FUSE program is located at > https://github.com/scopedog/FUSE-Test > > and fts.c is also located under freebsd and ubuntu dirs (interestingly, fts.c > of FreeBSD and Ubuntu are almost identical). > > Thank you. > > -- > Hiroshi Nishida > nishida@asusa.net > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Sat Mar 26 04:48:33 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB502ADE77B for ; Sat, 26 Mar 2016 04:48:33 +0000 (UTC) (envelope-from nishida@asusa.net) Received: from asusam.asj-hosting.net (asusa.asj-hosting.net [219.118.222.245]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (Client CN "*.asj-hosting.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F3E31202 for ; Sat, 26 Mar 2016 04:48:32 +0000 (UTC) (envelope-from nishida@asusa.net) Received: (qmail 55608 invoked by uid 89); 26 Mar 2016 13:48:23 +0900 X-ASJ-Track-ID: <20160326044823.55608.qmail@asusam.asj-hosting.net> X-Spam-Checker-Version: ASJ KMsrv Spam Check Process Internal X-Spam-Status: No, hits=0.0 X-Spam-Flag: No X-Virus-Scanned: ASJ KMsrv Virus Check Process 08041001 X-ASJ-SMTP-Authentication: nishida@asusa.net X-ASJ-Arrival-IP: 73.25.52.117 X-ASJ-SPF-Info: auth X-ASJ-Scan-ID: <1458967703.68927.55601@asusam.asj-hosting.net> X-ASJ-Received-SPF: pass (send with smtp authentication by nishida@asusa.net@73.25.52.117) Received: from c-73-25-52-117.hsd1.or.comcast.net (HELO ASUSA-Mac-mini.local) (nishida@asusa.net@73.25.52.117) by asusams.asj-hosting.net with ESMTPS (AES128-SHA encrypted); 26 Mar 2016 13:48:23 +0900 Subject: Re: Problem with FUSE + fts References: <56F42EF4.5000505@asusa.net> <1294209833.31699182.1458950014610.JavaMail.zimbra@uoguelph.ca> To: freebsd-fs@freebsd.org From: Hiroshi Nishida Message-ID: <56F6148D.2030706@asusa.net> Date: Fri, 25 Mar 2016 21:48:13 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1294209833.31699182.1458950014610.JavaMail.zimbra@uoguelph.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Mar 2016 04:48:34 -0000 Thank you for your response. On 3/25/16 4:53 PM, Rick Macklem wrote: > I think I see the same thing when doing an "rm -r" on a fuse/GlusterFS volume. Unfortunately, it happens also with "find XXX -print", though I have experienced a similar "rm -r" + "XXX: No such file or directory" problem with UFS + SUJ. And I also verified with truss that in _fstat(fd, &sb); p->fts_ino != sb.st_ino stat() system call is called with the same path as p's. Anyway, the following patch for lib/libc/gen/fts.c prevents the error but is far from a good solution. https://github.com/scopedog/FUSE-Test/blob/master/fts.c.patch It assumes that the filesystem id (f_type in struct statfs) of FUSE is 0xed but I am not sure if it's applicable to all FUSE filesystems. I'll look into FUSE source code next week. > To be honest, I just add a "-f" to the command to shut it up and then it deleted > the tree. > > I think, in general, what readdir() returns after an entry is unlink'd is undefined > behaviour. As such, the safe way to delete all of a directory is something like: > - in a loop until readdir() returns EOF > - opendir() > - readdir() the first entry > - unlink() that entry > - closedir() > --> So that all you ever do is readdir() the first entry after an opendir(). By the way, could you delete all the files with "-f"? I am testing with a pretty big directory containing 81,000 files/dirs and have never used "-f", but have to "rm -r" again for undeleted entries. However, the offset problem is very interesting as it seems to be applicable to all filesystems. Thank you. -- Hiroshi Nishida nishida@asusa.net