public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aeb@veritas.com>
To: Miles Lane <miles@speakeasy.org>
Cc: Matthew Dharm <mdharm@one-eyed-alien.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test10 -- Problem reading VFAT formatted ORB drive.
Date: Tue, 7 Nov 2000 05:45:50 +0100	[thread overview]
Message-ID: <20001107054550.A15541@veritas.com> (raw)
In-Reply-To: <3A07C0BF.4060607@speakeasy.org>
In-Reply-To: <3A07C0BF.4060607@speakeasy.org>; from miles@speakeasy.org on Tue, Nov 07, 2000 at 12:43:43AM -0800

On Tue, Nov 07, 2000 at 12:43:43AM -0800, Miles Lane wrote:

> I have an ORB drive I am accessing using the usb-storage driver.
> I formatted the drive media last night using Windoze 98.  The media
> was formatted as though it had one large partition, which is weird
> because I had previously partitioned the drive under Linux 2.4.0-test10
> with several partitions.  The Windoze format utility did not notice
> those partitions and simply (I thought) wrote one large partition and
> formatted it as VFAT.  I have successfully written and read data on
> the media using two separate Windoze 98 machines.  When I mounted
> the drive under 2.4.0-test10 and then looked at the media with
> fdisk, here's what I see:
> 
> #> fdisk /dev/sda
> 
> Disk /dev/sda: 68 heads, 62 sectors, 1021 cylinders
> Units = cylinders of 4216 * 512 bytes
> 
>     Device Boot    Start       End    Blocks   Id  System
> /dev/sda1   ?    455397    584533 272218546+  20  Unknown
> Partition 1 has different physical/logical beginnings (non-Linux?):
>       phys=(356, 97, 46) logical=(455396, 22, 59)
...
> 
> What's going on here?  It seems to me that this is a bug in the
> Linux test10 filesystem support, since Windoze can read and write
> to this drive currently.  Our implementation should be compatible.

Well, clearly (i) you can read it, and (ii) you don't like the contents.
With these removable disks there are often two possibilities:
either format the thing as a large floppy (without partition table)
or format it as a disk.
Maybe you did the former. (In that case, "mount /dev/sda" might work.)

If you can't find out what happened, I wouldnt mind seeing
the first 64 sectors or so.

(By the way, the geometry is interesting: 1021/68/62.
My web page says:
  "The size is 2.2 GB. Castlewood recommends a C/H/S = 4273/16/63 geometry,
   which multiplies out to 4307184 sectors, that is, 2205278208 bytes.
   The default geometry with which the IDE version of the drive is shipped
   gives only 528 MB."
Now 68*62*1021*512=2203922432, almost full capacity. I wonder who
invented it.)

Andries
-
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-07  4:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-07  8:43 2.4.0-test10 -- Problem reading VFAT formatted ORB drive Miles Lane
2000-11-06 21:54 ` Crutcher Dunnavant
2000-11-07  4:45 ` Andries Brouwer [this message]
2000-11-07 18:17   ` Miles Lane

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=20001107054550.A15541@veritas.com \
    --to=aeb@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm@one-eyed-alien.net \
    --cc=miles@speakeasy.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