From owner-freebsd-bugs@FreeBSD.ORG Wed Nov 28 12:17:42 2007 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55A5016A41B; Wed, 28 Nov 2007 12:17:42 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.233.200]) by mx1.freebsd.org (Postfix) with ESMTP id DDC8513C468; Wed, 28 Nov 2007 12:17:41 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru (swsoft-msk-nat.sw.ru [195.214.232.10]) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id lASCHbSc023943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Nov 2007 15:17:39 +0300 (MSK) Received: from vova by vbook.fbsd.ru with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IxLrF-000LPp-Qu; Wed, 28 Nov 2007 15:17:37 +0300 From: Vladimir Grebenschikov To: Remko Lodder In-Reply-To: <474D56B2.4080409@FreeBSD.org> References: <200711281055.lASAtkjO075937@freefall.freebsd.org> <1196248411.15014.25.camel@localhost> <474D5261.9070806@FreeBSD.org> <1196250328.15014.29.camel@localhost> <474D56B2.4080409@FreeBSD.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Wed, 28 Nov 2007 15:17:37 +0300 Message-Id: <1196252257.15014.40.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/118300: fsck -y failed to cure UFS2 volume with lost '.' entry in one directory X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2007 12:17:42 -0000 On Wed, 2007-11-28 at 12:53 +0100, Remko Lodder wrote: > Vladimir Grebenschikov wrote: > > On Wed, 2007-11-28 at 12:34 +0100, Remko Lodder wrote: > >> Vladimir Grebenschikov wrote: > >>> On Wed, 2007-11-28 at 10:55 +0000, remko@FreeBSD.org wrote: > >>>> Synopsis: fsck -y failed to cure UFS2 volume with lost '.' entry in one directory > >>> It is very concrete problem report - > >>> "fsck -y failed to cure UFS2 volume with lost '.' entry in one > >>> directory" > >>> > >>> I have UFS2 volume, and fsck -y reports that it cures it, but actually > >>> it has inconsistencies after that. > >>> > >>> Do you think that it is not a problem ? > >>> > >>> Please reopen PR. > >>> > >> Hello, > >> > >> No I will not reopen the ticket till more information is available that > >> shows that this is indeed a bug that should be fixed. It could just be > >> a combination of problems on your local end which are not actually a bug > >> in the code or something. > > > > What else information do you want to see here ? I'll provide. > > > > It should be reproducable on other hardware as well if this is a real > bug, I pretty sure, that everybody who will mount my volume will see the same problem. > so perhaps you can printout more information on the /compat/linux > directory which is giving you problems, are the directories all there > that should 'support' the problematic missing ``.`` ? etc. Looks like we are speaking on different languages. Once again: 1. only directory that has a problem is /compat/linux/usr/lib/locale/af_ZA/ 2. IMHO contents of all other part of /compat/linux is irrelevant here, but if anybody think that it is relevant I may provide find /compat/linux/ output or any else. 3. for my knowledge I've provide enough information about broken directory and its entries. I am happy to provide more, if anybody points me what to provide. > I am not a FS expert, so hence the reasoning to poke the fs mailinglist > since there are people with much more clue then me over there. If they > agree this is a real problem and should be fixed, I will surely reopen > the ticket and include usefull information in it so that we can keep > track of the PR etc. For the moment this still does not seem like a PR > to me but perhaps a local value or something that messed up which might > just not be a bug but a local problem >From my point it is clearly malfunction of fsck - it failed to fix volume. > (that does not mean that is not a problem for you of course). For me it is rather simple to fix problem by hands (with fsdb - as I suggested in PR or just reformat volume with newfs). But my main intention was - to improve quality of fsck by reporting problem and providing debug/verify/etc cycle. If such FS problem happens for me it may happens for everybody else, with more or less probability. > > I've write to fs@freebsd.org already with no any feedback for three > > days: > > > > People are busy so it would be unfair to have them reply within a > certain timeframe right? You could just follow-up on it and reply > 'did someone have the time to look at this already and/or what else > can I do to provide more valuable information?' > > Someone will reply eventually and an occassional friendly reminder > can be greatly appreciated :) > > Cheers > remko > -- Vladimir B. Grebenschikov vova@fbsd.ru