From owner-freebsd-current@FreeBSD.ORG Mon Aug 15 01:49:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5809106566C for ; Mon, 15 Aug 2011 01:49:50 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx1.freebsd.org (Postfix) with ESMTP id 83A3A8FC0C for ; Mon, 15 Aug 2011 01:49:50 +0000 (UTC) Received: by iye7 with SMTP id 7so12684998iye.17 for ; Sun, 14 Aug 2011 18:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=kyDmOA+C9uqQtCMMH6el3axyEiMYNtJUrUlNTE95ABc=; b=jjHSQnCuq/FxfsjqUMmUpz2r89azcUeZcvIcMoYqG+aCfu4R3I8AjIfK73QJbtZfGn fg3onTpNA9w28OBSbFtQwYLq5T08YbgXYH9m1Q5HtX+ETVUby6k3GTMVATVP19Y3uDys hn/Q8hsXH+9UbI8bb7y+jgChsbaHl0c9t4+PE= MIME-Version: 1.0 Received: by 10.231.69.136 with SMTP id z8mr6678293ibi.4.1313371129437; Sun, 14 Aug 2011 18:18:49 -0700 (PDT) Received: by 10.231.157.77 with HTTP; Sun, 14 Aug 2011 18:18:49 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Aug 2011 22:18:49 -0300 Message-ID: From: "Carlos A. M. dos Santos" To: "deeptech71@gmail.com" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ghost files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2011 01:49:50 -0000 On Sun, Aug 7, 2011 at 3:08 AM, deeptech71@gmail.com wrote: > as of recent times, some git rebase operations fail unexpectedly with > an error: "cannot create .git/index.lock: file exists". an > investigation session was something like the following: > $ ls -l .git > the index.lock file is not in the shown list. > $ ls -l .git/index.lock > the file is listed! it's a regular file, its size is ~60KiB. > $ cat .git/index.lock > some file content is shown. > $ mv .git/index.lock .git/someplace > moving fails with: index.lock: file does not exist. > $ ee .git/index.lock > some file content is shown, which i edit and save. then the > .git/index.lock file really disappears (cat, direct ls, ee, mv, etc. > do not find the file), and the content i put in the .git/index.lock > file via ee is now in .git/index. > > H$X!!!!!111 > > i still have some git rebase operations (which are notably > disk-active) fail from time to time with "impossible" reasons (for > example: something like "cherry picking failed", or something like > "cannot move git-rebase-new to git-rebase-todo: file does not exist"). > > i'd note that the hard drive is kind of old (>7 years), and i recently > had the power cut during port build operations twice, although the > (UFS) filesystem is fsck-clean. > > has anyone experienced anything like this? > what is the possibility of a filesystem/kernel bug or fsck bug? Do not start supposing that this is a filesystem/kernel bug so early. I have seen similar mysterious messages @work, with Git servers running on Linux, so I'm inclined to believe that it is a software issue. --=20 "The flames are all long gone, but the=EF=BB=BF pain lingers on"