Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Mar 2020 15:16:37 -0600
From:      Gary Aitken <freebsd@dreamchaser.org>
To:        Michael Sierchio <kudzu@tenebras.com>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: "directory not empty", "no such file or directory" errors on upgrade
Message-ID:  <9265b3f4-2e15-1470-acb5-842f0dbae5dc@dreamchaser.org>
In-Reply-To: <CAHu1Y70h5B4qakT8=9mq7vARMdG-BU_neZw8=dqJubx7OUP31g@mail.gmail.com>
References:  <c6e1a79d-2ce9-52a3-9039-d5f3b727cc49@dreamchaser.org> <94e006d9-bf6e-52e2-c667-763385cdd98e@kicp.uchicago.edu> <20200312195259.GA1025@neutralgood.org> <CAHu1Y70h5B4qakT8=9mq7vARMdG-BU_neZw8=dqJubx7OUP31g@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 3/12/20 2:01 PM, Michael Sierchio wrote:
> Some quick observations – rmdir will fail if a directory is not empty, and
> rm -rf will fail if a file has the schg flag set.  A possible brute force
> solution to this is
> 
>> chflags -R 0 <dir>
>> rm -rf <dir>
> 
> 
> 
> On Thu, Mar 12, 2020 at 12:53 PM Kevin P. Neal <kpn@neutralgood.org> wrote:
> 
>> On Thu, Mar 12, 2020 at 02:09:33PM -0500, Valeri Galtsev wrote:
>>>
>>>
>>> On 2020-03-12 14:03, Gary Aitken wrote:
>>>> Upgrading from 11.2-RELEASE to 11.3-RELEASE
>>>>
>>>> The final invoke of freebsd-update install completed with the following
>>>> messages:
>>>>
>>>> ///usr/src/sys/pc98/include/acpica_machdep.h  no such file or directory
>>>> rmdir: ///usr/src/contrib/ofed/usr.lib        directory not empty
>>>> rmdir: ///usr/src/contrib/ofed/usr.bin        directory not empty
>>>> rmdir:
>> ///usr/src/contrib/llvm/tools/lldb/source/Plugins/InstrumentationRuntime/ThreadSanitizer
>>>> directory not empty
>>>> rmdir:
>> ///usr/src/contrib/llvm/tools/lldb/source/Plugins/InstrumentationRuntime/AddressSanitizer
>>>> directory not empty
>>>
>>> I would unmount filesystem and run fsck on it first.
>>
>> And add the "-f" flag to fsck.

Doing the fsck appeared to have no effect, although I don't understand
why it says it was modified.  Or does a -f prevent display of things
found to be fixed?:

# mount -fur /dev/ada0p2
# fsck -f /dev/ada0p2

SAVE DATA TO FIND ALTERNATE SUPERBLOCKS? [yn] y

** Last Mounted on /
** Roof file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
624589 files, 5541279 used. 12482048 free (106480 frags, 1546946 blocks, 0.6% fragmentation)

***** FILE SYSTEM IS CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****	

I understand the reasoning behind the fsck, but that would only
be part of the problem.  Are those directories supposed to be repopulated
with more recent versions?  Or should they simply be removed?
If they need to be repopulated, how does one repopulate them?

Thanks,

Gary




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?9265b3f4-2e15-1470-acb5-842f0dbae5dc>