public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: linux-kernel@vger.kernel.org
Subject: [Fwd: NTFS repair tools]
Date: Thu, 07 Dec 2000 20:27:41 -0700	[thread overview]
Message-ID: <3A30552D.A6BE248C@timpanogas.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]


Linux/Linus/Anton/Alan,

I am still sending out the NTFS repair tools for Linux trashed volumes,
and I've lost count now relative to how many I've sent out, but it's
somewhere in the thousands.  Is NTFS write stable enough now in 2.4 to
fix these problems, if so, can we DISABLE by REMOVING write code in the
VFS tables for those versions in other trees we know will trash people's
drives.  I am sending out over 100 copies a week now (I could make a
business out of fixing NTFS drives trashed by Linux) and the numbers are
getting higher instead of lower of people asking for these tools, which
woul indicate more people's data is getting trashed.

Do folks not know this NTFS driver will trash hard drives?  We need to
alert folks DO NOT USE WRITE NTFS MODE in those versions we know are
busted.  I enjoy helping NT customers get their data back and helping
with this problem, but at some point, the NTFS driver either needs to
get sync'd or WRITE disabled.  What I'm doing here is like trying to put
a bandaid over the mouth of the amazon river, and as Linux grows and
grows and grows, this problem will just get larger, and to a point where
I don't have the bandwidth to support it properly.

I will keep providing this service, but I am only treating the symptons
of the illness and not curing the patient.  Based upon the level of
contamination of TRG with Microsoft IP, I have been advised if I post an
NTFS replacement before the 18 month doctrine of inevitability "window"
is past, Microsoft will most certainly sue us, and win.

I strongly recommend stubbing our the file_write() calls in the NTFS VFS
until this gets fixed, until I can get working NTFS out there, or Anton
can get one out there (which will be another year and a half if it comes
from us based on the agreements we have with Microsoft).

:-)

Jeff

[-- Attachment #2: Type: message/rfc822, Size: 1819 bytes --]

From: Lynn Evans <lynn@mail.earth.monash.edu.au>
To: jmerkey@timpanogas.com
Subject: NTFS repair tools
Date: Fri, 08 Dec 2000 14:13:58 +1100
Message-ID: <3A3051F5.1D16ADB0@mail.earth.monash.edu.au>

I have been using a PC which dual boots Linux/NT. Linux
seems to have trashed the ntfs partition when it ran out of
space while writing to it. The partition is data only but
was not backed up.
A search on the net indicated that this is a common problem
and that you may be able to point me at or provide tools
which could help repair the partition.
I would be grateful for any help,
Lynn

--

________________________________
Lynn Evans
Department of Earth Sciences
P.O. Box 28E
Monash University
Melbourne, VIC 3800 Australia

Phone +61 (3) 9905 1527
Fax   +61 (3) 9905 4903
Lynn.Evans@sci.monash.edu.au
________________________________


             reply	other threads:[~2000-12-08  4:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08  3:27 Jeff V. Merkey [this message]
2000-12-08  4:13 ` [Fwd: NTFS repair tools] Peter Samuelson
2000-12-08  4:43   ` Jeff V. Merkey
2000-12-08  5:53     ` Michael H. Warfield
2000-12-08  4:54       ` Jeff V. Merkey
2000-12-08  5:04       ` Peter Samuelson
2000-12-08  5:08         ` [PATCH] NTFS repair tools Jeff V. Merkey
2000-12-08  6:06           ` Peter Samuelson
2000-12-08  8:17             ` Jeff V. Merkey
2000-12-08 14:46             ` Jeff Garzik
2000-12-08  7:37           ` Anton Altaparmakov
2000-12-08 19:01             ` Jeff V. Merkey
2000-12-08  7:50         ` [Fwd: NTFS repair tools] Andrzej Krzysztofowicz
2000-12-08 13:19       ` David Relson
2000-12-08 13:43         ` David Weinehall
2000-12-08 14:34           ` Jan-Benedict Glaw
2000-12-08 17:02             ` Michael H. Warfield
2000-12-08 18:35             ` Jeff V. Merkey
2000-12-08 14:00     ` Alan Cox
2000-12-08 14:27       ` Rik van Riel
2000-12-08 14:44         ` Mohammad A. Haque
2000-12-08 15:08           ` David Woodhouse
2000-12-08 14:50         ` Richard B. Johnson
2000-12-08 18:33       ` Jeff V. Merkey
2000-12-08 17:42         ` Jeff Garzik
2000-12-08 18:50           ` Jeff V. Merkey
2000-12-09 22:03         ` Eric W. Biederman
2000-12-10  1:11           ` Jeff V. Merkey
2000-12-10  2:12       ` Ren Haddock
2000-12-10  5:26         ` Andre Hedrick
2000-12-10  2:34       ` David Feuer
2000-12-10  2:49         ` Daryll Strauss
2000-12-12  2:23           ` Jes Sorensen
2000-12-12  2:46             ` Wakko Warner
2000-12-10  5:00         ` John Alvord
2000-12-10 16:11           ` Horst von Brand
2000-12-08 13:55 ` Alan Cox
2000-12-08 18:31   ` Jeff V. Merkey
  -- strict thread matches above, loose matches on Subject: below --
2000-12-09  8:00 Mark Sutton
2000-12-09 16:49 ` Willy Tarreau
2000-12-09 20:14   ` Jeff V. Merkey
2000-12-09 22:51   ` Jeff V. Merkey
2000-12-11 13:52 ` Xavier Bestel
2000-12-10  1:38 willy tarreau
2000-12-10  2:40 ` Jeff V. Merkey

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=3A30552D.A6BE248C@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    /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