Hi,
I was cleansing /usr/obj after a panic to see if I could reproduce it and
I have this slight oddity:
[root@daemon:/usr/obj] (32) # rm -rf work/
rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty
rm: work/FreeBSD/src/gnu: Directory not empty
rm: work/FreeBSD/src: Directory not empty
rm: work/FreeBSD: Directory not empty
rm: work/: Directory not empty
[note I already did chflags]
[root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/
[root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll
total 2
1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./
1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ../
[root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (35) # cd ..
[root@daemon:/usr/obj/work/FreeBSD/src/gnu] (36) # ll
total 3
1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./
1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:33 ../
1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 usr.bin/
I have no idea what's wrong here.
After the panic however I did get some softupdates inconsistencies, such
as: DUPs, Block counts, even an internal error: dups with -p.
I'd love to hear some ideas about how to solve this.
--
Jeroen Ruigrok van der Werven asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist BSD: Technical excellence at its best
Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
