public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: <lnordstrom@home.se>
To: linux-8086@vger.kernel.org
Subject: Filesystem creation
Date: Sat, 11 May 2002 23:23:39 -200	[thread overview]
Message-ID: <200205112122.g4BLMat08562@bele.abc.se> (raw)

Hello.

As being new to this list, first a short introduction:
Living 15 km outside the nearest town with my woman and four
cats. Working as a lathe-turner in town.
I have been interested in and tinkered with computers since the
late seventies, more actively since late eighties.
Could afford to buy my first DOS-box (second hand XT) -89. Since
then the zoo has grown a bit. Installed Linux for the first time
somewhere late -98. Got LRP running on an old crappy 386 to
network my modem a year later. Fiddel with muLinux now and then.
Never done any serious programming of any sort, just small bits
and pieces in Basic, Pascal, assembler, DOS batch, shellscript.
Enough of this.

I was glad when I found out about ELKS a while ago (2-3 yrs) and
even gladder to see that there now are ready-to-go floppy
images.

I'm trying to run the image "comb" on an IBM PS/2-30. It boots
OK and runs as I expect. But when I try to make a file system on
the harddisk and mount it, I bump into something.

fdisk reports 773 cyl, 2 heads, 27 sec.

/dev/bda1  *  0 1   6   1 27 385   1  20520
/dev/bda2  *  0 1 386   1 27 695  80  16740
/dev/bda3  *  0 1 696   1 27 772  80   4158

mkfs /dev/bda2 5859 finishes OK, but a following fsck /dev/bda2
produces an error message, fsck: bad magic number in super-block.

If I reduce the number of blocks by one, to 5858, fsck finishes
without error message.

Mounting the new fs under /mnt goes OK, but ls /mnt gives error
messages.

/mnt:
Bad inode number on dev 0302: 3677 is out of range
Bad inode number on dev 0302: 11330 is out of range
(some garbage on this line)

Trying to repair the fs with fsck -a desn't seem to do any good.

If I reduce the number of blocks further, down to 5666, I get no
error messages anywhere. Mounting, unmounting, making
directories, copying files seems to work OK.

Did I bump into anything but my own ignorance?

I realize I know too little about the minix fs. Google produces
a lot of links but the first few pages contained no link to a
spec. Anybody got a good URL to a little detail on minix fs?


Regards,
Lars

Does steel wool come from metal sheep?

Net-Tamer V 1.10.1  - Registered


             reply	other threads:[~2002-05-12  1:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-12  1:23 lnordstrom [this message]
2002-05-12 20:04 ` Filesystem creation Riley Williams
2002-05-13  8:59 ` Javier Sedano
2002-05-13 12:02   ` Harry Kalogirou
2002-05-13 17:42     ` Riley Williams
2002-05-13 23:52       ` Alan Cox
2002-05-14  6:56         ` Riley Williams
2002-05-14 12:44         ` Riley Williams
2002-05-14 17:47           ` Alan Cox
2002-05-14 17:59             ` Riley Williams
2002-05-14 23:41               ` Alan Cox
2002-05-15 17:52                 ` Riley Williams
     [not found]     ` <3CE0283D.264@havn.com>
2002-05-14 21:01       ` Harry Kalogirou
2002-05-15  1:18         ` Alan Cox
2002-05-15 17:05         ` Riley Williams
  -- strict thread matches above, loose matches on Subject: below --
2002-05-13  2:33 lnordstrom
2002-05-12 23:07 ` Riley Williams
2002-05-13 14:22   ` Dan Olson
2002-05-13 17:36     ` Riley Williams
2002-05-13 23:50       ` Alan Cox
2002-05-14  0:12         ` Dan Olson
2002-05-14  7:06           ` Riley Williams
2002-05-14 23:31             ` Dan Olson
2002-05-14  6:54         ` Riley Williams
2002-05-14 23:36           ` Dan Olson
2002-05-14  0:19       ` Dan Olson
2002-05-14  6:42         ` Riley Williams
2002-05-14 23:48           ` Dan Olson
2002-05-15  0:12             ` Alan Cox

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=200205112122.g4BLMat08562@bele.abc.se \
    --to=lnordstrom@home.se \
    --cc=linux-8086@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