buggered file system
Mark Russell
freebsd at mark.net.au
Thu Apr 15 08:06:23 PDT 2004
On Thu, 15 Apr 2004, Ruslan Ermilov wrote:
> On Thu, Apr 15, 2004 at 01:38:32AM +1000, Mark Russell wrote:
> > Whilst burning a bunch of cd's my notebook running current of 21/03/04
> > decided to hang.
> >
> > Now I have an extremely full file system, I've found a directory that
> > refuses to be deleted and I'm wondering if there is a way I can save this
> > without backing up and reinstalling, hey I'm lazy.
> >
> > Filesystem 1K-blocks Used Avail Capacity Mounted on
> > /dev/ad0s1a 253678 57508 175876 25% /
> > devfs 1 1 0 100% /dev
> > /dev/ad0s1d 36654788 4857574508 -4823852102 14405% /usr
> > linprocfs 4 4 0 100%
> > /usr/compat/linux/proc
> >
> > root at notebook: /usr/lost+found > rm -rf diebastard
> > rm: diebastard: Directory not empty
> >
> > root at notebook: /usr/lost+found > ls -la
> > total 6
> > drwxr-xr-x 3 root wheel 512 Apr 15 01:33 ./
> > drwxr-xr-x 20 root wheel 512 Apr 14 22:04 ../
> > drwxrwxrwx 3 root mark 512 Apr 15 2004 diebastard/
> >
> > fsck /usr
> > ** /dev/ad0s1d
> > ** Last Mounted on /usr
> > ** Phase 1 - Check Blocks and Sizes
> > fsck_ufs: cannot alloc 3221301040 bytes for inoinfo
> >
> Tried an alternate superblock with fsck(8)?
>
Thats one thing I didn't try, I gave up and reinstalled anyway.
Thanx
--
You cant use the word sex on the internet -- Marge Simpson
More information about the freebsd-current
mailing list