From owner-freebsd-fs@freebsd.org  Sat Nov 28 10:01:54 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
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 ED69AA3AF46
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sat, 28 Nov 2015 10:01:54 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 (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 C651E1C97
 for <freebsd-fs@freebsd.org>; Sat, 28 Nov 2015 10:01:54 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from Julian-MBP3.local (ppp121-45-225-88.lns20.per1.internode.on.net
 [121.45.225.88]) (authenticated bits=0)
 by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id tASA1Ye8084501
 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
 Sat, 28 Nov 2015 02:01:37 -0800 (PST)
 (envelope-from julian@freebsd.org)
Subject: Re: Recovering an unlink-ed, but still opened file
To: "Mikhail T." <mi+thun@aldan.algebra.com>,
 "alex.burlyga.ietf alex.burlyga.ietf" <alex.burlyga.ietf@gmail.com>
References: <5658E498.9070700@aldan.algebra.com>
 <CA+JhTNQh2CKwuEsKcc0v=G=0zG4a5JQTYO56bXv+3MmZ8=MVDg@mail.gmail.com>
 <56591999.1040001@aldan.algebra.com>
 <CA+JhTNTDE_orbEj5EV1VXjSB+tNWNmNQdSR9Q07aKZH5eWD8oA@mail.gmail.com>
 <56593251.90705@aldan.algebra.com>
Cc: freebsd-fs <freebsd-fs@freebsd.org>
From: Julian Elischer <julian@freebsd.org>
Message-ID: <56597B78.6060203@freebsd.org>
Date: Sat, 28 Nov 2015 18:01:28 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56593251.90705@aldan.algebra.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Nov 2015 10:01:55 -0000

On 28/11/2015 12:49 PM, Mikhail T. wrote:
> On 27.11.2015 22:30, alex.burlyga.ietf alex.burlyga.ietf wrote:
>> Is the file on NFS mount by any chance?
> I don't have an ongoing problem -- I just want to investigate and, if
> sufficiently easy, implement a solution...
are you allowed to reboot?

fsdb may be your answer to relink it and then reboot, causing fsck to 
correct the linkage counts.

>