Date: Fri, 11 Mar 2011 14:23:04 -0600 From: Ade Lovett <ade@FreeBSD.org> To: Aryeh Friedman <aryeh.friedman@gmail.com> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: sysutils/dolly breaks cvs Message-ID: <86F0820E-116B-4258-A970-15A83FA9EF65@FreeBSD.org> In-Reply-To: <AANLkTinsZ8TJqUJy1LUyuJeRbrU9SZCi6%2B9Q6MiRfnZy@mail.gmail.com> References: <AANLkTimyRDqQDftvhmg4V10CeW=9jW2=tf99LzKkBMwn@mail.gmail.com> <20110311163040.GB9541@darklight.org.ru> <AANLkTik9PXY5R2qPg--k91miO9Twk0PtOpZPEadJG%2BYj@mail.gmail.com> <20110311171155.GB21078@atarininja.org> <AANLkTinsZ8TJqUJy1LUyuJeRbrU9SZCi6%2B9Q6MiRfnZy@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 11, 2011, at 11:52 , Aryeh Friedman wrote: > If I know the inode how can I force the inode to be cleared even if > the filename is illegal? Usual disclaimers apply about backing up your data prior to this. Reboot single user. # clri /dev/ad1d inode_number # fsck /dev/ad1d substitute the actual device name, of course. -aDe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86F0820E-116B-4258-A970-15A83FA9EF65>