Messages in this thread | | | From | Marcin Gibuła <> | Subject | Re: Windows Logical Disk Manager error | Date | Fri, 1 Oct 2004 16:26:07 +0200 |
| |
> I would not advise you to use volume6 without the md driver. You are > then missing the last 32kb off the end and you never know when they
Well, I can't even build it... mdadm failes and driver complains with md: Dev sda2 smaller than chunk_size: 0k < 32k
Different chunk size doesn't make any difference.
> direction. Fortunately you can fix this case by using the "--rounding=" > parameter to mdadm. So if you have a cluster size of 4k try > --rounding=4. (If you don't know your cluster size enable debugging in > the ntfs driver and then do the mount and "dmesg | grep cluster_size" > will tell you the answer. To enable debugging in the driver it must be > compiled with debugging enabled and you need to, as root, do: "echo 1 > > /proc/sys/fs/ntfs-debug" after loading the module if modular and before > doing the mount command.)
According to ntfs driver output my cluster size is indeed 4kb, but it still failes to read mounted fs.
Error is now: NTFS-fs error (device md1): ntfs_readdir(): Actual VCN (0x20006500680054) of index buffer is different from expected VCN (0x4). Directory inode 0x5 is corrupt or driver bug.
Oh, and my system (and kernel) is x86-64 if it matters.
> "chkdsk /f" on it fixed it in that particular case (even though chkdsk > reported no errors, apparently it fixed them without telling anyone!). > So this is worth trying before you start messing around with --rounding= > and mdadm.
I've tried that. No effect though.
-- mg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |