linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jim Hickstein <jxh@mirapoint.com>
To: "Derrik Walker v2.0" <firebug@apk.net>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-user@lists.linuxppc.org
Subject: Re: Physical disk size 65536 blocks for an 8G drive
Date: Sat, 06 Nov 1999 21:29:42 -0800	[thread overview]
Message-ID: <38250E46.DC6F9625@mirapoint.com> (raw)
In-Reply-To: Pine.LNX.4.10.9911061719150.17987-100000@zzzt.apk.net


> > I have a PBG3 Wallstreet and recently bought a new 8GB drive to put in
> > it, an IBM DYLA-28100.  MacOS 8.6, update the drivers, so far, so good.
> > I managed to get pdisk to make partitions (after umounting /mnt/cdrom
> > from /dev/hda to silence a warning in writing the partition table).
> > MacOS runs fine, with volumes in hda10 (5GB hfs+) and hda11 (600MB hfs),
> > _above_ Linux.  But Linux barfs mounting / on /dev/hda7 (and even worse
> > for /usr on /hda9), saying that the superblock reports a size of
> > so-and-so (~131000 for /) but the _physical size of the disk_ is 65536 blocks.
> >
> > Evidently something is reporting a block count of 0xffff, and it's
> > getting incremented to tell me the "length".  Yet, the drive probes
> > correctly (apparently) and reports a size of 7145MB or so.

Nevermind.  Someone told me about "cat /proc/partitions", which revealed
that 65536 _blocks_ (1K) was in fact the correct size of /dev/hda7, and
the ~900000-block size in the superblock was the wrong part.

I tried it all again, this time with no Jaz cart, and I told it to check
for bad blocks (not sure I had the patience for this last time), and for
some reason it worked.  I'm running it now.  Bizarre.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~1999-11-07  5:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-06 21:48 Physical disk size 65536 blocks for an 8G drive Jim Hickstein
1999-11-06 22:22 ` Derrik Walker v2.0
1999-11-07  5:29   ` Jim Hickstein [this message]

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=38250E46.DC6F9625@mirapoint.com \
    --to=jxh@mirapoint.com \
    --cc=firebug@apk.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).