deleting lost+found directory

[Kris Kennaway]

On Sat, Mar 06, 2004 at 04:03:35PM -1000, Vincent Poy wrote:

> > > > > > They're just directories, remove them in the usual way.
> > > > >
> > > > > 	Tried that, didn't work...
> > > >
> > > > > root at bigbang [4:00pm][/mnt/usr/lost+found] >> rm -rf *
> > > > > rm: #5558272: Directory not empty
> > > > > rm: #7018496: Directory not empty
> > > > > rm: #7206914: Directory not empty
> > > > > rm: #7254025: Directory not empty
> > > > > rm: #7254167: Directory not empty
> > > >
> > > > Unmount the filesystem and run fsck again (e.g. with the -f flag).
> > > > You seem to have additional filesystem corruption here.
> > >
> > > 	I did fsck with the -fy flag just now and this is what it says:
> > >
> > > UNREF DIR  I=471104  OWNER=root MODE=40755
> > > SIZE=512 MTIME=Mar  1 04:00 2004
> > > RECONNECT? yes
> > >
> > > SORRY. NO SPACE IN lost+found DIRECTORY
> > > UNEXPECTED SOFT UPDATE INCONSISTENCY
> >
> > Is the disk full or out of inodes?
> 
> 	Not sure about the inodes but the disk is at 0% capacity as ad2s1a
> doesn't have any problems.  ad2s1d is the one where I rm -rf . since that
> is used to do a dump,restore of /usr.

I don't understand which disk is which..can you please describe your
configuration in more detail?

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040306/18413e9a/attachment.bin