From: Anton Altaparmakov <aia21@cam.ac.uk>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: ntfs CFT - was: Re: 2.6.14-rc4-mm1
Date: Mon, 17 Oct 2005 10:56:07 +0100 [thread overview]
Message-ID: <1129542967.26285.30.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <20051016154108.25735ee3.akpm@osdl.org>
On Sun, 2005-10-16 at 15:41 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
>
> git-ntfs.patch
This is a request for testers for ntfs. 2.6.14-rc4-mm1 contains a
pretty much complete re-write of file write support so some more testers
than just myself would be good before I submit it for inclusion in
2.6.15...
The rewrite means that the following features are now supported:
Given an existing uncompressed and unencrypted file, you can use:
- write(2) to write to the file, including beyond the end of the
existing file, and the file will be extended appropriately. Both
resident and non-resident files are supported. Support for heavily
fragmented files still has some limitations but you will just get an
EOPNOTSUPP error if you hit one. Everything will still be consistent on
the volume. Sparse files can also be written to and holes will be
filled in appropriately.
- truncate(2) and ftruncate(2) to change the size of the file, inlcuding
using open(2) with O_TRUNC flag. As with write(2) there still are some
limitations for heavily fragmented files, and as above, everything will
still be consistent on the volume if you hit an unsupported case.
What this means is that you can now run your favourite editor on an
existing file, e.g. "vim /ntfs/somefile.txt" works fine and you can save
your changes. Also things like running OpenOffice should work to edit
existing MS Office documents but I haven't tried it yet (it should work
as long as OpenOffice does not need to create temporary files in the
same directory as the document).
Still not supported features are creation/deletion of files/directories
and mmap(2) based writes to sparse regions of files. (The mmap(2)
support has not been modified since the last release, only the file
write(2) support was rewritten.)
If you do try it, please let me know how it worked for you! - Thanks a
lot in advance for testing!
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
.
next prev parent reply other threads:[~2005-10-17 9:56 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-16 22:41 2.6.14-rc4-mm1 Andrew Morton
2005-10-17 0:05 ` [PATCH] add missing header in include/asm/atomic.h Dominik Karall
2005-10-17 0:13 ` 2.6.14-rc4-mm1 Michal Piotrowski
2005-10-17 3:19 ` 2.6.14-rc4-mm1 Andrew Morton
2005-10-17 6:03 ` 2.6.14-rc4-mm1 Michal Piotrowski
2005-10-17 6:42 ` 2.6.14-rc4-mm1 Michal Piotrowski
2005-10-17 7:47 ` 2.6.14-rc4-mm1 Russell King
2005-10-17 0:46 ` 2.6.14-rc4-mm1 Con Kolivas
2005-10-17 7:10 ` 2.6.14-rc4-mm1 MAEDA Naoaki
2005-10-17 9:56 ` Anton Altaparmakov [this message]
[not found] ` <4489a22a0510172209v322e9d9eqe90c489c66b5c83b@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.0510180859580.7514@hermes-1.csi.cam.ac.uk>
[not found] ` <4489a22a0510181026v577f9b0ev535cf0acc74661f@mail.gmail.com>
[not found] ` <4489a22a0510181048n60ec5952i33d52c1b3527f906@mail.gmail.com>
2005-10-19 11:10 ` Warning: Serious NTFS data corruption bug! + Fix! - Was: Re: ntfs CFT - was: 2.6.14-rc4-mm1 Anton Altaparmakov
2005-10-17 10:29 ` 2.6.14-rc4-mm1 - drivers/serial/jsm/jsm_tty.c: no member named 'flip' Damir Perisa
2005-10-17 14:56 ` V. Ananda Krishnan
2005-10-17 15:21 ` Damir Perisa
2005-10-18 14:02 ` 2.6.14-rc4-mm1 - drivers/serial/ V. Ananda Krishnan
2005-10-18 20:12 ` Greg KH
2005-10-17 18:05 ` 2.6.14-rc4-mm1 - drivers/serial/jsm/jsm_tty.c: no member named 'flip' Alan Cox
2005-10-22 2:08 ` Paul Jackson
2005-10-22 6:39 ` Andrew Morton
2005-10-22 9:54 ` Alan Cox
2005-10-24 7:52 ` Andrew Morton
2005-10-17 12:21 ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-17 20:22 ` 2.6.14-rc4-mm1 Andrew Morton
2005-10-17 21:27 ` 2.6.14-rc4-mm1 Vojtech Pavlik
2005-10-17 21:39 ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-17 21:48 ` 2.6.14-rc4-mm1 Greg KH
2005-10-17 21:58 ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18 6:42 ` 2.6.14-rc4-mm1 Greg KH
2005-10-18 6:39 ` 2.6.14-rc4-mm1 Vojtech Pavlik
2005-10-18 6:44 ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18 6:58 ` 2.6.14-rc4-mm1 Greg KH
2005-10-18 7:09 ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18 7:17 ` 2.6.14-rc4-mm1 Greg KH
2005-10-18 7:22 ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18 7:38 ` 2.6.14-rc4-mm1 Greg KH
2005-10-18 7:30 ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-18 7:40 ` 2.6.14-rc4-mm1 Greg KH
2005-10-18 8:26 ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-19 3:44 ` 2.6.14-rc4-mm1 Greg KH
2005-10-19 3:58 ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-17 20:44 ` 2.6.14-rc4-mm1 Greg KH
2005-10-17 22:06 ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-17 21:06 ` 2.6.14-rc4-mm1 dead in early boot Helge Hafting
2005-10-17 21:09 ` Andrew Morton
2005-10-17 21:27 ` Helge Hafting
2005-10-17 21:53 ` Helge Hafting
2005-10-18 0:38 ` Andrew Morton
2005-10-18 14:30 ` Michael Neuffer
2005-10-17 22:24 ` Helge Hafting
2005-10-18 7:45 ` [PATCH] disable PREEMPT_BKL per default Olaf Hering
2005-10-18 7:53 ` Arjan van de Ven
2005-10-18 8:47 ` Olaf Hering
2005-10-18 8:58 ` Arjan van de Ven
2005-10-18 11:12 ` Olaf Hering
2005-10-18 11:52 ` Ingo Molnar
2005-10-19 14:04 ` 2.6.14-rc4-mm1 Alexandre Buisse
2005-10-19 15:52 ` 2.6.14-rc4-mm1 Jiri Slaby
2005-10-19 15:04 ` 2.6.14-rc4-mm1 Alexandre Buisse
2005-10-19 18:49 ` Wifi oddness [Was: Re: 2.6.14-rc4-mm1] Jiri Slaby
2005-10-20 16:48 ` Alexandre Buisse
2005-10-20 21:02 ` Jiri Slaby
2005-10-20 21:26 ` Mark Lord
2005-10-20 23:08 ` Jiri Slaby
2005-10-20 23:39 ` Jeff Garzik
2005-10-20 23:45 ` Andrew Morton
2005-10-21 0:21 ` Jeff Garzik
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=1129542967.26285.30.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=akpm@osdl.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®