From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Stefan Pfetzing <dreamind@dreamind.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] XFS - blkgetsize64
Date: Wed, 04 Sep 2002 10:51:47 -0600 [thread overview]
Message-ID: <20020904165147.A33FC4829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Stefan Pfetzing <dreamind@dreamind.de> of "Wed, 04 Sep 2002 16:30:13 +0200." <20020904143013.GC4386@dreamind.de>
Stefan Pfetzing wrote:
> mkfs.xfs always got the size of the Device (/dev/sda5) wrong. (it complained
> about not getting with lseek64 to that position...)
...
> So he said, perhaps there is a bug in the SCSI (lasi?) driver.
I don't think it's the driver.
lseek64 must be getting redirected to lseek().
Linux kernel only supports "lseek".
See "struct file_operations" in include/linux/fs.h.
loff_t is a 64-bit type.
include/linux/types.h:typedef __kernel_loff_t loff_t;
include/asm/posix_types.h:typedef long long __kernel_loff_t;
> P.S.: I'm using 2.4.19-pa9 with a self made diff from vanilla 2.4.19 against
> XFS CVS. (the patch did in nearly cleanly)
Are you running 32-bit or 64-bit kernel?
I want to know if arch/parisc/kernel/sys_parisc32.c might be the problem.
grant
next prev parent reply other threads:[~2002-09-04 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 14:30 [parisc-linux] XFS - blkgetsize64 Stefan Pfetzing
2002-09-04 16:51 ` Grant Grundler [this message]
2002-09-04 18:11 ` Randolph Chung
2002-09-04 18:42 ` [parisc-linux] GCC and quad-precision floating point John David Anglin
2002-09-04 19:15 ` Carlos O'Donell
2002-09-04 19:59 ` John David Anglin
2002-09-04 18:28 ` [parisc-linux] XFS - blkgetsize64 Stefan Pfetzing
2002-09-04 20:57 ` Stefan Pfetzing
2002-09-05 4:38 ` Randolph Chung
2002-09-05 5:28 ` Randolph Chung
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=20020904165147.A33FC4829@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=dreamind@dreamind.de \
--cc=parisc-linux@lists.parisc-linux.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.