From: David Sanders <linux@sandersweb.net>
To: Haakon Riiser <haakon.riiser@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NTFS disk usage on Linux 2.6
Date: Thu, 15 Jan 2004 14:05:41 -0500 [thread overview]
Message-ID: <200401151401.1764@sandersweb.net> (raw)
In-Reply-To: <20040115010210.GA570@s.chello.no>
On Wednesday 14 January 2004 08:02 pm, Haakon Riiser wrote:
> Has anyone else noticed that the reported disk space usage on
> NTFS is completely unreliable on Linux 2.6? Just issued the
I'm having the same symptom. The following is on a 4G partition. The
WINNT directory is reported as 66G in size. Kernel 2.6.1.
david@debian:/mnt/hda5$ du * -sh
124M file
56M GNUwin32
6.3M Inetpub
1.3M lynx
0 Multimedia Files
267M pagefile.sys
134M perl
922M Program Files
0 RECYCLER
42M TEMP
2.7M util
13M vim
2.5k _viminfo
66G WINNT
--
David Sanders
linux@sandersweb.net
next prev parent reply other threads:[~2004-01-15 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 1:02 NTFS disk usage on Linux 2.6 Haakon Riiser
2004-01-15 14:51 ` Craig Taylor
2004-01-15 16:03 ` Disconnect
2004-01-15 19:05 ` David Sanders [this message]
2004-01-15 22:34 ` Wes Janzen
2004-01-16 0:43 ` Adam Sampson
2004-01-18 0:55 ` Haakon Riiser
2004-01-19 14:24 ` 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=200401151401.1764@sandersweb.net \
--to=linux@sandersweb.net \
--cc=haakon.riiser@fys.uio.no \
--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