Re: [announcement] ntfs-3g: open source read-writedriver - bugreport (???)

Hi,

Thanks for the bug report.

Can you capture a metadata of the bad partition?
That can be done by repeating what you did (except the chkdsk),
unmounting, and doing the following while the partition is unmounted:
ntfsclone --metadata --output ntfsmeta.img /dev/hdb3
bzip2 ntfsmeta.img

And send the resulting file (usually about 0.5-8 MB), via mail, or put
it somewhere for download   (please don't send large files to the
mailing list. A private mail would be great). If you need some ftp
account to upload the file, contact me privately.

The problem can be probably indentified by examining the metadata.

For more details on capturing metadata, see
http://wiki.linux-ntfs.org/doku.php?id=ntfsclone

Thanks

On 7/19/06, Boross Péter wrote:
> Welcome!
>
> I'm using an AMD Duron 850 MHz with VIA chipset; with UHU-Linux 1.2
> (kernel 2.6.9-19, but patched by UHU-developers) and Windows 2000 SP4 as
> "NTFS-maker".
>
> I tried yesterday the driver on the partition /dev/hdb3.
>
> FUSE install (from source): OK
> ntfs-3g install (from source): OK
>
>  > umount /dev/hdb3
>  > modprobe fuse
>  > ntfs-3g /dev/hdb3 /Win2000/NTFS-Tmp
> everything were OK.
>
> I made a new directory on /dev/hdb3, and copied a big (approx. 2GB) file
> into it with Midnight Commander. The file were copied succesfully. I
> made some ls -l commands to compare the source and target file lengts,
> it was OK. After it, I restarted the computer, again with UHU 1.2., but
> (with my default settings) the /dev/hdb3 were mounted with kernel NTFS
> in read-only mode (UHU disables the limited kernel-NTFS write access).
> The mc showed the new (previously made) directory on /dev/hdb3 in red,
> and I wasn't able to step into it. With the gnome nautilus filemanager
> the situation was the same.
> I started windows, the Total Commander were no able to change to the new
> directory too. I typed
>  > chkdsk d:\NTFS-Tmp /f ( in my computer, the /dev/hdb3 is mounted in
> windows into the NTFS-Tmp directory of the main drive D: )
> chkdsk found some inode and free space errors, it repaired them, and
> voilà: The new directory created under linux were disappeared.
> I were able to repeat it every time, without exception (with small(er)
> files too).
> I would use NTFS under linux. What do I miss?
> May be a problem if captive-NTFS (and its requirements, e.g. LUFS) is
> installed on the computer (although it was not used)?
>
> Thank you for your help
> Péter Boross
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Linux-NTFS-Dev mailing list
> Linux-NTFS-Dev@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/linux-ntfs-dev
>


-- 
Yuval Fledel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV