> Please try the patch below.
Thank you - it helped.
> > As for R/W support, I think that this option should probably
> > not be visible in the "kernel for the masses" line,
> It is marked experimental, so it is not in the "kernel for the
> masses". Also, Configure.help has a clear warning about the state of
> this code. If somebody asks for experimental code, and ignores the
> warning, they should know how to recover from data loss.
How is the policy regarding experimental code
in the stable kernels? I see a difference between
"perhaps won't work" and "this can trash your data".
In the second case the config should probably
scream loudly and not hope that the Joe Random User
clicks on the help button ...
> > I am able to mount the smaller one, but the
> > bigger one says "kmalloc: Size (503808) too large" to
> > the kernel log and refuses to mount.
>
> This sounds serious. Could you please add -DDEBUG to ntfs/Makefile,
> and then do
>
> echo 4095 >/proc/sys/fs/ntfs-debug
>
> When mounting, this will produce a lot of output. I'd be interested in
> some of it :-)
Well - this ends relatively early compared to the output of
the successfull mount:
ntfs_read_super
lock_super
Done reading boot block
Going to init volume
MFT record at cluster 0x8
Done to init volume
set_blocksize
kmalloc: Size (503808) too large
unlock_super
read_super: done
I have added a debug output before the ntfs_malloc
right after the set_blocksize - vol->mft_recordsize
is the 503808 (0x7b000) and vol->clustersize is 2048.
Regards
-- Stano
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/