From owner-freebsd-fs@FreeBSD.ORG Mon Jun 8 19:31:17 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F945106564A for ; Mon, 8 Jun 2009 19:31:17 +0000 (UTC) (envelope-from mlstarling31@hotmail.com) Received: from col0-omc4-s13.col0.hotmail.com (col0-omc4-s13.col0.hotmail.com [65.55.34.215]) by mx1.freebsd.org (Postfix) with ESMTP id 1E80F8FC1C for ; Mon, 8 Jun 2009 19:31:17 +0000 (UTC) (envelope-from mlstarling31@hotmail.com) Received: from COL104-W55 ([65.55.34.199]) by col0-omc4-s13.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Jun 2009 12:18:33 -0700 Message-ID: X-Originating-IP: [69.182.171.61] From: Michael Starling To: Date: Mon, 8 Jun 2009 15:18:33 -0400 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 08 Jun 2009 19:18:33.0122 (UTC) FILETIME=[E9F86820:01C9E86D] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Mounting ext3 under Freebsd X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 19:31:17 -0000 Hello...This problem is driving me crazy as I thought it was fixed with the= release of 7.2. I can mount the ext3 filesystem from a previous linux driv= e but I can't access the data. it was my understanding that a patch has been = incorporated into the 7.2 release ..Any ides as to why I might still be see= ing this issue?.Thanks uname -a=20 FreeBSD BSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 200= 9 OK..So here's what's happening after shutting down the linux box and placin= g the disk inside the BSD box. tune2fs -l /dev/ad6s1 tune2fs 1.41.4 (27-Jan-2009) Filesystem volume name: Last mounted on: Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filet= ype sparse_super large_file Filesystem flags: signed_directory_hash=20 Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 15269888 Block count: 61049000 Reserved block count: 3052450 Free blocks: 36030598 Free inodes: 15269372 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1009 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Fri May 29 10:44:59 2009 Last mount time: Mon Jun 8 09:57:59 2009 Last write time: Mon Jun 8 13:33:00 2009 Mount count: 5 Maximum mount count: 21 Last checked: Fri May 29 10:44:59 2009 Check interval: 15552000 (6 months) Next check after: Wed Nov 25 09:44:59 2009 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group wheel) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 0904fd61-260b-467c-ae33-ba484e5d9f64 Journal backup: inode blocks Now it says the filesystem is clean so I mount it with. mount -t ext2fs /dev/ad6s1 /mnt ls /mnt ls: /mnt: Bad file descriptor OK so we look at tune2fs again and the filesystem is "not clean" now.=20 tune2fs -l /dev/ad6s1 tune2fs 1.41.4 (27-Jan-2009) Filesystem volume name: Last mounted on: Filesystem UUID: fbb12204-b8fc-4f29-aab8-d2d9dd1ccbce Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filet= ype sparse_super large_file Filesystem flags: signed_directory_hash=20 Default mount options: (none) Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 15269888 Block count: 61049000 Reserved block count: 3052450 Free blocks: 36030598 Free inodes: 15269372 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1009 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Fri May 29 10:44:59 2009 Last mount time: Mon Jun 8 09:57:59 2009 Last write time: Mon Jun 8 13:37:47 2009 Mount count: 5 Maximum mount count: 21 Last checked: Fri May 29 10:44:59 2009 Check interval: 15552000 (6 months) Next check after: Wed Nov 25 09:44:59 2009 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group wheel) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 0904fd61-260b-467c-ae33-ba484e5d9f64 Journal backup: inode blocks So I umount the filesystem and run e2fsck with. e2fsck /dev/ad6s1 e2fsck 1.41.4 (27-Jan-2009) /dev/ad6s1: clean=2C 516/15269888 files=2C 25018402/61049000 blocks The filesystem now reports as "clean" again....So this is just a vicious cycle which I can't break..aaaaaaaaaaahhhhhhhhhhhhhhhhhhh....Please help...Losing sanity.. _________________________________________________________________ Hotmail=AE has ever-growing storage! Don=92t worry about storage limits.=20 http://windowslive.com/Tutorial/Hotmail/Storage?ocid=3DTXT_TAGLM_WL_HM_Tuto= rial_Storage_062009=