From owner-freebsd-current Tue May 9 01:11:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA06030 for current-outgoing; Tue, 9 May 1995 01:11:00 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA06012 for ; Tue, 9 May 1995 01:10:08 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA00484; Tue, 9 May 1995 18:08:42 +1000 Date: Tue, 9 May 1995 18:08:42 +1000 From: Bruce Evans Message-Id: <199505090808.SAA00484@godzilla.zeta.org.au> To: uhclem@nemesis.lonestar.org Subject: Re: bin/389: Problem #FDIV024 Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Number: 389 >>Category: bin >>Synopsis: Simultaneous creation/deletion of dirs corrupts filesystem [FDIV024] I was able to reproduce the hang under -current: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 15 1669 159 0 -14 0 172 488 uihget D+ v2 0:00.05 ls -Fg 15 1619 160 2 -14 0 296 616 ufslk2 D v3 0:02.19 tar xf ../bin 15 1624 160 0 -18 0 296 620 vodead D v3 0:00.88 tar xf ../bin 15 1628 160 1 -14 0 296 616 ufslk2 D v3 0:00.77 tar xf ../bin 15 1632 160 0 -14 0 296 616 ufslk2 D v3 0:00.79 tar xf ../bin 15 1678 160 1 -14 0 160 476 ufslk2 D+ v3 0:00.04 ls -Fg The problems seem to be easier to reproduce on a small file system. I didn't see any on a new 512MB file system but I soon saw them on a 20000 block file system using bin.tar created from the current /usr/src/bin and running lots of tar xf's and rm -rf's concurrently. This was running as non-root. As root you have to worry about something unlinking "." and ".." directory entries. I don't think anything actually does, but tar --unlink might. Bruce