From owner-freebsd-questions@FreeBSD.ORG Sun Oct 24 17:38:45 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E1AD106564A for ; Sun, 24 Oct 2010 17:38:45 +0000 (UTC) (envelope-from modulok@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 26B1B8FC13 for ; Sun, 24 Oct 2010 17:38:44 +0000 (UTC) Received: by wyb42 with SMTP id 42so2579431wyb.13 for ; Sun, 24 Oct 2010 10:38:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=pXab+REuHRmxTbgOj448gf8nGR31SfGwkS6x/YgHunc=; b=SsU2lhvmMfv70QGRcS7oPj2s8bhFT10cGx/UI2qo99pjI+OJpCFxeA+F0opAEAlG6L rbJoeBiAaCcSq6W9yHKYeSk/XkpVIC8fKbHuRIcU9jH75DzRXN3/UXJc+oTn8iJNOREk 1phFLJiDCu2yP4lrOdQbdo0L8bWCYxbZtKS0U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=EMR6yHLfxY+fUd9XHhsR2gyP5r8BP2OPPbtXkLk4MkB4wlM5UR/bnlIqPGcAB75LNv T5e4o/BrM5Z9MZ44BrlhItnD5MU7ve0fNaTSKeuRPsKydN1qWp1ylfjHvA3R+0+GUjXn sKXl7GSNpdOYIcSTDmm1n6grNlW+4D1kUl9Uo= MIME-Version: 1.0 Received: by 10.227.138.7 with SMTP id y7mr5068584wbt.133.1287941923961; Sun, 24 Oct 2010 10:38:43 -0700 (PDT) Received: by 10.227.138.74 with HTTP; Sun, 24 Oct 2010 10:38:43 -0700 (PDT) Date: Sun, 24 Oct 2010 11:38:43 -0600 Message-ID: From: Modulok To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1 Subject: Weird file system corruption or something else? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2010 17:38:45 -0000 List, I have a disk image of a Windows machine I took via dd. It's shared on the local network from FreeBSD via samba. The disk image is read-only. I want to access files within the disk image from some Windows boxes, so I do this: mdconfig -a -t vnode -f image.bin mount_ntfs -o ro /dev/md0s1 ./mnt I then add the appropriate entry in my smb.conf file to share the 'mnt' directory. It worked... almost. PROBLEM: I can see files from the windows machines, but I cannot decend into any subdirectories or open any files unless they've first been listed or opened on FreeBSD. The file permission bits are correct, but the 'link' column in the 'ls -l' output on all files is '0', until I open a file or list the contents of a directory on FreeBSD. Thereafter, its normal i.e. '1' for regular files and so forth, and I can access the files from Windows as usual. I can issue a 'tree' command to automate the listing of directories on FreeBSD, thus changing their link number... so that I can access them from windows, but this all seems very strange. I don't want to have to open every file, before I can open any files from windows. The file system of the disk image wasn't corrupt when I took it, and dd had zero errors when it was created. I have no problem accessing files on the local FreeBSD. The disk image still matches the sha256 checksum from when I create it, so it hasn't since become corrupt. What's going on?! How do I fix this? Is there some mount option I missed? An mdconfig issue? A mount_ntfs bug? -Modulok-