From owner-freebsd-fs@FreeBSD.ORG Mon Jan 28 14:40:02 2008 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5577116A417 for ; Mon, 28 Jan 2008 14:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4560413C467 for ; Mon, 28 Jan 2008 14:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0SEe2d6038675 for ; Mon, 28 Jan 2008 14:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0SEe2Nb038674; Mon, 28 Jan 2008 14:40:02 GMT (envelope-from gnats) Date: Mon, 28 Jan 2008 14:40:02 GMT Message-Id: <200801281440.m0SEe2Nb038674@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Joe Peterson Cc: Subject: Re: bin/118249: mv(1): moving a directory changes its mtime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joe Peterson List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2008 14:40:02 -0000 The following reply was made to PR bin/118249; it has been noted by GNATS. From: Joe Peterson To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/118249: mv(1): moving a directory changes its mtime Date: Mon, 28 Jan 2008 07:14:09 -0700 A couple of notes on this... * It does not happen with, e.g., ZFS, so it appears to be UFS-specific. * When doing cp -pR, it does not happen. * Along these lines, I tried moving files and dirs *across* file systems, and it does not happen. So it's the case of moving a dir to another dir in the *same* fs that invokes the issue. Since moving across filesystems (according to the man page) uses "rm -f dest && cp -pRP source dest && rm -rf source" rather than rename, this makes sense. P.S. I used the web-form to submit the bug, so the text box must treat the text as one long line (hence the 417 character line).