public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: "Joseph K. Malek" <malekjo@aphrodite.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Broken NTFS
Date: Wed, 29 Nov 2000 12:28:32 -0700	[thread overview]
Message-ID: <20001129122832.A8639@vger.timpanogas.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1001129091726.14820A-100000@chaos.analogic.com> <Pine.LNX.4.21.0011290628350.2047-100000@fluffy.aphrodite.com>
In-Reply-To: <Pine.LNX.4.21.0011290628350.2047-100000@fluffy.aphrodite.com>; from malekjo@aphrodite.com on Wed, Nov 29, 2000 at 06:33:36AM -0800

On Wed, Nov 29, 2000 at 06:33:36AM -0800, Joseph K. Malek wrote:
> Hi all,
> 
> I have a broken NTFS, due to my own mistake of mounting the
> partition RW and moving a file instead of copying it....I've been poking
> around for an NTFS editing tool; only to find that this is easier said
> than done.  Does anyone have an NTFS repair tool for winnt 4 (I already
> have the ddk), or any idea where I can find one?
> 

I have a tool that will repair the damage caused to an NTFS volume by 
Linux.  Questions:

1.  Did you boot NT on the drive and did it become RAW?
2.  Have you run checkdisk against the drive, and if so, what happened?

If you answer yes to #1, you have probably already experienced permanent
data loss on the device.  Older NTFS versions on Linux would make changes
to the MFT without clearing the old journal file, then leave the drive
marked as "clean" to NT.  What can happen in this case is that NTFS 
on W2K will see the logfile, then attempt to roll out the changes.  In NT
the MFT is updated real time and the logfile is transacted after the fact.
This can (but not always) cause massive data loss on NTFS drives.  Anton
has fixed a lot of these issues on the newer code, but Linux NTFS
is still a very dangerous piece of software to use R/W (R/O works 
OK).

Do you need this tool?


Jeff

> thanks in advance!
> 
> -- 
> 
> .oO0Oo.|.oO0Oo.|.oO0Oo.|.oO0Oo.|.oO0Oo.|.oO0Oo.
> This message was made from 100% post-consumer
> recycled magnetic domains. No binary trees were
> destroyed to make it.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-29 19:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-27  3:35 access() says EROFS even for device files if /dev is mounted RO Peter Cordes
2000-11-27 12:42 ` Andries Brouwer
2000-11-27 21:47   ` Rogier Wolff
2000-11-28  0:09     ` Andries Brouwer
2000-11-28 14:04       ` Rogier Wolff
2000-11-28 21:37         ` Andries Brouwer
2000-11-29 12:01           ` Hugh Dickins
2000-11-29 12:39             ` Alexander Viro
2000-11-29 15:46               ` Hugh Dickins
2000-11-29 16:18                 ` Alexander Viro
2000-11-29 16:40                   ` Tigran Aivazian
2000-11-29 16:52                     ` Alexander Viro
2000-12-01 17:12                     ` Olivier Galibert
2000-12-01 17:59                       ` Richard B. Johnson
2000-11-29 16:24                 ` Tigran Aivazian
2000-11-29 16:25                   ` Tigran Aivazian
2000-11-29 16:42                   ` Alexander Viro
2000-11-29 16:58                     ` Tigran Aivazian
2000-11-29 17:07                       ` Tigran Aivazian
2000-11-29 16:48                   ` Hugh Dickins
2000-11-29 14:24             ` Richard B. Johnson
2000-11-29 14:33               ` Broken NTFS Joseph K. Malek
2000-11-29 19:28                 ` Jeff V. Merkey [this message]
2000-11-28 22:56   ` access() says EROFS even for device files if /dev is mounted RO Peter Cordes
2000-11-28 23:23     ` Alexander Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001129122832.A8639@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malekjo@aphrodite.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox