On 2/24/24 1:34 PM, Samuel Sieb wrote:
On 2/24/24 12:16, home user wrote:
> On 2/23/24 2:34 PM, Jon LaBadie wrote:
>> On Fri, Feb 23, 2024 at 12:19:51PM -0700, home user wrote:
>>> On 2/23/24 5:44 AM, George N. White III wrote:
>>>> On Thu, Feb 22, 2024 at 2:22 PM home user <mattisonw(a)comcast.net
<mailto:mattisonw@comcast.net>> wrote:
>>>>
>>>
>>>>
>>>> Is there anything in your /boot/lost+found?
>>>
>>> /boot/lost+found/:
>>> total 20
>>> drwx------. 2 root root 12288 Mar 17 2013 .
>>> dr-xr-xr-x. 6 root root 5120 Feb 22 20:21 ..
>>> -bash.12[boot]:
>>>
>>> But what is odd is the ls -l output for /boot/lost+found/ itself. Why is an
empty directory taking up 12288 bytes? Other directories that are not empty are only
taking up 1024 bytes.
>>
>> Directories expand in size when a lot of directory entries exist.
>> They do not shrink when those entries are removed.
>>
>> You can manually shrink it by rmdir the L&F directory then recreate it.
>> But do you really care about 11K bytes?
>>
>
> Something I did not know. Thank-you.
>
> You're right, it's only 11K. Relative to the original problem, not
significant.
That directory is also special. There might be consequences for recreating it. I
don't know if it's accessed by name or inode.
That's the first I've ever heard of that! I learn something new once in a while.
Thank-you.
I'm definitely leaving it.