I am converting a large file system from NTFS to ext3. This filesystem is a FC array (Dell 660F). Currently, I am copying the files from it to another PV660 that will be the new home through SMB. There HAS to be a better way. I have looked and so far can't find anything. I have tried mounting the array using the unsopported CentOS kernel (Can't remember version, 2.6.9_34.UNSUPPORTED, something like that) that has ntfs support compiled in. What's weird is it will see the drive, mount it RO (which is fine) and read some of the directories. What is weird is it cannot read all of the directories.
Here is what is being dumped to messages:
Jun 3 00:32:33 host2 kernel: NTFS driver 2.1.20 [Flags: R/W MODULE].
Jun 3 00:32:33 host2 kernel: NTFS volume version 3.1.
Jun 3 00:32:33 host2 kernel: NTFS-fs error (device sdd1): load_system_files(): Volume is dirty. Mounting read-only. Run chkdsk and mount in Windows.
Jun 3 00:32:33 host2 kernel: NTFS-fs error (device sdd1): ntfs_check_logfile(): The two restart pages in $LogFile do not match.
Jun 3 00:32:33 host2 kernel: NTFS-fs warning (device sdd1): load_system_files(): Failed to load $LogFile. Will not be able to remount read-write. Mount in Windows.
The volume is almost always dirty. It's on a SAN. It has hundreds of acceses to it simultaneously. It's windows. It a TERRIBLE file system. Hence the conversion.
Currently, I am getting a whopping 2-5 megs/second through samba on a gigabit link. The files are being dumped to a SAN, so I know that isn't the bottlneck. I am certain it's SAMBA and windows locking mechanism. They are webroots, so there's a ton of little files.
Has anyone experienced this log file issue with mounting a NTFS FS on linux? Was there any way to resolve it? Is there a faster way anyone has tried/can think of?
110 Media Group Inc
Dangit. Just realized that left shift-x key on my laptop doesn't work, but the right shift key-x does. Weird. Title should say EXT3.