From: arvest@orphansonfire.com
To: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.11 loses sda9
Date: Thu, 11 Oct 2001 00:20:17 -0500 [thread overview]
Message-ID: <01101100201700.04473@lithium> (raw)
In-Reply-To: <Pine.GSO.4.21.0110110106070.21168-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0110110106070.21168-100000@weyl.math.psu.edu>
On Thursday 11 October 2001 00:07, Alexander Viro wrote:
> > I recompiled (I used the same .10 conf) and rebooted, but my reboot
> > halted because /dev/sda9 didnt exist. I checked this in fdisk, and it
> > didnt see it. I rebooted to the 2.4.10 kernel, and sda9 was there. What
> > happened?
>
> Information from fdisk would help - from both versions (with 2.4.11 you'll
> need to boot with init=/bin/sh, obviously). It may be a bug in partition
> code, it may be something fishy with guessing geometry (SCSI uses bread()
> for that) and it may be something fishy in block devices in pagecache
> stuff.
>
> If you have sfdisk, sfdisk /dev/sda -O /tmp/foo + mailing the result would
> make debugging the thing much simpler (that one - from the 2.4.10).
I can get the system booted enough to work on (and totaly up) with this
partition failing. I dont know what more information from fdisk I can give
you, sda9 is there with .10, and gone with .11 It even allowed me to add a
new partition (i didnt save) I tried sfdisk but it gave me these errors.
sfdisk /dev/sda -O /tmp/foo
Checking that no-one is using this disk right now ...
BLKRRPART: Device or resource busy
This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.
Use the --force flag to overrule all checks.
I didnt try the flags, Im worried that its going to overwrite my
filesystem. Heres my /proc/scsi/sym53c8xx/0 in case its needed. My system
is entirely scsi, except for an atapi burner. All scsi compiled static.
General information:
Chip sym53c875, device id 0xf, revision id 0x26
On PCI bus 0, device 16, function 0, IRQ 9
Synchronous period factor 12, max commands per lun 32
Whats my next step?
next prev parent reply other threads:[~2001-10-11 5:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 5:07 2.4.11 loses sda9 Alexander Viro
2001-10-11 5:20 ` arvest [this message]
2001-10-11 5:23 ` Alexander Viro
2001-10-11 5:45 ` arvest
2001-10-11 6:08 ` Andreas Dilger
2001-10-11 6:17 ` Alexander Viro
2001-10-11 16:41 ` arvest
2001-10-11 16:46 ` Ignacio Vazquez-Abrams
2001-10-11 16:50 ` Alexander Viro
2001-10-11 17:23 ` Alexander Viro
2001-10-11 18:22 ` Guest section DW
2001-10-11 18:25 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-10-12 0:07 Andries.Brouwer
2001-10-11 22:11 Andries.Brouwer
2001-10-11 22:26 ` Alexander Viro
2001-10-11 20:29 Andries.Brouwer
2001-10-11 20:54 ` Alexander Viro
2001-10-11 19:07 Andries.Brouwer
2001-10-11 19:19 ` Alexander Viro
2001-10-11 4:22 arvest
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=01101100201700.04473@lithium \
--to=arvest@orphansonfire.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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