Re: 2.2.x corruption solved (Was Re: Statically linked 'tar')
- To: Andrea Arcangeli <andrea@suse.de>
- Cc: Bart Warmerdam <bartw@xs4all.nl>, debian-alpha@lists.debian.org, linux-kernel@vger.rutgers.edu, Written by Bernhard Fastenrath <fasten@informatik.uni-bonn.de>
- Subject: Re: 2.2.x corruption solved (Was Re: Statically linked 'tar')
- From: Martin Lucina <mato@nz.eds.com>
- Date: Wed, 13 Oct 1999 09:44:40 +1300
- Message-id: <[🔎] 19991013094439.F283@strangepork.lab.nz.eds.com>
- Mail-followup-to: Andrea Arcangeli <andrea@suse.de>, Bart Warmerdam <bartw@xs4all.nl>, debian-alpha@lists.debian.org, linux-kernel@vger.rutgers.edu, Written by Bernhard Fastenrath <fasten@informatik.uni-bonn.de>
- In-reply-to: <[🔎] Pine.LNX.4.10.9910121505530.646-100000@alpha.random>; from Andrea Arcangeli on Tue, Oct 12, 1999 at 03:21:52PM +0200
- References: <[🔎] 19991012092828.D283@strangepork.lab.nz.eds.com> <[🔎] Pine.LNX.4.10.9910121505530.646-100000@alpha.random>
On Tue, Oct 12, 1999 at 03:21:52PM +0200, Andrea Arcangeli wrote:
> After some time the kernel crashed and I destroyed all partitions of my
> hard disk. _all_. Note that the partition table was still fine. Only the
> contents of the partitons (superblocks mainly) was completly screwed up.
Same story in my case.
> So this is a warning for people having partition c stopping before one of
> your partition. fdisk is right about partition c. Trust its end and not
> what fdisk suggests as end of other partitions.
>
> I think the fix is simply a -1 in some line of fdisk... Looks like a
> silly/typo bug. I cc'ed to the author of the bsdlabel in our fdisk. If he
> can't fix that I can do that myself.
Agreed. It's not by far the only bug though. There are at least another two I
recall. First, have you tried editing any disklabels with fdisk? Generally
after deleting say the 'b' and 'e' partitions from a disklabel with 'a' to 'f'
and then trying to add them back in will completely screw fdisks calculations
and it will become impossible to write out a correct disklabel. I had to redo
the disklabel from the beginning a couple of times before I worked this out.
Second, it is a well known problem that either fdisk or the kernel (I think
it's just a missed out call to ioctl() in fdisk) will not re-scan the
disklabel after writing it, thus people have to reboot before it is
recognised.
Martin
Reply to: