Date: Fri, 4 Nov 2011 16:04:21 +0000 From: Alexander Best <arundel@freebsd.org> To: Chris Rees <crees@freebsd.org> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>, Ivan Voras <ivoras@freebsd.org> Subject: Re: Default inode number too low in FFS nowadays? Message-ID: <20111104160421.GA43288@freebsd.org> In-Reply-To: <CADLo83-sTOpfjLDT2gFa9vyvh%2Bw8OVfq-ADm8jar49YzQknjPw@mail.gmail.com> References: <B888842A-7DB4-491B-93E3-A376745019F5@sarenet.es> <j8u2af$chv$1@dough.gmane.org> <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> <4EB3C63F.2060805@quip.cz> <20111104141626.GA28925@freebsd.org> <CADLo83-sTOpfjLDT2gFa9vyvh%2Bw8OVfq-ADm8jar49YzQknjPw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri Nov 4 11, Chris Rees wrote:
> On 4 November 2011 14:16, Alexander Best <arundel@freebsd.org> wrote:
> > On Fri Nov 4 11, Miroslav Lachman wrote:
> >> Matt Connor wrote:
> >> >
> >> >On Nov 3, 2011, at 5:43 AM, Ivan Voras<ivoras@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'
> >
>
> I almost had the strength of mind to stay out of this....
>
> BUT you could well run into argument list too long issues there
> (considering the insane number of inodes used), so you're probably
> better off getting around that using the builtin echo:
>
> # echo /usr/ports/*/*/work | xargs rm -r
right i forgot about long argument lists. will -prune speed up the above
find(1) command invocation?
cheers.
alex
>
> Since you're doing stuff like that, find is probably more appropriate.
>
> Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111104160421.GA43288>