From owner-freebsd-stable@FreeBSD.ORG Tue Aug 2 23:00:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0ABF16A41F for ; Tue, 2 Aug 2005 23:00:32 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68D7C43D6B for ; Tue, 2 Aug 2005 23:00:29 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 4F1FCA246E8 for ; Tue, 2 Aug 2005 20:00:24 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31614-06 for ; Tue, 2 Aug 2005 23:00:23 +0000 (GMT) Received: from ganymede.hub.org (blk-224-176-51.eastlink.ca [24.224.176.51]) by hub.org (Postfix) with ESMTP id 03F87A2469E for ; Tue, 2 Aug 2005 20:00:22 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 427373BE2E; Tue, 2 Aug 2005 20:00:30 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 415A734F92 for ; Tue, 2 Aug 2005 20:00:30 -0300 (ADT) Date: Tue, 2 Aug 2005 20:00:30 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20050802195358.F965@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: unionfs: Permission denied on binaries issue ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2005 23:00:32 -0000 'k, I seem to recall this one being brought up before, but hadn't saved that thread :( I've re-read through the mount_unionfs man page to make sure that I hadn't missed anything, so ... I'm trying to narrow down where the issue with the file system hang is coming in, and in doing so, I just did a mount_unionfs of the file system, cd'd to the usr/bin directory and ran './bzip2' ... it worked fine ... but, when I run it a second time, I ge a 'Permission denied' error ... The reason, of course, is that the bzip2 binary has 'moved up' a layer, and consequently had its bits changed to 644 instead of 755 ... Now, if I recall the original thread, the comment was to change the mount point to noatime, so that, of course, running a binary doesn't cause the access time to be updated ... But, this wasn't an issue in 4.x ... has unionfs changed that much since 4.x, or should this be considered a bug? If not considered a bug, what impact is there of setting the unionfs to noatime? Will this affect files that aren't on the unionfs? for instance, if I 'vi /usr/bin/testfile', and then did a more of it at a later point, will the access time be updated? Basically, does this only affect the file system that has been union'd onto the "bottom" of the file system, or does it affect everything, both the top and bottom layer? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664