On Tue, 4 Mar 2008, Evan Dandrea wrote: > > Good evening, > > I am one of the developers responsible for getting Wubi, the Windows > Ubuntu Installer, properly integrated into Ubuntu. For those of you who > are not familiar with the project, Wubi lets a user install Linux inside > Windows by creating a loopback ext3 filesystem on the Windows NTFS > partition. > > In testing this I believe I've uncovered a bug in ntfs-3g. I can > trigger this bug reliably by doing an install using the amd64 version of > Wubi and Ubuntu on VMWare, but user testing seems to indicate that this > does not effect amd64 on bare metal. The install itself completes > without issue, but upon rebooting ntfs-3g bails out, producing the > attached log file. > > Any help or suggestions will be much appreciated. > > We are using ntfs-3g 1.1120. If you think this may be fixed in the > latest version, I can work to get that in the Ubuntu archive.
Please see: http://forum.ntfs-3g.org/viewtopic.php?p=3039&sid=d3d5b23ad44e623f8bb2c238d7c3e83e ------------------------------------------------------------------------------ szaka Lead Developer Miklos replied: the problem seems to be with the FUSE kernel module from the FUSE 2.7.2 package using with the latest Linux kernel 2.6.24. Please use the FUSE kernel module included in Linux kernel 2.6.24, that one must work fine. ----------------- Thunfisch thanks for the hint! I compiled FUSE into the kernel instead of building the module from the project's sources. Now everything works fine. ------------------------------------------------------------------------------ If Ubunutu uses the FUSE kernel module from the fuse-2.7.2 package, tell them to use the one from the kernel or try the one from fuse-2.7.3, maybe it fixes that bug, but better look into the changelog of fuse-2.7.3 to be sure that it's safe to use with 2.6.24 and newer. BTW: This link was the first hit when searching for balance_dirty_pages_ratelimited_nr ntfs which is the function is is printed on top of the kernel stack trace. That is not the function where the oops occured, but it's a function which does not show up that often. Note: NTFS-3G is a pure userspace driver, no code of ntfs-3g is in the kernel. So whenever you see a kernel oops like this in your log, it can't be NTFS-3G itself. Linux version 2.6.24-11-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu1)) #1 SMP Fri Feb 29 21:26:31 UTC 2008 (Ubuntu 2.6.24-11.17-generic) BTW: /etc/rcS.d/S18mounthost: 68: awk: not found /etc/rcS.d/S18mounthost: 68: awk: not found awk seems to be missed by that mount script. Here the oops from your log: * Checking minimum space in /tmp... SMP CPU 0 Pid: 2387, comm: mount.ntfs Not tainted 2.6.24-11-generic #1 get_dirty_limits+0x102/0x1e0 RSP: 0018:ffff81002fa4bae8 EFLAGS: 00010246 RAX: 0000000000012400 RBX: 0000000000002480 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff81002cf34840 RDI: ffffffff80690158 RBP: ffff81002cf347b8 R08: 28f5c28f5c28f5c3 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff81002fa4bba0 R13: ffff81002fa4bbb0 R14: ffff81002fa4bba8 R15: 0000000000000600 FS: 00007f725c6066e0(0000) GS:ffffffff805b1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00007fff35c55f28 CR3: 000000002f947000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process mount.ntfs (pid: 2387, threadinfo ffff81002fa4a000, task ffff81002cecef80) Stack: 0000800000000000 0000000000000008 0000000000000400 0000000000000400 0000000000000000 ffff81002cf347b8 ffff81002ec024d8 ffffffff8028795a ffff81002ef0e820 ffff81002fa4bb58 0000000000000000 ffff81002cf34818 Call Trace: balance_dirty_pages_ratelimited_nr+0x1aa/0x360 block_write_end+0x47/0x90 generic_file_buffered_write+0x1fb/0x6b0 :fuse:fuse_dev_read+0x277/0x4d0 current_fs_time+0x1e/0x30 __generic_file_aio_write_nolock+0x24f/0x400 generic_file_aio_read+0xff/0x1b0 generic_file_aio_write_nolock+0x2f/0x90 do_sync_write+0xd9/0x120 autoremove_wake_function+0x0/0x30 do_readv_writev+0x186/0x230 thread_return+0x3a/0x57b vfs_write+0xed/0x190 sys_pwrite64+0x84/0xa0 system_call+0x7e/0x83 Code: 48 f7 f1 49 89 04 24 4c 8b 05 90 8b 40 00 48 8b 35 91 8b 40 get_dirty_limits+0x102/0x1e0 RSP <ffff81002fa4bae8> ---[ end trace 1e56471a6dca7063 ]--- Buffer I/O error on device loop0, logical block 957332 lost page write due to I/O error on loop0 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
