All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Marc Mutz <Marc@mutz.com>
Cc: Adam <adam@cfar.umd.edu>, linux-kernel@vger.kernel.org
Subject: Re: 'holey files' not holey enough.
Date: Wed, 29 Nov 2000 16:34:22 -0700 (MST)	[thread overview]
Message-ID: <200011292334.eATNYNB09518@webber.adilger.net> (raw)
In-Reply-To: <3A2584DC.1699B6CD@Mutz.com> "from Marc Mutz at Nov 29, 2000 10:36:12 pm"

Marc Mutz writes:
> kernel 2.2.17, '/' being a 1k blocksize ext2fs:
> 
> root@adam:/ > dd if=/dev/zero of=holed.file bs=1000 seek=5000 count=1000
> 1000+0 records in
> 1000+0 records out
> root@adam:/ > ls -l holed.file
> -rw-r--r--   1 root     root      6000000 Nov 29 23:33 holed.file
> root@adam:/ > du -sh holed.file
> 5.7M    holed.file

Strangely, I have 2.2.17 (TurboLinux patched), on a 1k filesystem and
I have no problems.  I have 1k, 2k, and 4k ext2 fs, all OK.

What people who have the problem should be doing is:
> ls -li holed.file        # find inode number
10732 -rw-r--r--    1 root     root      6000000 Nov 29 16:17 holed.file
> du -sk holed.file        # see what "stat" thinks
983k    holed.file
> debugfs /dev/XXX
debugfs> stats           # find out ext2 block size
...
Block size = 1024, fragment size = 1024
...
debugfs> stat <10732>  # (with < and >)
Inode: 10732   Type: regular    Mode:  0644   Flags: 0x0   Generation:
4048594821
User:     0   Group:     0   Size: 6000000
File ACL: 0    Directory ACL: 0
Links: 1   Blockcount: 1966
                       ^^^^ these are 512-byte blocks, so / 2 for ~kB
		            they include indirect blocks and such
Fragment:  Address: 0    Number: 0    Size: 0
ctime: 0x3a258e82 -- Wed Nov 29 16:17:22 2000
atime: 0x3a258e82 -- Wed Nov 29 16:17:22 2000
mtime: 0x3a258e82 -- Wed Nov 29 16:17:22 2000
BLOCKS:
47512 47513 47514 47515 47516 47517 47518 47519 47520 ... 48723 48724
TOTAL: 983
       ^^^ these are ext2fs sized blocks, not necessarily kB

If what debugfs says doesn't match du, then it is du/libc/stat that is
broken.  If debugfs says the file actually has 6000000 bytes of data,
then it is the filesystem that is broken.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-30  0:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-29 13:00 'holey files' not holey enough Adam
2000-11-29 13:07 ` Tigran Aivazian
2000-11-29 13:14   ` Adam
2000-11-29 20:55   ` Adam
2000-11-29 20:03     ` Martin Josefsson
2000-11-29 22:36 ` Marc Mutz
2000-11-29 23:18   ` safemode
2000-11-29 23:34   ` Andreas Dilger [this message]
2000-11-30 14:34     ` Adam
2000-11-30 17:45       ` Andreas Dilger
2000-12-01 14:13     ` Marc Mutz
     [not found] <Pine.GSO.4.21.0012020517290.20770-100000@chia.umiacs.umd.edu>
2000-12-02 20:40 ` Jaakko Hyvätti

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=200011292334.eATNYNB09518@webber.adilger.net \
    --to=adilger@turbolinux.com \
    --cc=Marc@mutz.com \
    --cc=adam@cfar.umd.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.