From: Anton Altaparmakov <aia21@cantab.net>
To: Axel Siebenwirth <axel@hh59.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NTFS: 2.0.15 - Fake inodes based attribute i/o via the page cache, fixes, cleanups
Date: Mon, 08 Jul 2002 19:30:00 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20020708192448.028f5ec0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20020708180423.GA4676@neon.hh59.org>
At 19:04 08/07/02, Axel Siebenwirth wrote:
>Is it still the lack of information on the filesystem from Microsoft?
No, we have a pretty good idea of ntfs now. But it is a complicated fs and
when writing you need to take care of a lot of things simultaneously or you
corrupt the volume. ntfs is organized as a transactional, relational
database , hence there is a lot of book keeping involved in modifyin any
structure. Even without supporting the journal (we will not support it at
least initially...) almost all data is duplicated in various places and if
you forget to update something somewhere when updating it elsewhere you
basically make salad of the metadata and the probability is quite high that
you end up killing the data on the volume either in part or completely...
Finally I am busy with my PhD and I have two part time jobs as well so I
don't have much time to develop ntfs... As always with free software
development, it goes slowly...
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2002-07-08 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 17:47 Anton Altaparmakov
2002-07-08 18:04 ` Axel Siebenwirth
2002-07-08 18:21 ` Anton Altaparmakov
2002-07-08 18:30 ` Anton Altaparmakov [this message]
2002-07-08 20:52 ` NTFS write support [was: NTFS: 2.0.15] Axel Siebenwirth
2002-07-08 21:10 ` Anton Altaparmakov
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=5.1.0.14.2.20020708192448.028f5ec0@pop.cus.cam.ac.uk \
--to=aia21@cantab.net \
--cc=axel@hh59.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
all inboxes | Powered by JetHome®