public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Mutz <Marc@Mutz.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Adam <adam@cfar.umd.edu>, linux-kernel@vger.kernel.org
Subject: Re: 'holey files' not holey enough.
Date: Fri, 01 Dec 2000 14:13:10 +0000	[thread overview]
Message-ID: <3A27B1F6.48E959BE@Mutz.com> (raw)
In-Reply-To: <200011292334.eATNYNB09518@webber.adilger.net>

Andreas Dilger wrote:
> 
> 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

dito

> > debugfs /dev/XXX
> debugfs> stats           # find out ext2 block size
> ...
> Block size = 1024, fragment size = 1024
> ...

dito

> Links: 1   Blockcount: 1966

dito

> TOTAL: 983

dito

> 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.
> 
$ du --version
du (GNU fileutils) 3.16
$ ls -l /lib/libc*
lrwxrwxrwx   1 root     root           13 May  8  1999 /lib/libc.so.4 \
-> libc.so.4.7.6
-rwxr-xr-x   1 root     root       634880 Apr 29  1996
/lib/libc.so.4.7.6
-rwxr-xr-x   1 root     root      2478585 Dec 14  1998 /lib/libc.so.6
-rwxr-xr-x   1 root     root        85699 Dec 14  1998
/lib/libcrypt.so.1
$ ldd /usr/bin/du
        libc.so.6 => /lib/libc.so.6 (0x40009000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

all from SuSE 6.0 (I know, it's old...)

Marc

-- 
Marc Mutz <Marc@Mutz.com>     http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics

PGP-keyID's:   0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)


-
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-12-01 17:58 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
2000-11-30 14:34     ` Adam
2000-11-30 17:45       ` Andreas Dilger
2000-12-01 14:13     ` Marc Mutz [this message]
     [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=3A27B1F6.48E959BE@Mutz.com \
    --to=marc@mutz.com \
    --cc=adam@cfar.umd.edu \
    --cc=adilger@turbolinux.com \
    --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