Date: Mon, 12 Jan 2009 11:14:50 +0100 From: raoul <rmgls@free.fr> To: pluknet <pluknet@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: ext3fs Message-ID: <20090112101450.DCA4A4C805F@smtp4-g21.free.fr>
next in thread | raw e-mail | index | archive | help
On Mon, 12 Jan 2009 12:34:42 +0300 pluknet <pluknet@gmail.com> wrote: > 2009/1/12 raoul <rmgls@free.fr>: > > > > Hi all, > > > > it seems on Current buildword from 4 January 2009 > > that ext3fs is confusing mount: > > ext2fs works fine; > > > > so my question: is ext3fs supported? > > > > here is my results: > > > > mount -t ext2fs /dev/ad4s2 /mnt => ok > > ls /mnt => Bad file descriptor > > with a LOR: > > > > GEOM_LABEL: Label ext2fs/debian removed. > > > > lock order reversal: > > 1st 0xd8518110 bufwait (bufwait) @ kern/vfs_bio.c:2443 > > 2nd 0xc4c31e00 dirhash (dirhash) @ ufs/ufs/ufs_dirhash.c:263 > > KDB: stack backtrace: > > db_trace_self_wrapper(c0b98baf,e6238898,c0831475,4,c0b941ba,...) at db_trace_self_wrapper+0x26 > > kdb_backtrace(4,c0b941ba,c4520878,c4523e18,e62388f4,...) at kdb_backtrace+0x29 > > _witness_debugger(c0b9b869,c4c31e00,c0bbaf87,c4523e18,c0bbac2d,...) at _witness_debugger+0x25 > > witness_checkorder(c4c31e00,9,c0bbac24,107,0,...) at witness_checkorder+0x839 > > _sx_xlock(c4c31e00,0,c0bbac24,107,d90c9894,...) at _sx_xlock+0x85 > > ufsdirhash_acquire(0,e,c4a49000,d85180b0,d90c9894,...) at ufsdirhash_acquire+0x35 > > ufsdirhash_remove(c4f6f960,d90c9894,894,e6238984,e6238980,...) at ufsdirhash_remove+0x14 > > ufs_dirremove(c4f6e10c,c4f9d618,500940c,0,0,...) at ufs_dirremove+0xe5 > > ufs_rename(e6238c1c,e6238c1c,e6238bcc,e6238b7c,e6238bcc,...) at ufs_rename+0xbe3 > > VOP_RENAME_APV(c0c975c0,e6238c1c,101,0,5009410,...) at VOP_RENAME_APV+0xa5 > > kern_renameat(c4fb6000,ffffff9c,85c9664,ffffff9c,85c9680,...) at kern_renameat+0x2b7 > > kern_rename(c4fb6000,85c9664,85c9680,0,e6238d2c,...) at kern_rename+0x36 > > rename(c4fb6000,e6238cf8,8,c0b9c07a,c0c73400,...) at rename+0x29 > > syscall(e6238d38) at syscall+0x2a3 > > Xint0x80_syscall() at Xint0x80_syscall+0x20 > > --- syscall (128, FreeBSD ELF32, rename), eip = 0x2824ed0b, esp = 0xbfbfd8bc, ebp = 0xbfbfd8e8 --- > > lock order reversal: > > 1st 0xc4f9f594 ufs (ufs) @ kern/vfs_mount.c:1190 > > 2nd 0xc4caedf4 devfs (devfs) @ /usr/src/sys/modules/ext2fs/../../gnu/fs/ext2fs/ext2_vfsops.c:918 > > KDB: stack backtrace: > > db_trace_self_wrapper(c0b98baf,e61c3a4c,c0831475,4,c0b941ba,...) at db_trace_self_wrapper+0x26 > > kdb_backtrace(4,c0b941ba,c4523db0,c4523ce0,e61c3aa8,...) at kdb_backtrace+0x29 > > _witness_debugger(c0b9b869,c4caedf4,c0b8b90e,c4523ce0,c4faff0f,...) at _witness_debugger+0x25 > > witness_checkorder(c4caedf4,9,c4faff0f,396,c4caee10,...) at witness_checkorder+0x839 > > __lockmgr_args(c4caedf4,80400,c4caee10,0,0,...) at __lockmgr_args+0x797 > > vop_stdlock(e61c3bb0,c0e1cee8,c4a729a4,80400,c4caed9c,...) at vop_stdlock+0x62 > > VOP_LOCK1_APV(c0c6f400,e61c3bb0,e61c3bd0,c0cab6a0,c4caed9c,...) at VOP_LOCK1_APV+0xa5 > > _vn_lock(c4caed9c,80400,c4faff0f,396,c4d28840,...) at _vn_lock+0x5e > > ext2_sync(c4a96280,1,c4a72900,4eb,0,...) at ext2_sync+0x283 > > dounmount(c4a96280,8000000,c4a72900,471,9,...) at dounmount+0x45c > > unmount(c4a72900,e61c3cf8,8,e61c3d38,c0c72a10,...) at unmount+0x2e0 > > syscall(e61c3d38) at syscall+0x2a3 > > Xint0x80_syscall() at Xint0x80_syscall+0x20 > > --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280d224f, esp = 0xbfbfe00c, ebp = 0xbfbfe0d8 --- > > GEOM_LABEL: Label for provider ad4s2 is ext2fs/debian. > > 1822]: speaker open error 2: No such file or directory. > > ssage repeated 3 times > > GEOM_LABEL: Label ext2fs/debian removed. > > GEOM_LABEL: Label for provider ad4s2 is ext2fs/debian. > > > > > > > > it is a journalized debian partition. > > > > to help here is the superblock report from tune2fs: > > > > tune2fs 1.41.3 (12-Oct-2008) > > Filesystem volume name: debian > > Last mounted on: <not available> > > Filesystem UUID: d9497b41-f521-4c61-981c-10ccb840ea59 > > Filesystem magic number: 0xEF53 > > Filesystem revision #: 1 (dynamic) > > Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery 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: 2260992 > > Block count: 9032546 > > Reserved block count: 451627 > > Free blocks: 7479934 > > Free inodes: 2027863 > > First block: 0 > > Block size: 4096 > > Fragment size: 4096 > > Reserved GDT blocks: 1021 > > Blocks per group: 32768 > > Fragments per group: 32768 > > Inodes per group: 8192 > > Inode blocks per group: 512 > > Filesystem created: Fri Dec 26 07:48:32 2008 > > Last mount time: Mon Jan 12 08:43:04 2009 > > Last write time: Mon Jan 12 08:43:04 2009 > > Mount count: 15 > > Maximum mount count: 20 > > Last checked: Sun Jan 4 13:31:26 2009 > > Check interval: 15552000 (6 months) > > Next check after: Fri Jul 3 14:31:26 2009 > > Reserved blocks uid: 0 (user root) > > Reserved blocks gid: 0 (group root) > > First inode: 11 > > Inode size: 256 > ^^^ > This prevents ext2/3 from mount. > See "256-byte inode support" thread on hackers@ Thanks for the hint i will look at this. Best regards raoul rmgls@free.fr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090112101450.DCA4A4C805F>