On Sun, Nov 06, 2005 at 12:40:10PM -0700, Roy Bixler wrote:
> I'm having filesystem problems and am looking for help.
> 
> But, first, by way of background, I have been using NetBSD for a while
> (since the 1.5.x days) and thought I was pretty well versed in it.
> Some time ago, when I was running v. 2.0, I bought an additional hard
> disk.  It is an IBM 73 G. SCSI drive.  I only partitioned a part of it
> figuring I would add partitions as I needed space.
> 
> I finally got the new disk going and used it for about a year under
> v. 2.0 and v. 2.0.2 with no trouble.  Then, yesterday, I upgraded to
> v. 2.1.  At first, it seemed that this was going to be a very smooth
> upgrade.  When I rebooted, everything came up just as before and,
> unlike previous upgrades, there was no need to tinker with the files
> in /etc.
> 
> The trouble began when I downloaded the latest pkgsrc.tar.gz file and
> used one of the partitions on the new disk to unpack the files.  In
> the middle of the extraction, the system froze hard and I to reboot
> using the power button.  "fsck" found a few errors, but that was
> expected.  I ran "fsck -f" on the partition afterwards just to be sure
> and it found no more errors.  When I tried "rm -rf pkgsrc", it failed
> when removing some of the subdirectories claiming that they "weren't
> empty."  When I did "ls -al pkgsrc", it showed an empty directory.
> 
> I figured there must be some pretty extensive corruption on the
> filesystem, so I backed up the other directories there and then did a
> "newfs" command on it.  That also failed.  It would get to a certain
> point and then give a message like
> 
> wtfs: write error: Undefined error: 0

Did the kernel print some error message in dmesg or /var/log/messages ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--