Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Nov 2007 12:53:22 +0100
From:      Remko Lodder <remko@FreeBSD.org>
To:        vova@fbsd.ru
Cc:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/118300: fsck -y failed to cure UFS2 volume with lost '.' entry in one directory
Message-ID:  <474D56B2.4080409@FreeBSD.org>
In-Reply-To: <1196250328.15014.29.camel@localhost>
References:  <200711281055.lASAtkjO075937@freefall.freebsd.org>	 <1196248411.15014.25.camel@localhost> <474D5261.9070806@FreeBSD.org> <1196250328.15014.29.camel@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
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, 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.

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 (that does not mean that is not
a problem for you ofcourse).

> 
> 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

-- 
/"\   Best regards,                      | remko@FreeBSD.org
\ /   Remko Lodder                       | remko@EFnet
 X    http://www.evilcoder.org/          |
/ \   ASCII Ribbon Campaign              | Against HTML Mail and News



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?474D56B2.4080409>