Default inode number too low in FFS nowadays?

Doug Barton dougb at FreeBSD.org
Sun Nov 6 22:04:43 UTC 2011


On 11/04/2011 07:16, Alexander Best wrote:
> On Fri Nov  4 11, Miroslav Lachman wrote:
>> Matt Connor wrote:
>>>
>>> On Nov 3, 2011, at 5:43 AM, Ivan Voras<ivoras at freebsd.org>  wrote:
>>>
>>>> On 02/11/2011 12:57, Borja Marcos wrote:
>>
>> [...]
>>
>>>> Did you forget to do "make clean" after "make install" on several large
>>>> ports?
>>>>
>>>> But yes, the ports tree is getting a bit unwieldy. On the other hand,
>>>> did you fsck the file system lately?
>>>>
>>>
>>> cd /usr/ports/ports-mgmt/portupgrade&&  make install clean
>>>
>>> portsclean -CD
>>>
>>> That's a quick way to clean out all the clutter.
>>
>> Installing ruby and portupgrade is really big overhead to simple task, 
>> which can be done by:
>>
>> cd /usr/ports && make clean
>>
>> or with find:
>>
>> find /usr/ports/ -depth 3 -name "work" -exec rm -r {} +
> 
> ...or with 'rm -rf /usr/ports/*/*/work'

This comes up periodically, and for some reason no one pays attention to
all the work that's been done in the past to verify that the fastest
method is:

find /usr/ports -maxdepth 3 -type d -name -work -exec rm -rf {} \;

Of course, the best solution by far is to set WRKDIRPREFIX to a path
with adequate space, preferably something other than /usr/obj.


hth,

Doug

-- 

		"We could put the whole Internet into a book."
		"Too practical."

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/



More information about the freebsd-fs mailing list