From: Stefan Pfetzing <dreamind@dreamind.de>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] XFS - blkgetsize64
Date: Wed, 4 Sep 2002 22:57:44 +0200 [thread overview]
Message-ID: <20020904205744.GA29749@dreamind.de> (raw)
In-Reply-To: <20020904182814.GA17156@dreamind.de>
Hum, replying to myself...
* Stefan Pfetzing <dreamind@dreamind.de> [020904 20:28]:
> * Grant Grundler <grundler@dsl2.external.hp.com> [020904 18:51]:
> > Stefan Pfetzing wrote:
> [snip]
> > > 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.
> I'm running a 32bit kernel, since some time ago I had problems with 64bit and
> cdrecord.
I just got a blkgetsize* testprogram...
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=62038)
---snip---
root@hp:~# ./blkgetsizetester /dev/sda2
Device size is 83968 blocks (42991616 bytes)
Device size per BLKGETSIZE64 is 12345 bytes
root@hp:~# ./blkgetsizetester /dev/sda5
Device size is 1026016 blocks (525320192 bytes)
Device size per BLKGETSIZE64 is 12345 bytes
root@hp:~#
---snip---
I think thats the problem with xfs... well at least blkgetsize64 should report
an error, if its not working correctly.
bye
Stefan
--
http://www.dreamind.de/
Oroborus and Debian GNU/Linux Developer.
next prev parent reply other threads:[~2002-09-04 20:57 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
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 [this message]
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=20020904205744.GA29749@dreamind.de \
--to=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.