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 drive but I can't access the data. It was my understanding that a patch has been incorporated into the 7.2 release ..Any ideas as to why I might still be seeing this issue?. Again, some people are telling me that it was fixed in relase 7.2 while others say it wasn't and I need to apply a patch..I tried the patch but it fails...



uname -a
FreeBSD BSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009

OK..So here's what's happening after shutting down the linux box and placing the disk inside the BSD box.



tune2fs -l /dev/ad6s1

tune2fs 1.41.4 (27-Jan-2009)

Filesystem volume name: <none>

Last mounted on: <not available>

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 filetype sparse_super large_file

Filesystem flags: signed_directory_hash

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.



tune2fs -l /dev/ad6s1

tune2fs 1.41.4 (27-Jan-2009)

Filesystem volume name: <none>

Last mounted on: <not available>

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 filetype sparse_super large_file

Filesystem flags: signed_directory_hash

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, 516/15269888 files, 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..

FreeBSD supports ext2/ext3 created with Inode size 128, there were some patches to add support for 256 Inode version, but I do not remember if they have been MFC'd, check lists.freebsd.org for details.

I was finally able to get this working after coming in contact with a saint of a man on the freebsd-fs mailing list. He stuck with me and worked on this for an entire day until we were able to resolve the issue..The problem was that after I had installed 7.2, I used cvsup to update my source files however in the file I specified *default tag=. instead of *default tag=RELENG_7_2..So I'm sure you can guess what happened next...So the patch wasn't working because the files under /usr/src/sys/gnu/fs/ext2fs/ were from the CURRENT release. That would explain the patch failing because ext2 is already fixed in the 8.0 Release.....So I was basically trying to patch an already patched ext2fs and recompile the 8.0 source files agianst the 7.2 Kernel.......Anyhow, this has been a cautionary tale for me in my new ventures into FreeBSD......