From: David Sanders <linux@sandersweb.net>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [PATCH-BK-2.6] NTFS fix "du" and "stat" output (NTFS 2.1.6).
Date: Wed, 21 Jan 2004 13:24:54 -0500 [thread overview]
Message-ID: <200401211318.53776@sandersweb.net> (raw)
In-Reply-To: <Pine.SOL.4.58.0401191413180.7391@yellow.csi.cam.ac.uk>
On Monday 19 January 2004 09:15 am, Anton Altaparmakov wrote:
> This fixes the erroneous "du" and "stat" output people reported on
> ntfs partitions containing compressed directories.
Thanks for the quick patch. There are still problems with the reported
disk usage. I use as an example the file win.ini. With the 2.4.24
kernel I get the following results:
$ ls -l win.ini
-r--r----- 1 root staff 399 Jan 27 2003 win.ini
$ stat win.ini
File: "win.ini"
Size: 399 Blocks: 2 IO Block: 1024 Regular File
Device: 305h/773d Inode: 1023 Links: 1
Access: (0440/-r--r-----) Uid: ( 0/ root) Gid: ( 50/ staff)
Access: Thu Jan 15 15:34:09 2004
Modify: Mon Jan 27 18:54:00 2003
Change: Sun Sep 22 07:23:44 2002
$ du -h win.ini
1.0k win.ini
But, under the 2.6.1 kernel:
$ ls -l win.ini
-r-xr-x--- 1 root staff 399 Jan 27 2003 win.ini
$ stat win.ini
File: "win.ini"
Size: 399 Blocks: 0 IO Block: 4096 Regular File
Device: 305h/773d Inode: 1023 Links: 1
Access: (0550/-r-xr-x---) Uid: ( 0/ root) Gid: ( 50/ staff)
Access: Thu Jan 15 15:34:09 2004
Modify: Mon Jan 27 18:54:00 2003
Change: Mon Jan 27 18:54:00 2003
$ du -h win.ini
0 win.ini
Now, surely the 2.4.24 kernel is reporting the more accurate disk usage
since with 2.6.1 it reports 0 blocks (vice 2).
Thanks in advance,
--
David Sanders
linux@sandersweb.net
next prev parent reply other threads:[~2004-01-21 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 14:15 [PATCH-BK-2.6] NTFS fix "du" and "stat" output (NTFS 2.1.6) Anton Altaparmakov
2004-01-21 18:24 ` David Sanders [this message]
2004-01-21 19:14 ` David Sanders
2004-01-22 9:29 ` Anton Altaparmakov
2004-01-21 19:38 ` David Sanders
2004-01-22 10:32 ` Anton Altaparmakov
2004-01-22 9:20 ` Anton Altaparmakov
2004-01-22 17:48 ` David Sanders
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=200401211318.53776@sandersweb.net \
--to=linux@sandersweb.net \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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