From owner-freebsd-questions@FreeBSD.ORG Wed Jun 11 03:16:45 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C802637B401 for ; Wed, 11 Jun 2003 03:16:45 -0700 (PDT) Received: from plexcom.no (mail.plexcom.no [80.232.113.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D98743F3F for ; Wed, 11 Jun 2003 03:16:44 -0700 (PDT) (envelope-from sgt@plexcom.no) Received: from neo.plex.no [80.232.113.246] by plexcom.no with ESMTP (SMTPD32-7.07) id A3429E00E8; Wed, 11 Jun 2003 12:24:02 +0200 From: =?ISO-8859-1?Q?Torbj=F8rn?= Kristoffersen To: freebsd-questions@freebsd.org Content-Type: text/plain Organization: Plex Communications AS Message-Id: <1055326611.4818.111.camel@neo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 11 Jun 2003 12:16:51 +0200 Content-Transfer-Encoding: 7bit Subject: Serious filesystem problem (FreeBSD 4.8) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 10:16:46 -0000 Hi We have a fileserver, an Adaptec 3410S RAID card and a RAID 01 partition that we use for network storage. It's shared with NFS and SMB. A directory that's being shared to an SMB client, has lately encountered many weird problems. Suddenly files/directories turn into something similar to this: # ls -l drwxr-xr-x 20788 administrator administrator 7440289925196497251 Sep 11 2004 brokendir # rm -rf aa rm: aa: Directory not empty # ls -la brokendir # Some directories/files are broken like this: # du -sh some_dir/ du: fts_read: No such file or directory # cd some_dir/ some_dir# find . ./users ./users/12a ./users/12a/main.mbx find: fts_read: No such file or directory The worst thing is, more and more files and directories become corrupt, albeit not very often. What should we do? I have attached dmesg output in this mail. We use Samba Version 2.2.6pre2. One thing definately worth mentioning is: These problems began occurring a week ago, when one of the disks in the RAID 01 setup failed. We simply inserted a new disk, and had it rebuilt, the Adaptec Storage Manager Pro reports healthy disks... And the other directories in the RAID 01 partition, are also working fine. Anyone encountered something similar? TIA -Torbjorn