Date: Mon, 8 Jun 2009 16:59:16 -0300 From: =?ISO-8859-1?Q?Sylvio_C=E9sar_Teixeira_Amorim?= <scjamorim@bsd.com.br> To: Michael Starling <mlstarling31@hotmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: Mounting ext3 under Freebsd Message-ID: <5859850b0906081259m2ba43694n9aa952641563c618@mail.gmail.com> In-Reply-To: <COL104-W5557D2F27F2A211C45887DD4470@phx.gbl> References: <COL104-W5557D2F27F2A211C45887DD4470@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
Linux: # tune2fs -s off /dev/sda1 # e2fsck -y /dev/sda1 FreeBSD: # cd /usr/ports/sysutils/e2fsprogs # make install all # mount -t ext2fs /dev/ad4s1 /media/linux Att Sylvio Cesar 2009/6/8 Michael Starling <mlstarling31@hotmail.com> > > Hello...This problem is driving me crazy as I thought it was fixed with t= he > release of 7.2. I can mount the ext3 filesystem from a previous linux dri= ve > but I can't access the data. it was my understanding that a patch has bee= n > incorporated into the 7.2 release ..Any ides as to why I might still be > seeing this issue?.Thanks > > > > 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.. > > _________________________________________________________________ > Hotmail=AE has ever-growing storage! Don=92t worry about storage limits. > > http://windowslive.com/Tutorial/Hotmail/Storage?ocid=3DTXT_TAGLM_WL_HM_Tu= torial_Storage_062009_______________________________________________ > freebsd-fs@freebsd.org<http://windowslive.com/Tutorial/Hotmail/Storage?oc= id=3DTXT_TAGLM_WL_HM_Tutorial_Storage_062009_______________________________= ________________%0Afreebsd-fs@freebsd.org>mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > --=20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D- Live free or die - UNIX* -=3D-=3D-=3D-=3D-=3D= -=3D-=3D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5859850b0906081259m2ba43694n9aa952641563c618>